World cookbook
Runnable recipes, each an outcome against twins with real SDKs, fake keys and local state. Consult the model for shared state semantics and the CLI reference for current commands. A recipe that needs a real service or a checkout of another repository says so on its page.
Start with a small example
These recipes use exact published packages and require no private source checkout or platform account. Use one in an empty directory. Each page names its prerequisites, assertions and limits.
| Recipe | Outcome | Prerequisites |
|---|---|---|
| Browser signup and signed webhooks | Create an account, persist its session, inspect vendor data, verify a callback and sign out | Node 22.6+, npm; Chromium for the automated suite |
| Repeatable data and behavior | Create a record, assert a one-time fault, retry a scripted answer, reset and repeat | Node 22.6+, npm |
| Isolated CI workers | Run two independent jobs and stop each World after success or failure | Node 22.6+, npm; package registry during preparation |
| Transactional email | Send with Resend's SDK, inspect a local sign-in code and resume the same message | Node 22.6+, npm |
Tutorials teach a task step by step; cookbook recipes assemble reusable workflows. Getting started is the first local lesson. Manual adoption, recovery and coverage explain how to adapt a recipe to your app.
Larger application case studies live in the source repository and name their own checkout prerequisites. This site serves the complete starter examples above.