cai-codex

Apply the Add Parameter refactoring (crosses class boundaries). Fixes missing data. Executes the catalog mechanics one step at a time, testing after each step.

Build a detail design's work breakdown unit by unit, test-first, verifying and committing each one before the next starts — or, with no design document, cut checkpointed units yourself. Usage: $build <detail design doc, or what to build>

Apply the Change Bidirectional Association to Unidirectional refactoring (crosses class boundaries). Fixes Inappropriate Intimacy. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Change Reference to Value refactoring (wide blast radius — read the preconditions carefully). Fixes awkward shared lifecycle. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Change Unidirectional Association to Bidirectional refactoring (crosses class boundaries). Fixes missing navigation. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Change Value to Reference refactoring (wide blast radius — read the preconditions carefully). Fixes duplicate entities. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Collapse Hierarchy refactoring (wide blast radius — read the preconditions carefully). Fixes Lazy Class. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Consolidate Conditional Expression refactoring (local and mechanical). Fixes scattered checks. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Consolidate Duplicate Conditional Fragments refactoring (local and mechanical). Fixes duplication in branches. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Convert Procedural Design to Objects refactoring (wide blast radius — read the preconditions carefully). Fixes procedural design. Executes the catalog mechanics one step at a time, testing after each step.

Something demonstrably broken right now — a failing test, a crash, wrong behaviour, a regression — where the root cause comes before any fix. Use when the user says "this is broken", "fix this bug", "為什麼會壞", or pastes an error message or stack trace.

Apply the Decompose Conditional refactoring (local and mechanical). Fixes Long Method. Executes the catalog mechanics one step at a time, testing after each step.

Write a design document for review — diagnosis (something is broken: the root cause and the fix, one page), stance (the trade this system makes, one page, read in full), decisions (the choices that trade implies, routed so only what needs a person reaches one), detail (turns an approved entrance into something that can be built from), or delta (recovers the decisions from a branch already built). Usage: $design <what to design, or the mode: diagnosis|stance|decisions|detail|delta>

An unknown that would change the work, surfaced before implementation code is written — the codebase area is unfamiliar, the requirements are ambiguous, the option space is unexplored, a term is undefined, or the result will be judged by look and feel. Use when the user says "what am I missing", "interview me about this", "brainstorm the options", "mock this up first", or "I don't know what X is".

Apply the Duplicate Observed Data refactoring (wide blast radius — read the preconditions carefully). Fixes Large Class (GUI). Executes the catalog mechanics one step at a time, testing after each step.

Apply the Encapsulate Collection refactoring (crosses class boundaries). Fixes Data Class. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Encapsulate Downcast refactoring (local and mechanical). Fixes caller-side casts. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Encapsulate Field refactoring (local and mechanical). Fixes Data Class. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Extract Class refactoring (crosses class boundaries). Fixes Large Class, Divergent Change, Data Clumps. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Extract Hierarchy refactoring (wide blast radius — read the preconditions carefully). Fixes overloaded class. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Extract Interface refactoring (crosses class boundaries). Fixes Large Class, test seams. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Extract Method refactoring (local and mechanical). Fixes Long Method, Duplicated Code, Comments. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Extract Subclass refactoring (wide blast radius — read the preconditions carefully). Fixes Large Class. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Extract Superclass refactoring (wide blast radius — read the preconditions carefully). Fixes Duplicated Code. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Form Template Method refactoring (wide blast radius — read the preconditions carefully). Fixes Duplicated Code. Executes the catalog mechanics one step at a time, testing after each step.

A git or GitHub CLI operation the user asks for — commit, add, push, pull, merge, rebase, stash, branch create/switch, pr, or a combined request like "commit + push + pr" — run on the chore tier instead of the main session model.

A design or plan doc to take from review to verified implementation — unit by unit when it carries a work breakdown schedule, whole otherwise. Usage: $goal <path to design/plan doc>

Apply the Hide Delegate refactoring (local and mechanical). Fixes Message Chains. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Hide Method refactoring (local and mechanical). Fixes over-wide interface. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Inline Class refactoring (crosses class boundaries). Fixes Lazy Class. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Inline Method refactoring (local and mechanical). Fixes Middle Man, over-extraction. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Inline Temp refactoring (local and mechanical). Fixes noise. Executes the catalog mechanics one step at a time, testing after each step.

Turn a request into an acceptance-testable problem statement before any code exists — explore context, ask one question at a time, propose 2-3 approaches with a recommendation, then wait for approval. Usage: $intake <request>

Apply the Introduce Assertion refactoring (local and mechanical). Fixes Comments (implicit assumptions). Executes the catalog mechanics one step at a time, testing after each step.

Apply the Introduce Explaining Variable refactoring (local and mechanical). Fixes complex expression. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Introduce Foreign Method refactoring (local and mechanical). Fixes Incomplete Library Class. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Introduce Local Extension refactoring (crosses class boundaries). Fixes Incomplete Library Class. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Introduce Null Object refactoring (crosses class boundaries). Fixes repeated null checks. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Introduce Parameter Object refactoring (crosses class boundaries). Fixes Long Parameter List, Data Clumps. Executes the catalog mechanics one step at a time, testing after each step.

Show or change which model each cai role (chore, build, think) runs on, without re-running $setup. Run $models to review and switch, $models <role> <model> to set one role, or $models reset <role> to put it back on cai's default.

Apply the Move Field refactoring (crosses class boundaries). Fixes Feature Envy, Inappropriate Intimacy. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Move Method refactoring (crosses class boundaries). Fixes Feature Envy, Shotgun Surgery. Executes the catalog mechanics one step at a time, testing after each step.

Lay out two or more ways forward so a person can actually choose between them: shared comparison dimensions, six fields per option including an everyday-life ELI5 analogy, a recommendation and the condition that voids it. Use before a list of options goes out, and after one already did and the reader could not act on it — 看不懂 / 這是什麼意思 / 差在哪 / 幫我展開 / 講白話一點 / 比較一下 / expand that / what is the difference / explain it simply / which should I pick. Usage: $options <what to compare, or nothing to rewrite the previous message>

Apply the Parameterize Method refactoring (crosses class boundaries). Fixes Duplicated Code. Executes the catalog mechanics one step at a time, testing after each step.

A plan, design doc, spec, RFC, or ADR to review before anything is built from it — read from the requirements first, the way a senior architect would. Use when the user asks for that review, says "審一下這份計畫", "is this over-engineered", "does this match the requirements", "is this spec precise enough to build from" — and on your own plans before handing them over.

Apply the Preserve Whole Object refactoring (crosses class boundaries). Fixes Long Parameter List. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Pull Up Constructor Body refactoring (crosses class boundaries). Fixes Duplicated Code. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Pull Up Field refactoring (crosses class boundaries). Fixes Duplicated Code. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Pull Up Method refactoring (crosses class boundaries). Fixes Duplicated Code. Executes the catalog mechanics one step at a time, testing after each step.

Apply the Push Down Field refactoring (crosses class boundaries). Fixes Refused Bequest. Executes the catalog mechanics one step at a time, testing after each step.