flowstate-docs Package Skill

Package: @epicdm/flowstate-docs Repository: flowstate-platform Path: packages/docs Version: 0.1.0

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

Primary Package Workflow

Docs Agent Routes

Status: Active Purpose: Preserve predictable documentation output for agents. Scope: src/app/agent/[slug]/route.ts and src/agent. Trigger: Agent docs route, slug resolution, response format, or machine-readable docs changes. Input: Documentation slug and expected consumer behavior. Output: Stable agent-readable docs route behavior.

Workflow

1. Inspect src/app/agent/[slug]/route.ts before changing response shape.
2. Keep route output simple for machine consumers.
3. Reuse synced/generated docs data instead of duplicating content lookup logic.
4. Update tests or add route-level checks when response status or payload shape changes.
5. Run typecheck and package tests.

Created: 2026-06-30

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-docs

Review date: 2026-06-30

Composition Notes

Use the site skill first, then navigation/search or agent-routes for specialized changes.

Review Gate

Package Skills Review: @epicdm/flowstate-docs

Review date: 2026-06-30 Status: Pass for local agent use

Checks

• Skills cite package scripts, sync script, route, navigation, section, search, and component surfaces.
• Skills avoid generic documentation-site advice and focus on this package's generated-doc workflow.
• Files were written only under packages/docs/.flowstate/skills.

Pressure Scenario

Scenario: "Add a generated docs section and ensure it appears in site navigation and agent docs."

Expected behavior with skills: load flowstate-docs-site, then navigation/search and agent-routes skills; update sync outputs/types and route behavior, run docs:sync, typecheck, and tests.

Remaining Risk

docs:sync may update generated docs outside .flowstate/skills; this authoring pass did not run it because the task forbids unrelated generated file changes.

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