write-catalystlisted

# /write-catalyst Draft a new catalyst file in [control/lib/mcp/catalysts/](control/lib/mcp/catalysts/) following the format, body principles, and section template documented in [docs/catalysts.md](docs/catalysts.md). Validate it parses, update the loader test, and hand back to the user for PR. The catalyst paradigm: a `.md` file with JSON frontmatter that mojulo ships through MCP so a user's Claude Code can read it once and *catalyze* the synthesis of a concrete `.claude/skills/<name>/SKILL.md` for that user's bot. The catalyst is not a skill; it produces a skill. Keep this distinction sharp throughout — if you blur it, the body you draft will be wrong. ## Read these first (every invocation) Always pull these into context before drafting anything: - [docs/catalysts.md](docs/catalysts.md) — the author spec. Format, validation, body principles, the six-section template, the checklist for adding a new one. - [control/lib/mcp/tools/catalysts.js](control/lib/mcp/tools/catalysts.js) — read `SYNTHESIZER_BRIEFING`. The body you draft is read by a future Claude *after* that briefing is prepended, so don't repeat what the briefing already says. - [control/lib/mcp/catalysts/loader.js](control/lib/mcp/catalysts/loader.js) — exact validation rules. Your draft must pass `parseCatalystFile`. - All existing `.md` files in [control/lib/mcp/catalysts/](control/lib/mcp/catalysts/) — these are the exemplars. Bias toward the one closest in category to the user's intent and study its mapping