flowstate-dashboard Package Skill

Package: @epicdm/flowstate-dashboard Repository: flowstate-platform Path: packages/dashboard 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

Dashboard Billing

Status: Active Purpose: Keep billing UI, server actions, API clients, and route handlers aligned. Scope: Billing routes, billing components, and src/lib/billing. Trigger: Credit balance, usage, purchase, limit, auto top-up, payment, refund, or treasury changes. Input: Billing behavior and affected API/client surface. Output: Billing change with type-safe data flow.

Source Map

Pages: src/app/(cloud)/dashboard/billing/*, src/app/(cloud)/dashboard/admin/payments, refunds, treasury, wallets.
APIs: src/app/api/billing/auto-top-up/route.ts, limits/route.ts, usage-export/route.ts, checkout/proxy/route.ts.
Helpers: src/lib/billing/api.ts, actions.ts, format.ts, types.ts.
Components: src/components/billing/*, src/components/admin/*, src/components/wallet/*.

Workflow

Start with src/lib/billing/types.ts to confirm shapes and status values.
Route external requests through src/lib/billing/api.ts; keep components presentational where possible.
Use server actions in src/lib/billing/actions.ts for mutations.
Preserve formatting through src/lib/billing/format.ts.
For admin money movement, inspect admin components and pages together before editing.

Red Flags

Red Flag	Action
Component fetches billing endpoint directly	Move or reuse lib/API helper
New status string appears outside `types.ts`	Add or reuse typed union
Money/credit formatting duplicated	Use `format.ts`

Created: 2026-06-30

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-dashboard

Review date: 2026-06-30

Skill	Type	Use When	Source Anchors
`flowstate-dashboard-cloud`	Orchestrator	Working on the Cloud dashboard, tenant provisioning, teams, admin, auth, or package verification	`src/app/(cloud)`, `src/lib/cloud`, `src/lib/auth`, `src/db/schema.ts`
`flowstate-dashboard-billing`	Workflow	Changing credit balance, usage, purchases, auto top-up, limits, admin payments, or billing APIs	`src/lib/billing`, `src/components/billing`, `src/app/api/billing`
`flowstate-dashboard-dojo`	Workflow	Changing Dojo catalog, course learning, review queue, audit, enroll, checkout, or lesson rendering	`src/app/(cloud)/dojo`, `src/app/api/dojo`, `src/components/dojo`, `src/lib/dojo/api.ts`

Composition Notes

Load flowstate-dashboard-cloud first for app boundaries. Add billing or Dojo skills when the change touches those subdomains.

Review Gate

Package Skills Review: @epicdm/flowstate-dashboard

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

Checks

Skills are grounded in route groups, lib directories, schema, package scripts, and docs.
Skills avoid enumerating hundreds of schema exports as independent features.
Files were written only under packages/dashboard/.flowstate/skills.

Pressure Scenario

Scenario: "Add a dashboard page that shows tenant usage and billing warnings."

Expected behavior with skills: load flowstate-dashboard-cloud and flowstate-dashboard-billing; use src/lib/cloud/queries.ts, billing API helpers, existing billing components, schema enums, and typecheck verification.

Remaining Risk

No package-local test script exists. Agents should rely on typecheck, build when safe, and focused manual/source review for integrations.

flowstate-flowstate-platform-epicdm-flowstate-dashboard

Tags

Publisher

Versions

Skill