flowstate-epic-flowstate-apps-epicdm-flowstate-app-state
Package-local agent skill for @epicdm/flowstate-app-state.
Tags
Publisher
Versions
1 version published — latest: 1.0.0
- 1.0.0publishedInvalid Date
Skill
flowstate-app-state Package Skill
Package: @epicdm/flowstate-app-state
Repository: epic-flowstate-apps
Path: packages/flowstate-app-state
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 State App
Status: Active
Purpose: Maintain State app integration and route to registry or dashboard workflows.
Scope: packages/flowstate-app-state.
Trigger: Use when changing State plugin metadata, exports, pages, pipeline dashboard, or contribution registry.
Input: src/index.ts, src/plugin.ts, flowstate.plugin.json, touched registry/hook/page files.
Output: State app changes with drift and verification recorded.
Workflow
1. Check Plugin Drift
Compare flowstate.plugin.json and src/plugin.ts. JSON uses "State Inspector" and route /apps/state; source plugin names "State Management" and describes an executive dashboard.
2. Route To The Right Workflow
Use state-contribution-registry for registry/types changes. Use state-pipeline-snapshots for pipeline health, slots, and snapshot pages.
3. Maintain Public Exports
Keep src/index.ts exports aligned for StateRegistry, pipeline config, and contribution types.
Verification
Run yarn workspace @epicdm/flowstate-app-state typecheck and yarn workspace @epicdm/flowstate-app-state build. Record that test does not run StateRegistry.test.ts.
Composition
Composes with package skills for contributors such as Projects, which exports stateContribution.
Pitfalls
- Do not edit
.flowstate/dojo. - Do not describe placeholder snapshot pages as complete.
- Keep registry changes backward-compatible for contributors.
Done When
Plugin metadata, exports, registry/dashboard changes, and verification notes are aligned.
Package Skill Inventory
Package Skill Inventory: @epicdm/flowstate-app-state
Package Context
State has one reusable library-like surface (StateRegistry) and one dashboard workflow (pipeline health/snapshots).
Skill Map
| Skill | Type | Trigger | Teaches | Evidence | Depends On | Dojo |
|---|---|---|---|---|---|---|
flowstate-app-state | orchestrator | Maintaining State app package | Plugin, exports, pages, verification | src/index.ts, src/plugin.ts, flowstate.plugin.json | app framework | ready-after-review |
state-contribution-registry | reference | Adding or consuming state contributions | Registry API and contribution contracts | StateRegistry.ts, types/contribution.ts, test | state consumers | ready-after-review |
state-pipeline-snapshots | workflow | Changing pipeline health or snapshots | Pipeline slots, health hook, snapshot capture placeholders | config/pipeline-slots.ts, hooks, pages | RxDB/app framework | defer |
Anti-Sprawl Decision: Three skills separate app integration, registry contracts, and dashboard workflow.
Feature Coverage
| Feature Group | Source Evidence | Covered By | Notes |
|---|---|---|---|
| Plugin/app/exports | source and JSON plugin | flowstate-app-state | Description drift noted. |
| Registry | StateRegistry.ts, types, tests | state-contribution-registry | Strong reusable surface. |
| Pipeline/snapshots | hooks/pages/config | state-pipeline-snapshots | Some placeholder risk. |
Composition Model
Use orchestrator first. Use registry skill for package contribution contracts; use snapshot skill for dashboard UI/data flow.
Deferred Skills
- Snapshot detail/history deep skill deferred until pages load real snapshot data.
Review Questions
- Which product description is authoritative: state inspector or executive dashboard?
- When will snapshot pages load persisted data?
Review Gate
Package Skills Review: @epicdm/flowstate-app-state
Verdict
Pass with fixes
Findings
| Severity | Skill | Issue | Evidence | Required Fix |
|---|---|---|---|---|
| Important | state-pipeline-snapshots | Snapshot history/detail are placeholders. | Page comments/source text. | Defer deep snapshot skill until implemented. |
| Important | All | Test script does not run existing registry test. | package.json, StateRegistry.test.ts. | Fix script before publication. |
Coverage
| Feature Group | Status | Skill | Notes |
|---|---|---|---|
| Plugin/app | Covered | flowstate-app-state | Drift noted. |
| Registry | Covered | state-contribution-registry | Strong source evidence. |
| Pipeline/snapshots | Partial | state-pipeline-snapshots | Placeholder risk. |
Drift and Contract Risks
| Area | Risk | Evidence | Decision |
|---|---|---|---|
| Description | Inspector vs dashboard naming drift. | JSON/source plugin. | Record. |
| Tests | Existing test hidden. | package/test file. | Record. |
| Dojo | Generated prototype. | .flowstate/dojo/*. | Leave untouched. |
Dojo Publication Decision
Defer for state-pipeline-snapshots; registry skill is locally useful but publication should wait for test script repair.
Follow-Up Work
- Wire registry tests.
- Implement snapshot history/detail data loading or mark routes experimental.
Usage
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-state/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.
Install
Run this in your project to install via CLI:
fscloud dojo skill install flowstate-epic-flowstate-apps-epicdm-flowstate-app-state --target <target> --out ./skillsReplace <target> with your agent target identifier. See the CLI docs for details.