Skip to content

Recipes ​

Short, task-oriented patterns for things you do all the time when authoring a kitsoki story. Each recipe is a minimal correct snippet plus a pointer to the reference doc that owns the full contract.

These are starting points, not specifications. When a field name or edge case matters, the authoritative sources are the schema (kitsoki docs app-schema) and the linked reference under ../stories/, ../architecture/, and ../tracing/.


RecipeYou want to…
Add an intentRecognise a user action and move between rooms
Confirmation gateMake the user confirm before an irreversible effect
Host call & branchRun a host.* call and handle success vs failure
Collect a formGather several typed fields in one submission
Flow test + cassetteLock behaviour with a deterministic test
Story flow coverageGate whether fixtures cover authored branches and enum parameters
Background jobRun long work off the turn and notify on completion
Studio MCP async smokeProve background completion, inbox teleport, and chat-work reacquisition over studio MCP
Studio MCP GitHub inbox smokeProve GitHub issue/PR intake and reacquisition over studio MCP
Studio MCP dogfoodDrive Kitsoki through its own MCP surface from Claude, Codex, or another agent
Repo history capsulesList and verify the 10 promoted historical bugfix capsules with GREEN/RED/GREEN oracle arming
Repo history training for a new repoTurn historical bug fixes into deterministic oracles, readiness reports, and live-cell commands
Repo history training with gears-rustUse the private/heavy Rust reference path for the external bake-off harness
Project prompt overlaySpecialize a generic story's prompts for a project without forking it

Larger worked examples ​

For end-to-end examples rather than single patterns, see the case studies — start with bug-fix.md, which traces how a prompt-driven agent loop became a multi-room deterministic pipeline — and the per-story READMEs under ../../stories/. The background-jobs section has its own deeper recipes page.