dojo-compiler Package Skill

Package: @epicdm/dojo-compiler Repository: flowstate-platform Path: packages/dojo-compiler 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 Compiler Emit

Status: Active Purpose: Keep target-specific emitted artifacts stable and tested. Scope: src/emit.ts, src/emitters, src/tarball.ts, and emitter tests. Trigger: New target, changed emitted file, tarball, or target output format. Input: Canonical skill and target ecosystem. Output: Target-specific output with exact tests.

Source Map

• Dispatcher: src/emit.ts.
• Targets: src/emitters/claude-code.ts, opencode.ts, crush.ts, openclaw.ts.
• Target exports: src/emitters/index.ts.
• Tarball packaging: src/tarball.ts.
• Tests: emit.test.ts, emitters.test.ts, tarball.test.ts.

Workflow

1. Add target name to Target in src/types.ts before emitter wiring.
2. Implement a focused emitter with explicit file names/content.
3. Wire target through src/emitters/index.ts and src/emit.ts.
4. Assert exact output keys and representative content in tests.
5. If tarball output changes, test byte-level packaging assumptions through tarball.test.ts.

Created: 2026-06-30

Package Skill Inventory

Skill Inventory: @epicdm/dojo-compiler

Review date: 2026-06-30

Composition Notes

Load the orchestrator first. Use manifest workflow for input graph semantics and emit workflow for target outputs.

Review Gate

Package Skills Review: @epicdm/dojo-compiler

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

Checks

• Skills are based on public exports, schema, resolver, emitters, errors, CLI, and tests.
• Skills avoid treating each exported function as a standalone generated feature.
• Files were written only under packages/dojo-compiler/.flowstate/skills.

Pressure Scenario

Scenario: "Add a new codex emit target."

Expected behavior with skills: load flowstate-dojo-compiler and flowstate-dojo-compiler-emit; update target union, emitter file, emitter index, emit.ts, tests, and typecheck.

Remaining Risk

Downstream Dojo publication files were not touched. Any compiler behavior change should be validated against existing generated Dojo artifacts separately.

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