Katas

A kata is a guided run through a workflow, inside the editor. start kata 1 _ begins one; the status line shows the current step; progress is detected from what you type and press.

Katas: guided walkthroughs

Progress is detected, not confirmed

There is no "next" button.

You start oneprogress persisted; the run resumes
C_ Kata 3/4: Welcome back to Claude Code basics — plan, model, commit — next: switch model
You perform the stepdetected from your keys
C_ Kata 4/4: ● Now: commit to git

The runner watches what you type and which keys you press, marks a step done when it observes it, and shows the next one. A confirm button would let a step be marked done without being done.

Coaching is live

Responses to what you did, not a script read in order.

A model watches progress and writes the next instruction to the status line, including corrections when your input diverges from the step. Coach output goes to the status line only; it never writes into your text.

Exit is unconditional

Esc three times, always.

The exit is plain key-handling with no model in the path, so it works identically when the coach is wrong, slow, or absent. stop kata _ also ends the run; skip _ advances past a step.

Without a model key

Steps and exit work; coaching does not, and says so.

Step detection and the escape path are local. The coaching requires a configured model key, and its absence is reported on the status line rather than degrading silently.