worker-dashboard-api Package Skill

Package: @epicdm/worker-dashboard-api Repository: flowstate-platform Path: packages/worker-dashboard-api Version: 0.0.1

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

Primary Package Workflow

Dashboard API Worker

Status: Active Purpose: Add dashboard API behavior while preserving route-local auth and OpenAPI contracts. Scope: packages/worker-dashboard-api Trigger: Route, schema, DB, auth, or scheduled-handler changes. Input: Endpoint path, auth requirement, Zod schema, DB or downstream dependency. Output: Route implementation, schema updates, and tests.

Workflow

1. Start at src/index.ts to confirm where the route group is mounted.
2. For authenticated user routes, apply requireAuth() inside the route module.
3. Define request/response schemas under src/schemas/ and use createRoute for OpenAPI routes.
4. Use getDb(c.env.DB) for dashboard D1 access.
5. Add tests under test/routes, test/lib, or test/middleware matching the changed layer.
6. Regenerate OpenAPI with yarn workspace @epicdm/worker-dashboard-api generate:openapi when route schema changes.

Verification

• Run yarn workspace @epicdm/worker-dashboard-api test.
• Run yarn workspace @epicdm/worker-dashboard-api typecheck.

Package Skill Inventory

Skill Inventory: @epicdm/worker-dashboard-api

Package Role

@epicdm/worker-dashboard-api provides dashboard profile, billing proxy, checkout, cloud management, onramp, media, email webhook, and cron APIs.

Skills

Composition Notes

• Compose with @epicdm/flowstate-api-core patterns for createApiApp, ok, err, and auth.
• Compose billing work with payment API contracts.
• Keep public/media and webhook auth separate from user JWT auth.

Review Gate

Review Gate: @epicdm/worker-dashboard-api Skills

Result

Pass.

Checks

• Skills are backed by worker entrypoint, routes, middleware, library code, and tests.
• Per-route auth and public/webhook/cron boundaries are explicit.
• Verification commands are package-local.

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