flowstate-epic-flowstate-apps-epicdm-flowstate-app-servers
Package-local agent skill for @epicdm/flowstate-app-servers.
Tags
Publisher
Versions
1 version published — latest: 1.0.0
- 1.0.0publishedInvalid Date
Skill
flowstate-app-servers Package Skill
Package: @epicdm/flowstate-app-servers
Repository: epic-flowstate-apps
Path: packages/flowstate-app-servers
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 Servers App
Status: Active
Purpose: Keep server-management app changes aligned with host loading.
Scope: packages/flowstate-app-servers.
Trigger: Use when changing Servers app routing, plugin metadata, page behavior, or server connection UI.
Input: src/plugin.ts, src/index.ts, src/ServersApp.tsx, src/pages/ServersPage.tsx, flowstate.plugin.json.
Output: A Servers package change with metadata drift handled explicitly.
Workflow
1. Compare Metadata Sources
Check both src/plugin.ts and flowstate.plugin.json. Existing drift exists: JSON uses category settings and amber color while source plugin uses category technical and green color.
2. Route To The Right Skill
Use servers-connection-management for add/edit/delete/test/sync behavior. Use servers-manifest-contract for commands, keybindings, sidebar, permissions, or metadata changes.
3. Verify Host Loading
Keep serversPlugin.component lazy-loading ServersApp, and preserve config.basePath: '/servers'.
Verification
Run yarn workspace @epicdm/flowstate-app-servers typecheck and yarn workspace @epicdm/flowstate-app-servers build. The package test script currently reports no tests.
Composition
Composes with app-framework server configuration APIs, especially useServerConfig and ServerConfigDialog.
Pitfalls
- Do not edit
.flowstate/dojo. - Record the dev-port collision with Todo if running dev servers.
- Do not claim command behavior is implemented solely from manifest entries.
Done When
Source plugin, JSON manifest, page behavior, and verification notes are aligned or documented as drift.
Package Skill Inventory
Package Skill Inventory: @epicdm/flowstate-app-servers
Package Context
Servers is mostly a framework-backed admin UI. Skills should teach how to work with ServersPage and how to avoid manifest/plugin drift.
Skill Map
| Skill | Type | Trigger | Teaches | Evidence | Depends On | Dojo |
|---|---|---|---|---|---|---|
flowstate-app-servers | orchestrator | Maintaining Servers package | App/plugin routing and verification | src/index.ts, src/plugin.ts, flowstate.plugin.json | app framework | ready-after-review |
servers-connection-management | workflow | Changing server add/edit/delete/test flows | useServerConfig workflow in page UI | src/pages/ServersPage.tsx | app framework server config | ready-after-review |
servers-manifest-contract | reference | Changing server commands, keybindings, or sidebar | Manifest/source drift and host contract | flowstate.plugin.json, src/plugin.ts | app framework | ready-after-review |
Anti-Sprawl Decision: Three skills cover the package; there are no package-local persistence services to split further.
Feature Coverage
| Feature Group | Source Evidence | Covered By | Notes |
|---|---|---|---|
| Plugin/app | src/plugin.ts, src/index.ts | flowstate-app-servers | Metadata drift noted. |
| Server config UI | ServersPage.tsx | servers-connection-management | Uses framework hook. |
| Commands/sidebar | flowstate.plugin.json | servers-manifest-contract | Manifest-heavy behavior. |
Composition Model
Use orchestrator, then connection workflow for page behavior or manifest reference for host contributions.
Deferred Skills
- Login workflow skill deferred because
LoginPage.tsxis light and command navigation depends on host auth.
Review Questions
- Which metadata source is authoritative:
src/plugin.tsorflowstate.plugin.json? - Should Todo or Servers change port?
Review Gate
Package Skills Review: @epicdm/flowstate-app-servers
Verdict
Pass with fixes
Findings
| Severity | Skill | Issue | Evidence | Required Fix |
|---|---|---|---|---|
| Important | servers-manifest-contract | Source plugin and JSON manifest drift on category/color/description. | src/plugin.ts, flowstate.plugin.json. | Reconcile before publishing. |
| Minor | All | No package tests. | package.json. | Add tests for ServersPage framework interactions. |
Coverage
| Feature Group | Status | Skill | Notes |
|---|---|---|---|
| Plugin/app | Covered | flowstate-app-servers | Drift called out. |
| Connection management | Covered | servers-connection-management | Framework-backed workflow. |
| Manifest commands | Covered | servers-manifest-contract | Host contribution caveat. |
Drift and Contract Risks
| Area | Risk | Evidence | Decision |
|---|---|---|---|
| Metadata | Host may read different category/color depending source. | Source and JSON. | Defer fix; record. |
| Port | Collides with Todo. | package scripts. | Record. |
| Dojo | Generated prototype. | .flowstate/dojo/*. | Leave untouched. |
Dojo Publication Decision
Defer until metadata drift is resolved.
Follow-Up Work
- Reconcile plugin JSON and source plugin.
- Add tests for server config workflows.
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-servers/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-servers --target <target> --out ./skillsReplace <target> with your agent target identifier. See the CLI docs for details.