flowstate-dashboard Package Skill

Package: @epicdm/flowstate-dashboard Repository: epic-flowstate-community Path: packages/flowstate-dashboard Version: 1.0.0

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

FlowState Dashboard Component Registry

Status: Active Purpose: Register and validate dashboard component ids and manifests. Scope: src/components, src/manifests, src/engine/ComponentResolver.ts. Trigger: Component id changes, new built-in components, plugin component registration, missing component fallback. Input: Component id, React component, component manifest. Output: Resolver and manifest registration that match runtime config ids.

First-Party Registration

Use registerFirstPartyComponents(resolver) to register 64 built-ins:

• Layouts
• Views and interactive views
• UI/domain UI
• Navigation
• Form fields and form panel
• Actions
• Collaboration
• Time tracking

First-party ids use colon form, for example fs:data-table, fs:grid, and fs:timer-control.

Resolver Behavior

ComponentResolver.resolve(id) checks:

1. Exact id
2. Legacy conversion from : to .
3. Missing component fallback

Registering an id twice overwrites the previous component, which is the intended override path.

Manifests

allManifests and category arrays describe the built-in components for discovery and plugin metadata. Keep component implementation, registration id, and manifest id aligned.

Verification

yarn workspace @epicdm/flowstate-dashboard test --runTestsByPath packages/flowstate-dashboard/tests/engine/component-resolver.test.ts packages/flowstate-dashboard/tests/manifests.test.ts packages/flowstate-dashboard/tests/ui-components.test.tsx

Created: 2026-06-30

Package Skill Inventory

@epicdm/flowstate-dashboard Skill Inventory

These skills group the 80 feature inventory entries into agent workflows rather than teaching each component as an isolated fact.

Review Gate

@epicdm/flowstate-dashboard Skill Review

Created package-local skills for the dashboard system under packages/flowstate-dashboard/.flowstate/skills.

Evidence Reviewed

• package.json
• src/index.ts
• src/sdk/index.ts
• src/dev-tools/index.ts
• src/providers/DashboardProvider.tsx
• src/engine/DashboardRenderer.tsx
• src/engine/ComponentResolver.ts
• src/engine/DataSourceManager.ts
• src/engine/ActionSystem.ts
• src/engine/FormEngine.ts
• src/engine/InteractionWiring.ts
• src/engine/HookCompiler.ts
• src/plugin/DashboardPlugin.ts
• src/components/index.ts
• src/engine/TemplateManager.ts
• src/seeding/seedBuiltInDashboards.ts
• src/hooks/useDashboards.ts
• .flowstate/feature-matrix/inventory.md
• .flowstate/dojo/agent-skillset.md

Review Notes

• This is a real exported TypeScript/React package, not a manifest-only connector.
• The feature inventory detects many components but does not teach the runtime composition model.
• Package skills emphasize how config, provider, data sources, resolver, renderer, SDK, templates, and plugin lifecycle work together.
• Interaction wiring and hook compilation are part of the data/action skill path.
• Generated Dojo ids drift between skill.yaml and sync-state.json; publish state is not the same as content quality.

Verification Status

• ASCII scan passed: no non-ASCII characters in .flowstate/skills.
• Skill frontmatter scan passed for all 8 SKILL.md files.
• yarn workspace @epicdm/flowstate-dashboard typecheck passed.
• yarn workspace @epicdm/flowstate-dashboard build passed; tsup warned that useMemo is imported from React but unused in built SDK output.
• yarn workspace @epicdm/flowstate-dashboard test --runInBand passed: 82 suites, 1680 tests; tests emitted expected react-test-renderer deprecation warnings.
• yarn nx build @epicdm/flowstate-dashboard passed; Nx Cloud reported the existing unconnected-workspace 401 notice and the same tsup warning.
• yarn workspace @epicdm/flowstate-dashboard lint passed with 145 warnings, including existing React hook/ref warnings in DashboardProvider, hook dependency warning in InteractiveDataTable, and many test non-null assertions.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/flowstate-dashboard/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.