InsForge Dev Dashboard

Use this skill for dashboard work in the InsForge repository.

Scope

• packages/dashboard/src/**
• packages/dashboard/package.json
• packages/dashboard/README.md
• packages/dashboard/*.config.*
• frontend/src/**
• frontend/package.json

Working Rules

1. Respect the shared-package versus host-app boundary.

   • This dashboard is built with React and TypeScript.
   • packages/dashboard/ is the source of truth for the dashboard product.
   • The package must support both self-hosting and cloud-hosting modes.
   • Keep self-hosting-only bootstrap, local env defaults, and shell styling in frontend/.
   • Do not let packages/dashboard/ depend on frontend/.
   • If both modes need a capability, define it in the package API first.

2. Preserve dashboard data-flow conventions.

   • Follow the flow service -> hook -> UI.
   • Use apiClient for HTTP calls so auth refresh and error handling stay consistent.
   • Put request logic in services, data fetching and mutation state in hooks, and rendering/orchestration in UI components and pages.
   • Reuse existing contexts, host abstractions, and hooks before creating new global state.

3. Reuse the existing component layers.

   • Use @insforge/ui for generic primitives.
   • Use shared dashboard components when the pattern is already present.
   • Keep reusable dashboard UI in packages/dashboard/.
   • Only add UI to frontend/ when it is specific to the local self-hosting shell.
   • Keep package styles scoped to the dashboard container.