flowstate-compliance Package Skill

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

Compliance Auth Context

Status: Active Purpose: Preserve protected compliance access and request context. Scope: Auth routes, session constants, OIDC client, and getAppContext. Trigger: Auth, session, redirect, or context changes. Input: Desired access behavior and affected route group. Output: Auth-context change with typecheck/test verification.

Source Map

• src/app/auth/login/route.ts, callback/route.ts, and logout/route.ts.
• src/lib/oidc/client.ts.
• src/lib/session/constants.ts defines __session_c.
• src/lib/get-app-context.ts returns app context for protected pages.
• src/app/(auth) and src/app/(compliance)/layout.tsx separate public auth and protected app surfaces.

Workflow

1. Trace the login or protected page request path before editing.
2. Keep session cookie changes centralized in src/lib/session/constants.ts.
3. Do not duplicate OIDC client setup outside src/lib/oidc/client.ts.
4. Keep getAppContext as the shared bridge from request/session/environment to pages.
5. Run typecheck and package tests.

Created: 2026-06-30

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-compliance

Review date: 2026-06-30

Composition Notes

Use the dashboard skill for route work, then invoke schema/score or auth/context when the change touches those shared contracts.

Review Gate

Package Skills Review: @epicdm/flowstate-compliance

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

Checks

• Skills cite schema, routes, context helpers, scoring, seed data, and package commands.
• Skills avoid mirroring the generated feature matrix and group work by compliance workflows.
• Files were written only under packages/compliance/.flowstate/skills.

Pressure Scenario

Scenario: "Add a new evidence type and display it in compliance evidence pages."

Expected behavior with skills: load flowstate-compliance-schema-score, update evidenceTypes and related schema/seed/page handling, then run typecheck and package tests.

Remaining Risk

Schema and migration generation were not run during authoring. Agents changing schema should run Drizzle generation and inspect migration diffs.

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