flowstate-ui Package Skill

Package: @epicdm/flowstate-ui Repository: epic-flowstate-community Path: packages/flowstate-ui Version: 1.0.7

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

Primary Package Workflow

FlowState UI Build Maintenance

Status: Active Purpose: Keep @epicdm/flowstate-ui publishable, correctly exported, and aligned with package-local documentation. Scope: package.json, tsup.config.ts, src/index.ts, component barrels, docs, tests, and .flowstate artifacts. Trigger: A change affects public exports, package dependencies, build output, README/changelog, generated declarations, or Dojo publication readiness. Input: Changed source, package metadata, docs, or generated artifacts. Output: Verified build outputs and updated package review notes.

Export Checklist

When adding a public component:

1. Add the component file under the right source group.
2. Export it from src/components/ui/index.ts or src/components/chat/index.ts.
3. Confirm src/index.ts re-exports that group.
4. Run yarn workspace @epicdm/flowstate-ui build to regenerate DTS output.
5. Verify downstream imports use @epicdm/flowstate-ui.

Build Contract

• build runs clean, tsup, then build:dts.
• build:dts uses dts-bundle-generator with Radix and CVA external inlines.
• Package outputs include ESM/CJS declarations and JS bundles under dist.
• files includes both dist and src; do not rely on src being a public import contract.

Dependency And Packaging Risks

• Runtime component imports must be in package dependencies or peerDependencies.
• KanbanBoard imports @dnd-kit/core and @dnd-kit/utilities; these are currently devDependencies and should be reviewed before publish-sensitive changes.
• React and React DOM are exact peer dependencies at 19.2.0.
• lucide-react appears in both dependencies and peer dependencies with different ranges; review before changing icon usage.

Docs And Dojo Drift

• README still uses old @epic-flow/flowstate-ui examples. Use @epicdm/flowstate-ui in skills and future docs.
• README peer dependency examples lag package.json.
• CHANGELOG.md lags package version.
• Existing .flowstate/dojo artifacts are generated prototypes and should be rebuilt from reviewed .flowstate/skills.

Verification

yarn workspace @epicdm/flowstate-ui typecheck
yarn workspace @epicdm/flowstate-ui test
yarn workspace @epicdm/flowstate-ui lint
yarn workspace @epicdm/flowstate-ui build
yarn nx build @epicdm/flowstate-ui
rg -n "@epic-flow|@epicdm" packages/flowstate-ui

Red Flags

• Passing only the lone Button test and claiming broad component coverage.
• Publishing generated Dojo skilllets as final skills.
• Editing chat syntax highlighting without CJS consumer verification.
• Adding source subpath imports to app examples.

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-ui

Package path: packages/flowstate-ui

Skill Map

Why This Split

The generated feature inventory lists individual components and helpers, but agents need workflow-level guidance: base primitives, FlowState-specific composites, chat surfaces, and build/export maintenance. This split keeps the package teachable without one skill per component.

Publication Notes

• Existing .flowstate/dojo files are generated prototypes.
• Rebuild Dojo artifacts from reviewed skills before publishing.

Review Gate

Package Skill Review: @epicdm/flowstate-ui

Package path: packages/flowstate-ui

Review Result

Status: source-backed and verified for local package-skill use; Dojo publication deferred until reviewed skill content is packaged for the Dojo API.

The skillset is organized around UI workflow groups: package entry points, primitives, FlowState composites, chat components, and build/export maintenance.

Checks

• Source review: completed from package metadata, root barrels, representative UI/chat components, docs, feature matrix, generated Dojo artifacts, inbound references, and package review subagent output.
• Skill inventory: completed.
• Skill files: completed.
• Verification: completed with lint and DTS warnings below.
• Generated Dojo replacement: deferred; existing .flowstate/dojo files are generated prototypes.
• Cloud Dojo publication: deferred until reviewed skills are packaged into Dojo manifests.

Verification Commands

Verification completed before publication:

yarn workspace @epicdm/flowstate-ui typecheck
yarn workspace @epicdm/flowstate-ui test
yarn workspace @epicdm/flowstate-ui lint
yarn workspace @epicdm/flowstate-ui build
yarn nx build @epicdm/flowstate-ui

Results:

• ASCII validation passed for .flowstate/skills.
• typecheck passed.
• test --runInBand passed: 1 suite, 4 tests.
• build passed.
• yarn nx build @epicdm/flowstate-ui passed and reported the existing Nx Cloud setup notice.
• lint failed with 13 errors and 148 warnings. Errors are mostly sort-imports in chart/cross-entity components and unnecessary non-null assertions in DataTable and KanbanBoard; warnings include missing explicit return types, any/unsafe Recharts payload usage, and non-null assertions.
• build and nx build emitted dts-bundle-generator warnings that ClassValue and Toast type nodes were renamed due to name collisions and will not be exported from the generated bundle.

Publication Gate

Do not publish generated .flowstate/dojo artifacts until they are rebuilt from reviewed package skills.

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-ui/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.