atomic

flowstate-flowstate-platform-epicdm-worker-dojo-api

Package-local agent skill for @epicdm/worker-dojo-api.

Tags

Publisher

Versions

1 version published — latest: 0.1.0

  • 0.1.0
    publishedInvalid Date

Skill

worker-dojo-api Package Skill

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

Dojo API Worker

Status: Active Purpose: Preserve Dojo API app, route, auth, schema, queue, and test contracts. Scope: packages/worker-dojo-api Trigger: Dojo route group, OpenAPI, DB schema, queue, webhook, audit, or worker entrypoint changes. Input: Route group, auth mode, DB/R2/queue binding, schema change, or event type. Output: Correct API behavior and tests.


Workflow

  1. Start at src/index.ts for API-core auth/public path behavior and top-level route mounts.
  2. Use src/v2.ts to choose or add the correct V2 sub-app and middleware chain.
  3. Treat authModeDetect() as header detection only; add verification middleware when the handler needs trusted human or agent identity.
  4. Keep DB shape aligned with src/db/schema.ts, migrations, and tests.
  5. For queue work, preserve the partition in src/index.ts: audit messages go to processAuditEvent, all other webhook events go to processWebhookBatch.
  6. Preserve workerExport.request because tests call .request() on the default export.

Verification

  • Run targeted Jest tests for the touched route group.
  • Run yarn workspace @epicdm/worker-dojo-api typecheck.
  • Run full package tests before handoff when route auth or shared schema changes.

Package Skill Inventory

Skill Inventory: @epicdm/worker-dojo-api

Package Role

@epicdm/worker-dojo-api is the Dojo LMS and skill marketplace API for catalog browse/search, publishing, checkout/install, courses/enrollments/modules, teams, publishers, admin review, webhook dispatch, and audit events.

Skills

SkillTypeUse WhenSource Backing
dojo-api-workerWorkflowChanging Dojo worker app composition, route mounts, OpenAPI, queue handling, or schema-aware API behavior.src/index.ts, src/v2.ts, src/db/schema.ts, tests
dojo-publish-catalogWorkflow/referenceWorking on skill/course publish, catalog visibility, R2 canonical artifacts, compilation queue, or MCP/catalog search.src/routes/publish.ts, src/routes/catalog*.ts, src/routes/mcp-search.ts, src/schemas/catalog.ts
dojo-teams-and-authWorkflowChanging auth modes, human verification, profile bootstrap, teams, invitations, members, or team content.src/v2.ts, src/middleware/*, src/routes/teams.ts, team route tests

Composition Notes

  • Compose publish changes with worker-dojo-jobs skill compilation behavior.
  • Compose team changes with profile bootstrap and human auth tests.
  • Use docs under docs/dojo for webhook and operational behavior, but verify implementation in source.

Review Gate

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

Result

Pass.

Checks

  • Skills are backed by worker entrypoint, V2 routing, schema, route, middleware, docs, and tests.
  • Auth-mode detection versus verification is explicit.
  • Publish skills call out the worker-dojo-jobs composition point.
  • Only .flowstate/skills files were added for this package.

Residual Risk

The package has unrelated pre-existing source edits in the working tree. These skills intentionally avoid touching those files.

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/worker-dojo-api/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-flowstate-platform-epicdm-worker-dojo-api --target <target> --out ./skills

Replace <target> with your agent target identifier. See the CLI docs for details.