flowstate-marketplace Package Skill

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

FlowState Marketplace Publishing Workflow

Status: Active Purpose: Keep marketplace listing and extension publishing behavior coherent across API, DB, storage, review, and UI surfaces. Scope: packages/marketplace Trigger: Listing/template APIs, extension publish pipeline, developer flows, reviews, purchases, or marketplace schema changes. Input: Route or feature target, DB tables, manifest/archive expectations, auth role, and test scenario. Output: Updated marketplace behavior with route/query/library tests.

Workflow

1. Start with the route cluster: public reads are in src/app/api/listings/*, src/app/api/templates/*, and src/app/api/extensions/*; developer writes are in src/app/api/developer/*.
2. For extension publishing, preserve the order in src/app/api/developer/extensions/publish/route.ts: developer auth, multipart check, bundle size check, manifest extraction, archive structure validation, checksum, listing ownership/version checks, R2 upload, auto-review, DB write, and cache invalidation.
3. Update validation in src/lib/validation/extension-manifest.ts before route code when changing manifest shape. Keep semver, extension type, platform, pricing, activation event, and size constraints explicit.
4. Put DB behavior in query modules under src/db/*; update src/db/schema.ts only for intentional schema changes.
5. Check admin consumers before exported schema changes with rg "@epicdm/flowstate-marketplace/db/schema" packages --glob '!**/node_modules/**'.
6. Add tests next to the affected surface: API tests in src/__tests__/api/*, DB tests in src/__tests__/db/*, library tests in src/__tests__/lib/*, and component tests in src/__tests__/components/*.

Verification

• yarn workspace @epicdm/flowstate-marketplace test
• yarn workspace @epicdm/flowstate-marketplace typecheck
• For schema changes: yarn workspace @epicdm/flowstate-marketplace db:generate
• For deployment-sensitive changes: yarn workspace @epicdm/flowstate-marketplace build

Red Flags

Composition

• Use auth-client-oidc-pkce-workflow for marketplace login/callback client behavior.
• Use chrome-app-shell-workflow for shared chrome UI composition.

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-marketplace

Created Skills

Candidate Future Skills

Source Evidence

• src/db/schema.ts defines templates, app versions, profiles, enrollments, publishers, reviews, purchases, support, and activity tables.
• src/app/api/developer/extensions/publish/route.ts implements the publish pipeline.
• src/lib/validation/extension-manifest.ts defines manifest constraints.
• src/__tests__/api/*, src/__tests__/db/*, src/__tests__/lib/*, and component tests cover behavior.

Review Gate

Review: @epicdm/flowstate-marketplace Skills

Result: Pass for source-backed package-local workflow guidance.

Checks

• The skill focuses on the extension/listing workflow and schema contracts rather than route enumeration.
• It cites publishing, validation, storage, schema, cache, and tests.
• It separates safe verification from heavier build/migration commands.
• It avoids modifying API code, generated .flowstate/dojo, .next, and .open-next.

Residual Risk

Marketplace is broad. Split extension archive, public listing, and dashboard UI skills before substantial future changes in those areas.

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