flowstate-extension-api Package Skill

Package: @epicdm/flowstate-extension-api Repository: epic-flowstate-community Path: packages/extension-sdk Version: 1.1.6

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

Primary Package Workflow

Extension API Build And Release

Status: Active Purpose: Preserve the SDK's two-entry build and publication boundary. Scope: package.json, tsup.config.ts, README, changelog, .flowstate artifacts. Trigger: A change affects exports, bundled dependencies, versioning, generated docs, or release readiness. Input: Changed source/build/docs files. Output: Verified package build and updated drift notes.

Build Contract

tsup.config.ts builds:

• index from src/index.ts
• testing/index from src/testing/index.ts

Both build CJS, ESM, and DTS output.

Dependency Boundary

• @epicdm/flowstate-app-framework is bundled with noExternal so extension authors depend only on the SDK.
• react and react-dom stay external.
• Keep the peer dependency at react >=18.0.0 unless the public author contract changes.

Drift Checks

• package.json version is the release authority.
• CHANGELOG.md currently lags package version.
• README examples are placeholders and should be made concrete when API examples are updated.
• Existing .flowstate/dojo files are generated prototypes and should be rebuilt from reviewed local skills.

Verification

yarn workspace @epicdm/flowstate-extension-api test
yarn workspace @epicdm/flowstate-extension-api typecheck
yarn workspace @epicdm/flowstate-extension-api build

Red Flags

• Build output missing testing/index.
• SDK examples import from @epicdm/flowstate-app-framework/extensions.
• Dojo artifacts are published from generated package summaries.
• Version bumps skip changelog or package-local review notes.

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-extension-api

Package path: packages/extension-sdk

Skill Map

Why This Split

The package is intentionally thin. The useful agent knowledge is not a long feature list; it is knowing the facade contract, the testing harness, and the build boundary that keeps extension authors decoupled from flowstate-app-framework.

Publication Notes

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

Review Gate

Package Skill Review: @epicdm/flowstate-extension-api

Package path: packages/extension-sdk

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 intentionally compact because the package is a facade plus testing harness, not a runtime app or CLI.

Checks

• Source review: completed from package metadata, source exports, tests, README, changelog, feature matrix, generated Dojo artifacts, and package review subagent output.
• Skill inventory: completed.
• Skill files: completed.
• Verification: completed.
• 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-extension-api test
yarn workspace @epicdm/flowstate-extension-api typecheck
yarn workspace @epicdm/flowstate-extension-api build

Results:

• ASCII validation passed for .flowstate/skills.
• typecheck passed.
• test --runInBand passed: 2 suites, 15 tests.
• build passed for root and testing/index CJS, ESM, and DTS outputs.

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