flowstate-web Package Skill

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

Web Content And Payments

Status: Active Purpose: Coordinate content rendering and paid-access behavior in the LMS template. Scope: Content libs/routes/components plus payments and Stripe. Trigger: CMS block, content route, course page, product, price, purchase, subscription, or access change. Input: Content or payment behavior and affected route. Output: Content/payment change with schema and rendering consistency.

Source Map

• Content routes: src/app/blog, src/app/lp/[slug], src/app/p/[slug], course pages.
• Content libs: src/lib/content/queries.ts, src/lib/content/types.ts.
• Rendering: src/components/block-renderer.tsx, src/components/blocks/*, mdx-components.tsx.
• Payments: src/lib/payments/*, src/lib/stripe.ts, src/app/api/stripe/webhook/route.ts.
• Schema: products, prices, subscriptions, purchases, premium tiers, course products, and course purchases in src/db/schema.ts.

Workflow

1. For content changes, update type/schema assumptions before renderer logic.
2. Add block-specific rendering in a component and wire it through block-renderer.
3. Preserve public route metadata and cache/revalidate behavior when changing content routes.
4. For payment changes, keep Stripe webhook handling idempotent and backed by payment libs.
5. Verify access gates and purchase buttons after product or tier changes.

Created: 2026-06-30

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-web

Review date: 2026-06-30

Composition Notes

Use flowstate-web-lms first. Add content/payments or teams/support skills based on the domain being changed.

Review Gate

Package Skills Review: @epicdm/flowstate-web

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

Checks

• Skills are grounded in source routes, schema, content/payment/support/team libs, scripts, docs, and package commands.
• Skills describe reusable LMS template workflows instead of copying Epic Dojo-specific instructions.
• Files were written only under packages/epicflowstate/.flowstate/skills.

Pressure Scenario

Scenario: "Add a new CMS block that can appear on landing pages and course pages."

Expected behavior with skills: load flowstate-web-lms and flowstate-web-content-payments; update content types/queries, block renderer, specific block component, page routes, and typecheck.

Remaining Risk

Build may exercise integration-heavy app paths. Agents should run typecheck first and build only when environment assumptions are satisfied.

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