flowstate-app-support Package Skill

Package: @epicdm/flowstate-app-support Repository: epic-flowstate-apps Path: packages/flowstate-app-support 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 Support App

Status: Active Purpose: Keep Support app changes aligned with host integration. Scope: packages/flowstate-app-support. Trigger: Use when changing support routing, plugin metadata, dashboard surfaces, exports, or multiple support domains. Input: src/plugin.ts, src/index.ts, src/App.tsx, flowstate.plugin.json, touched hooks/components. Output: A support package change with source-backed verification notes.

Workflow

1. Confirm Plugin Metadata

Check supportPlugin for id support, route /apps/support, category business, and base path /support. Cross-check sidebar links in flowstate.plugin.json.

2. Choose A Data Workflow

Use support-record-crud for tickets, KB articles, or feedback. Use support-health-integrations for health scores or integrations.

3. Decide Public Export Scope

src/index.ts currently exports only the plugin, app, props, and version. If downstream code needs hooks or schemas, add explicit exports and verify.

Verification

Run yarn workspace @epicdm/flowstate-app-support typecheck and yarn workspace @epicdm/flowstate-app-support build. Record that the current test script does not run the package's hook tests.

Composition

Composes with @epicdm/flowstate-collections model contracts and app-framework database/org hooks.

Pitfalls

• Do not edit .flowstate/dojo.
• Do not assume support.newTicket is implemented as a command handler inside this package.
• Keep route/basePath/sidebar paths consistent.

Done When

Plugin metadata, manifest links, exports, touched data workflow, and verification notes are aligned.

Package Skill Inventory

Package Skill Inventory: @epicdm/flowstate-app-support

Package Context

Support has repeated collection-hook workflows. The skillset groups those by operational purpose rather than creating one skill for each collection.

Skill Map

Anti-Sprawl Decision: Three skills cover app integration and the two recurring support data workflows.

Feature Coverage

Composition Model

Use the orchestrator first. Use one workflow skill for the affected data domain, then return to orchestrator for exports and verification.

Deferred Skills

• Dashboard metrics skill deferred until dashboard calculations become explicit services.
• Command skill deferred until support.newTicket has source handler evidence.

Review Questions

• Should src/index.ts export hooks and schemas for downstream use?
• Should the package test script run hook tests?

Review Gate

Package Skills Review: @epicdm/flowstate-app-support

Verdict

Pass with fixes

Findings

Coverage

Drift and Contract Risks

Dojo Publication Decision

Defer until test script and export intent are clarified.

Follow-Up Work

• Wire Jest/Vitest script to existing hook tests.
• Decide which hooks/schemas belong in src/index.ts.

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