Creates new canonical AI agent files in .agents/agents/ following AI Agents Convention, then routes them to every harness via ./rhino harness adapters generate. Ensures proper structure, skills integration, and documentation.
Creates Annotated-concept tutorial content for ayokoding-web with 45-60 concept-centric worked examples plus accessible Mermaid diagrams. Supports a validated no-code sub-mode (leadership topics — 20-30 worked scenarios, zero code). Ensures bilingual content and quality compliance.
Creates By Example tutorial content for ayokoding-web with 75-85 heavily annotated code examples following five-part structure. Ensures bilingual content and quality compliance.
Creates In-the-Field production implementation guides for ayokoding-web with 20-40 guides following standard library first principle. Ensures production-ready code with framework integration.
Creates Primer ("Just Enough X") tutorial content for ayokoding-web: fast language or tool on-ramps with 75-85 annotated code examples at By-Example pace, scoped to just-enough breadth for productive use. Ensures bilingual content and quality compliance.
Audits each project's test targets, local hooks, and pipeline definitions against the adopted gate standards and returns rated findings, without modifying anything.
Applies a CI checker's findings to test targets, hooks, and pipeline definitions after re-validating each one, and records what it fixed, disproved, and left for a person.
Audits published content pages for clear writing, accessible structure, true facts, working links, and the product rules its adapter states, and returns criticality-rated findings with their sources, without modifying anything.
Executes Content Propagation on a frozen content ledger, correcting facts only from a cited source, repairing links to verified targets, and fixing writing and structure without restyling, with product rules applied as the adapter states them.
Audits documentation for factual accuracy against authoritative sources and the repository, for contradictions within and across documents, and for references to things that no longer exist, returning rated findings; as a combined validator it also checks structure and links.
Expert at managing files and directories in docs/ directory. Use for renaming, moving, or deleting files/directories while maintaining kebab-case conventions, fixing links, and preserving git history.
Applies documentation checker findings after re-validating each against the current text and its recorded evidence, edits only high-confidence fixes, and records false positives and findings left for a person.
Validates internal and external documentation links. Always uses docs/metadata/external-links-status.yaml as its sole cache, prunes it, and updates lastFullScan on every invocation. Use for dead links, URL reachability, internal references, or link-health audits.
Expert documentation writer specializing in GitHub-compatible markdown and Diátaxis framework. Use when creating, editing, or organizing project documentation.
Audits the separation between the platform style guides under docs/explanation/software-engineering/ and AyoKoding educational content, for each relationship the Software Design Reference lists, and returns criticality-rated findings without modifying anything.
Executes Software Engineering Separation Propagation on a frozen ledger, adding prerequisite statements, removing duplicated teaching from style guides, and repairing table entries and cross-links, without ever writing AyoKoding educational content.
Applies validated fixes from docs-tutorial-checker audit reports. Re-validates pedagogical findings before applying changes. Use after reviewing docs-tutorial-checker output.
Audits a repository's harness bindings for internal parity with their canonical sources and for drift from each harness's current documented conventions, and returns rated findings without editing.
★not rated 12 todayA37 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: