Bootstrap a Rat-Coding project after the user installs only /rat-init: install or merge the project-visible AGENTS.md rules, check/install the rest of the Rat-Coding skills with the user-approved skill manager, reload the rules, then hold a short Socratic dialogue to scaffold README.md and doc/rationales.md when needed. Use when the user runs /rat-init, asks to start a Rat-Coding project, asks to adopt Rat-Coding in a repo, or asks to bootstrap docs for a fresh repo. Architecture/framework selection and project initialization are handled by /rat-architecture.
Propose architecture and framework choices for a Rat-Coding project based on README.md and doc/rationales.md, investigate similar off-the-shelf products, present honest trade-offs, incorporate user preferences, and initialize the project with ecosystem-standard tooling after an explicit decision. When architecture/framework is obvious from the requested product shape, present one clear option instead of forcing multiple options. Use when the user runs /rat-architecture or asks for architecture/framework selection. Assumes README.md and doc/rationales.md already exist (typically from /rat-init).
Audit a Rat-Coding project for drift between README.md, doc/rationales.md, optional doc/design.md, tests, and implementation. Use when the user runs /rat-audit or asks whether the docs, rationales, design map, tests, and code still agree. Reports contradictions, missing rationale, stale design maps, uncovered behavior, oversized rationale sections, and unresolved TODOs without auto-fixing them.
Lighten an oversized Rat-Coding doc/rationales.md by preserving active decisions in a small runtime kernel and moving detailed history into focused supporting rationale files. Use when /rat-audit reports rationale bloat, when doc/rationales.md exceeds its size budget, or when the user asks to compact or lightweight rationales. Requires README.md and doc/rationales.md.
Add a new feature the Rat-Coding way: dialogue about why and how, check the feature against the product's press release, surface security risks and alternatives, write the rationale (why + chosen implementation approach) before coding, then iterate — rationale → implement → discover → update rationale → implement — until the ideal is realized. Use when the user runs /rat-feature or proposes any non-trivial change. Assumes README.md and doc/rationales.md already exist.