flowstate-build-config Package Skill

Package: @epicdm/flowstate-build-config Repository: epic-flowstate-apps Path: packages/build-config Version: 1.0.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 Build Config Theme And Shims

Status: Active Purpose: Maintain shared app theme tokens and browser compatibility shims. Scope: @epicdm/flowstate-build-config in packages/build-config. Trigger: Use when changing theme.css, build-config exports, or browser shim files. Input: Target token/shim change, affected app package, UX design-system notes. Output: Shared build-config behavior that apps can import without app-specific leakage.

Workflow

1. Inspect The Shared Surface

Read:

• packages/build-config/package.json
• packages/build-config/src/index.ts
• packages/build-config/src/theme.css
• packages/build-config/src/browser-shims/*
• ux/design-system.md for token intent

Confirm whether the change belongs in shared build config. If it only serves one app, keep it in that app package.

2. Change Tokens Or Shims Conservatively

1. Treat theme.css as shared app token infrastructure, not package-local styling.
2. Keep token naming aligned with UX steering docs.
3. Keep browser shims minimal; only stub APIs that app bundles must tolerate in the browser.
4. Do not introduce app-specific tokens into build-config.

3. Verify An Affected Consumer

After shim changes, build or typecheck at least one affected app package that imports the shimmed dependency. Prefer a package that previously failed without the shim.

Verification

yarn workspace @epicdm/flowstate-build-config typecheck
yarn build:affected

The current package does not declare a package-local typecheck script, so record that script gap when the workspace command fails. Use affected app checks as the practical validation.

Composition

Use the relevant app package skill after a token or shim change if a consumer package needs local styling, bundling, or runtime updates.

Pitfalls

• Do not copy generated Dojo prose into this skill.
• Do not use build-config as a dumping ground for app-specific CSS.
• Do not expand browser shims beyond the minimum needed for app bundling.

Done When

The shared export, token or shim file, affected app import, and validation result all agree.

Package Skill Inventory

@epicdm/flowstate-build-config Skill Inventory

Review Gate

@epicdm/flowstate-build-config Skill Review

Verdict

Pending verification.

Skill is source-backed and focuses on theme tokens and browser shim operation.

Verification To Run

yarn workspace @epicdm/flowstate-build-config typecheck

Run affected app builds after theme or shim changes.

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