flowstate-templates Package Skill

Package: @epicdm/flowstate-templates Repository: epic-flowstate-community Path: packages/flowstate-templates Version: 1.0.8

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

Primary Package Workflow

Adding Template Business Types

Status: Active Purpose: Add or update built-in business categories without breaking registry behavior or type coverage. Scope: packages/flowstate-templates/src/business-types Trigger: A task adds a new category or materially changes an existing bundle. Input: Business category definition and domain data. Output: Registered, tested TemplateBundle.

Existing Layout

Each category folder contains:

agents.ts
bizplan.ts
content.ts
finance.ts
index.ts
marketing.ts
operations.ts
product.ts

index.ts composes a TemplateBundle and calls registerBundle(bundle).

Add Or Change Workflow

1. Update or create domain files using types from src/types.ts.
2. Compose the bundle in the category index.ts.
3. Call registerBundle(bundle) in that index.ts.
4. Export/import the category from src/business-types/index.ts.
5. If adding a new category, update BusinessCategory.
6. Add or update business-specific tests and all-bundles expectations.
7. Check finance journal balancing and domain minimums.
8. Run package gates.

Red Flags

Verification

yarn workspace @epicdm/flowstate-templates test
yarn workspace @epicdm/flowstate-templates typecheck
yarn workspace @epicdm/flowstate-templates lint

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-templates

Review date: 2026-06-30

Skill Map

Feature Coverage

Composition Notes

• Use FlowState bizplan/product/finance/domain skills when converting templates into persisted FlowState records.
• This package supplies seed data and contracts; it does not create database records by itself.

Review Gate

Package Skill Review: @epicdm/flowstate-templates

Review date: 2026-06-30 Verdict: pass

Quality Gate

• Source-backed package purpose: pass.
• Public entry points documented: pass.
• Composable skill map: pass.
• Generated Dojo weaknesses called out: pass.
• Dojo publish readiness: deferred until generated artifacts are rebuilt from reviewed skills.

Evidence Checked

• package.json
• README.md
• src/index.ts
• src/registry.ts
• src/types.ts
• src/business-types/index.ts
• representative bundle indexes
• src/__tests__/registry.test.ts
• src/__tests__/all-bundles.test.ts
• src/__tests__/types.test.ts
• scripts/generate-json.ts
• .flowstate/feature-matrix/inventory.md
• .flowstate/dojo/agent-skillset.md

Verification Results

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

Results:

• ASCII/frontmatter check passed.
• test --runInBand passed: 8 suites, 185 tests.
• typecheck passed.
• lint passed with 197 existing warnings, all test non-null assertions.
• build passed.
• nx build passed and built/cached dependent tasks for flowstate-crypto and flowstate-collections; existing Nx Cloud 401/unconnected workspace notice reported.

Dojo Status

Deferred. Existing generated Dojo artifacts should be rebuilt from these reviewed local skills because they split package internals into per-constant skilllets, include generic course language, and have ID/publisher drift.

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