flowstate-epic-flowstate-apps-epicdm-flowstate-app-shell
Package-local agent skill for @epicdm/flowstate-app-shell.
Tags
Publisher
Versions
1 version published — latest: 1.0.0
- 1.0.0publishedInvalid Date
Skill
flowstate-app-shell Package Skill
Package: @epicdm/flowstate-app-shell
Repository: epic-flowstate-apps
Path: packages/flowstate-app-shell
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 Shell App
Status: Active
Purpose: Maintain Shell app integration and route agents to terminal workflows.
Scope: packages/flowstate-app-shell.
Trigger: Use when changing Shell plugin metadata, exports, manifests, pages, or terminal surfaces.
Input: src/index.ts, src/plugin.ts, src/manifest.ts, flowstate.plugin.json, touched hook/component.
Output: Shell app changes aligned with host and terminal packages.
Workflow
1. Check Plugin And Manifests
Compare shellPlugin, shellManifest, and flowstate.plugin.json for commands, route /apps/shell, and base path /shell.
2. Pick Terminal Workflow
Use shell-terminal-sessions for generic integrated terminal behavior. Use shell-agent-terminal for /agent/:agentId style behavior and agent server lookup.
3. Maintain Public Exports
src/index.ts exports many components, pages, hooks, and bottom panel renderers. Update exports when adding public terminal surfaces.
Verification
Run yarn workspace @epicdm/flowstate-app-shell typecheck and yarn workspace @epicdm/flowstate-app-shell build. Record that package test does not run existing tests.
Composition
Composes with @epicdm/flowstate-shell, flowstate-shell-core, and flowstate-shell-server package skills.
Pitfalls
- Do not edit
.flowstate/dojo. - Do not claim manifest command behavior without handler evidence.
- Keep terminal runtime assumptions in hooks/components, not plugin metadata.
Done When
Plugin, manifests, exports, workflow-specific code, and verification notes agree.
Package Skill Inventory
Package Skill Inventory: @epicdm/flowstate-app-shell
Package Context
Shell has two real workflows: integrated terminal sessions and agent-specific terminal pages.
Skill Map
| Skill | Type | Trigger | Teaches | Evidence | Depends On | Dojo |
|---|---|---|---|---|---|---|
flowstate-app-shell | orchestrator | Maintaining Shell app package | Plugin, manifest, exports, verification | src/index.ts, src/plugin.ts, src/manifest.ts, flowstate.plugin.json | shell packages | ready-after-review |
shell-terminal-sessions | workflow | Changing integrated terminal tabs/sessions | Session hooks, components, bottom panel renderers | useTerminalSessions.ts, IntegratedTerminalTab.tsx, bottomPanelRenderers.ts | flowstate-shell | ready-after-review |
shell-agent-terminal | workflow | Changing agent terminal page/hook | Agent id routing, server URL fallback, tests | AgentTerminalPage.tsx, useAgentTerminal.ts, tests | flowstate-shell-server | ready-after-review |
Anti-Sprawl Decision: Three skills match the package's two terminal workflows plus app integration.
Feature Coverage
| Feature Group | Source Evidence | Covered By | Notes |
|---|---|---|---|
| Plugin/manifest/exports | source and JSON manifests | flowstate-app-shell | Metadata/commands. |
| Integrated terminal | hooks/components/renderers | shell-terminal-sessions | Bottom panel integration. |
| Agent terminal | page/hook/tests | shell-agent-terminal | Tests exist but script drift. |
Composition Model
Use orchestrator first, then a workflow skill based on whether the change targets a generic terminal or agent terminal.
Deferred Skills
- Settings skill deferred; settings page is not a separate source-backed workflow yet.
Review Questions
- Should package test script run existing Jest tests?
- Which manifest source is authoritative for shell commands?
Review Gate
Package Skills Review: @epicdm/flowstate-app-shell
Verdict
Pass with fixes
Findings
| Severity | Skill | Issue | Evidence | Required Fix |
|---|---|---|---|---|
| Important | All | Existing tests are hidden by package test script. | package.json; test files under src. | Fix script before Dojo publication. |
Coverage
| Feature Group | Status | Skill | Notes |
|---|---|---|---|
| Plugin/manifests/exports | Covered | flowstate-app-shell | Source-backed. |
| Integrated terminal | Covered | shell-terminal-sessions | Renderer/session workflow. |
| Agent terminal | Covered | shell-agent-terminal | Tests identified. |
Drift and Contract Risks
| Area | Risk | Evidence | Decision |
|---|---|---|---|
| Tests | Tests exist but script says no tests. | package/test files. | Record. |
| Dojo | Generated prototype. | .flowstate/dojo/*. | Leave untouched. |
Dojo Publication Decision
Defer until test script is repaired or publication marks verification limits.
Follow-Up Work
- Wire tests into package script.
- Reconcile command declarations with source handlers.
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-shell/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-shell --target <target> --out ./skillsReplace <target> with your agent target identifier. See the CLI docs for details.