What problem does it solve?
It streamlines creating new recurring “Cry” commands that correctly delegate to an existing “Kata” and fit the repository’s naming and taxonomy rules.
Core Features & Use Cases
- Enforces Cry-to-Kata delegation: every Cry must reference at least one Kata to avoid weak or redundant commands.
- Generates complete Cry artifacts: produces structured Markdown with invocation syntax, parameters, prompt template, examples, constraints, and a Cry vs Kata comparison.
- Supports multilingual outputs: creates the default-language Cry and generates translations across the required i18n languages.
- Avoids duplication and preserves consistency: checks directives, internal codex quality criteria, existing Cries, and ensures the associated Kata exists or is flagged.
Quick Start
Tell the AI to create a new cry command named “invoice-status” that takes a required customer name and includes an optional freshness window, then save the resulting Cry artifact in the correct framework taxonomy and translate it to all configured languages.