Insforge Dev
Skill ActiveUse this skill set when contributing to the InsForge monorepo itself. This is for InsForge maintainers and contributors editing the platform, the shared dashboard package, the self-hosting shell, the UI library, shared schemas, tests, or docs.
To guide InsForge maintainers and contributors on best practices for developing within the InsForge monorepo, ensuring consistency and quality.
Features
- Monorepo contribution guidelines
- Package boundary identification
- Code placement rules
- Repository convention adherence
- Pre-PR development checklist
Use Cases
- Contributing code to the InsForge platform.
- Editing shared dashboard packages.
- Modifying the self-hosting shell or UI library.
- Updating shared schemas, tests, or documentation within the monorepo.
Non-Goals
- Guiding app development on InsForge.
- Providing general AI agent development instructions.
Trust
- warning:Issues AttentionOpen issues: 23, Closed issues (last 90d): 84. The closure rate is 84 / (23 + 84) ≈ 49.3%, which is below the 50% threshold for a pass, indicating maintainers may be slow to close issues.
Installation
npx skills add InsForge/InsForgeRuns the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.
Quality Score
Trust Signals
Similar Extensions
Add New Opc Skill
100Checklist and automation guide for adding a new skill to the OPC Skills project. Ensures all required files, metadata, logos, and listings are created before release. Use when adding a new skill, publishing a skill, or preparing a skill for release.
Baseline Ui
100Validates animation durations, enforces typography scale, checks component accessibility, and prevents layout anti-patterns in Tailwind CSS projects. Use when building UI components, reviewing CSS utilities, styling React views, or enforcing design consistency.
Deepinit
100Deep codebase initialization with hierarchical AGENTS.md documentation
Definition Of Done
100Mandatory checks to run before completing any task that touches md files or dart code in this repository.
Testing Clickup Cli
100Run and manage tests for clickup-cli. Covers unit tests, e2e tests against a real ClickUp workspace, and the test data setup. Use when running tests, adding test coverage, debugging test failures, or setting up test fixtures.
Playwright Best Practices
100Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.