flowstate-app-framework Package Skill

Package: @epicdm/flowstate-app-framework Repository: epic-flowstate-community Path: packages/flowstate-app-framework 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

FlowState App Framework App Shell

Status: Active Purpose: Guide app container and shell composition changes. Scope: App containers, shell surfaces, command/palette/menu/keybinding/navigation/quicknav/RPC systems. Trigger: Work touches FlowstateAppContainer, host shell UI, command surfaces, navigation, or RPC. Input: Target UI workflow, routing context, and command/shell behavior. Output: Shell changes that compose with framework services and tests.

Source Map

• src/components/FlowstateAppContainer.tsx, FlowstateAppProvider, FlowstateAppLayout.
• src/components/shell, src/components/statusbar, src/components/settings, src/components/common.
• src/commands, src/palette, src/menus, src/keybindings.
• src/navigation, src/quicknav, src/rpc.
• src/container, src/contexts, src/hooks.

Workflow

1. Decide whether the change is container-level, shell UI, command surface, navigation, or RPC.
2. Follow existing provider/context patterns instead of passing global state through ad hoc props.
3. Register commands/menus/palette entries together when a workflow needs discoverability.
4. Keep app links and prefixed navigation compatible with embedded app paths.
5. Add or update focused component/hook tests.

Guardrails

• Do not use visible UI text to document internal behavior.
• Keep shell controls ergonomic and consistent with existing framework components.
• Avoid changing command ids casually; downstream apps may persist or reference them.
• Shared UI exports can ripple through @epicdm/flowstate-ui.

Verification

yarn workspace @epicdm/flowstate-app-framework test -- src/components src/commands src/palette src/menus src/navigation src/quicknav src/rpc
yarn workspace @epicdm/flowstate-app-framework typecheck

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-app-framework

Package path: packages/flowstate-app-framework.

Skillset

Composition Notes

• Use plugin runtime before changing app host integration.
• Use data/auth together with app shell when UI components depend on injected context.
• Use onboarding subpath skill before changing CLI consumers such as flowstate-cli.
• Use connector-core skills when app-framework work touches connector UI/runtime re-exports.

Publication Readiness

Status: drafted, pending verification.

Before Dojo publication, rebuild package Dojo artifacts from this reviewed skillset.

Review Gate

Package Skill Review: @epicdm/flowstate-app-framework

Package path: packages/flowstate-app-framework.

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 workflow-shaped around public import boundaries, plugin/host runtime, app shell composition, data/auth context, and CLI-safe onboarding.

Checks

• Source review: completed from package review agent output, package metadata, export map, main barrel, source directory map, docs/version drift, and generated artifact drift.
• Skill inventory: completed.
• Skill files: completed.
• Verification: completed with known package quality findings below.
• Generated Dojo replacement: deferred; existing .flowstate/dojo files are generated prototypes.
• Cloud Dojo publication: deferred until Dojo skill/course manifests are rebuilt from the reviewed local skills.

Verification Commands

Verification completed before publication:

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

Results:

• ASCII validation passed for .flowstate/skills.
• typecheck passed.
• test passed: 239 suites, 3920 tests, 1 snapshot.
• build passed after dependent package declarations were built.
• yarn nx build @epicdm/flowstate-app-framework passed and built required dependencies first.
• lint failed with 12 existing errors: import ordering in document components and one prefer-template issue in src/components/documents/DocumentEditorSurface.tsx.
• Build emitted existing DTS warnings for ambiguous @epicdm/connector-core versus @epicdm/connector-core/react re-exports in src/sync/index.ts, plus an unused ObservabilityClient DTS warning.
• Nx reported the existing unconnected-workspace 401 from Nx Cloud.

Publication Gate

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