Katas
Kata recipes
Each recipe starts with the outcome, then gives the stack, prompts, checks, failures and ways to adapt it. Anything that has not been checked says so.
Recipes
- Inspect a daily weather record: dates, units, gaps and flags
Open a year of real daily weather from NOAA and write down what it holds before you use it: station, dates, units, missing values, and every measurement, quality and source flag.
- Estimate reference evapotranspiration with FAO-56 from temperature data
Reproduce FAO's worked examples for extraterrestrial radiation and Penman-Monteith reference evapotranspiration, then compute daily ET0 for a real year from temperature alone and compare it with the Hargreaves equation.
- Estimate a crop's net irrigation need from crop coefficients and effective rain
Turn reference evapotranspiration into a maize crop's water need with FAO-56 crop coefficients by growth stage, subtract effective rain with FAO's simple monthly formula, and report the net irrigation need by month.
- Agriculture Randori: an unseen change of assumption
Start from the maize estimate; a partner reveals one changed assumption after you begin. Predict the direction and rough size of the change, then recompute and explain the difference.
- Inspect an IFC model: schema, units, spatial tree and relationships
Open a real IFC file with IfcOpenShell and write down what it declares: schema, units, the spatial tree, each element with its GlobalId, and how the opening and window are related to the wall.
- Read the property sets and find what is missing
List every property set on the wall and window with its values and types, and mark the properties that exist but hold no value.
- Check a model against IDS requirements
Read a practice IDS file, run it against the sample with IfcTester, and explain the one requirement that fails.
- Change the model and check it again
Fix the failed requirement with an IfcOpenShell edit, keep every GlobalId, then rerun the IDS, schema and geometry checks on the edited copy.
- BIM Randori: an unseen requirement change
Start from the edited model; a partner reveals one new requirement card after you begin. Check, fix and recheck without breaking what already passed.
- Map a sitemap with branches and error states
Map every screen and state of a small SaaS flow, including errors, empty states, a dialog and the way back, before you draw a single screen.
- Draw low-fidelity screens and wire the flow
Turn the sitemap into greyscale screens at phone size, wired into a clickable prototype that reaches every state, errors included.
- Define design tokens for colour, type and spacing
Name the colours, type sizes and spacing of the design once, as design tokens in a JSON file, and check every text and control colour pair for contrast.
- Build components from tokens
Turn the repeated parts of your screens into components (buttons, fields, the error summary, the dialog) built from your tokens, so one change updates every screen.
- Implement the screens and check accessibility
Build the screens as a working web page from the same flow and tokens, then prove keyboard use, screen reader structure, contrast and reflow with automated checks.
- UX Randori: an unseen flow with a hidden constraint
An unseen-constraint UX Randori: map, wire and check a small flow you have not seen, and adapt when a partner reveals one constraint after you start.
Template examples (fixtures)
These pages show how a recipe is laid out. They are fixtures: nobody has run, reviewed or published them, and they are not katas to follow.



