// Use this skill when contributing to InsForge's shared dashboard package. This is for maintainers editing `packages/dashboard`, which ships in `self-hosting` and `cloud-hosting` modes, and the local `frontend/` shell used for `self-hosting` in this repo.
Use this skill when contributing to InsForge's backend package. This is for maintainers editing backend routes, services, providers, auth, database logic (including RLS-enforced surfaces like storage and realtime), schedules, or backend tests in the InsForge monorepo.
Use 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.
Write, edit, and maintain documentation. Use for collaborative drafting, autonomous writing, or improving existing docs. Defaults to collaborative mode where the human makes final decisions. Built by Mintlify.
Use this skill when contributing to InsForge's product documentation in this repository. This is for maintainers editing public docs in `docs/core-concepts`, agent docs in `docs/agent-docs`, SDK integration guides in `docs/sdks`, and OpenAPI specs in `openapi`.
Use 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.
Use this skill when contributing to InsForge's backend package. This is for maintainers editing backend routes, services, providers, auth, database logic (including RLS-enforced surfaces like storage and realtime), schedules, or backend tests in the InsForge monorepo.
| name | dashboard |
| description | Use this skill when contributing to InsForge's shared dashboard package. This is for maintainers editing `packages/dashboard`, which ships in `self-hosting` and `cloud-hosting` modes, and the local `frontend/` shell used for `self-hosting` in this repo. |
Use this skill for dashboard work in the InsForge repository.
packages/dashboard/src/**packages/dashboard/package.jsonpackages/dashboard/README.mdpackages/dashboard/*.config.*frontend/src/**frontend/package.jsonRespect the shared-package versus host-app boundary.
packages/dashboard/ is the source of truth for the dashboard product.self-hosting and cloud-hosting modes.frontend/.packages/dashboard/ depend on frontend/.Preserve dashboard data-flow conventions.
service -> hook -> UI.apiClient for HTTP calls so auth refresh and error handling stay consistent.Reuse the existing component layers.
@insforge/ui for generic primitives.packages/dashboard/.frontend/ when it is specific to the local self-hosting shell.Keep the package surface aligned with shared contracts.
@insforge/shared-schemas.packages/dashboard/src/index.ts and packages/dashboard/src/types aligned with the public package API.any type. Prefer precise prop, state, API, and hook result types.Use the lowest test layer that covers the risk. Add one focused regression test for bug fixes when practical.
| Change type | Test layer | Location | Command |
|---|---|---|---|
| Pure helper, parser, formatter, state reducer | Unit | packages/dashboard/src/**/__tests__/*.test.ts | npm --workspace @insforge/dashboard run test:unit |
| React component behavior, forms, dialogs, conditional rendering | Component | packages/dashboard/src/**/__tests__/*.test.tsx | npm --workspace @insforge/dashboard run test:component |
| Routing, auth redirects, host-mode integration, browser-only behavior | UI smoke | packages/dashboard/tests/ui/*.spec.ts | npm --workspace @insforge/dashboard run test:ui |
Conventions:
npm --workspace @insforge/dashboard run test runs the full Vitest suite: unit plus component..github/workflows/frontend-tests.yml. Update the workflow when adding or renaming test scripts.packages/dashboard/src/test/setup.ts. Mock hooks, services, and host context at the package boundary; assert user-visible behavior and callback effects, not implementation details or CSS class strings.frontend/ shell. Mock backend API routes in packages/dashboard/tests/ui/fixtures/; every mocked route must either fulfill, fallback, or abort. Do not leave requests pending after a test branch.Use when previewing UI gated on useIsCloudHostingMode(), isInsForgeCloudProject(), or a PostHog feature flag (e.g. the CTest dashboard variant, dashboard-v3-experiment === 'c_test', the CLI connect panel) while running the local frontend/ self-hosting shell.
The lowest-friction approach is to temporarily hardcode the three gates below to true/the new branch, then restart the Vite dev server. These edits bypass real host/project detection and MUST be fully reverted before committing — landing them breaks both self-hosting and cloud-hosting users.
packages/dashboard/src/lib/config/DashboardHostContext.tsx — useIsCloudHostingMode() → return true; (was useDashboardHost().mode === 'cloud-hosting').packages/dashboard/src/lib/utils/utils.ts — isInsForgeCloudProject() → return true; (was the .insforge.app hostname check).AppRoutes.tsx → const DashboardHomePage = CTestDashboardPage; and, if relevant, the matching branch in AppLayout.tsx for <ConnectDialogV2>.Mark every hardcode with a trailing // LOCAL DEBUG: <original expression> comment so revert is a mechanical search.
git grep -n "LOCAL DEBUG" packages/dashboard/src/ returns zero matches.mode === 'cloud-hosting' comparison, the hostname check, the getFeatureFlag(...) call must all be back).DashboardPage, getFeatureFlag, ConnectDialog) are restored.cd packages/dashboard && npm run lint && npm run typecheck both pass.git diff of the four files above shows only intended changes — no return true;, no missing imports.| Excuse | Reality |
|---|---|
| "I'll revert in a follow-up PR." | Follow-up = a window where prod is broken. Revert now. |
| "The original check was effectively the same." | If it were, you wouldn't have needed the hardcode. Restore the expression, not a value-equivalent. |
| "Lint passed, so the deleted import doesn't matter." | Lint passed because the import was deleted; on revert the original code needs it back. |
| "I'll ship the env-var override instead." | No env-var override is wired in the code. Don't invent one on the commit path — restore the original. |
cd packages/dashboard && npm run test:unit when changing pure helpers or reducerscd packages/dashboard && npm run test:component when changing React component behaviorcd packages/dashboard && npm run test:ui when changing routing, auth, host-mode integration, or browser-only behaviorcd packages/dashboard && npm run typecheckcd packages/dashboard && npm run buildcd frontend && npm run build when the local self-hosting shell changesFor shared contract changes, also validate packages/shared-schemas/ and the affected backend surface.