An open library · CC BY 4.0 · 12 recipes in 10 domains
Every process written down in plain words, with the model to build it in the tool you use and the sources it was written from. A two-person shop, a volunteer group, a 300-person company: read it, make it yours, run it.
Every community cat fixed, returned home, and counted once. For a volunteer group of a few coordinators and the trappers and caretakers they call on. Trap, neuter, return, from a neighbor's report to a colony where every cat wears an eartip.
Trap, neuter, return for a volunteer group: colonies on a map, trappings booked onto clinic days, every cat counted once and returned home.
3 sources
Colony portrait · Laundromat lot
One cat drawn per estimated cat; the picture every trapping fills in. Fixed share 62 of 100.
Watch films the way a director makes them: one craft at a time, one scene shot by shot, every technique named. For a film club or class of five to thirty people who want to direct. Seasons of weekly meetings where everyone watches for the same thing, and a toolkit that grows with every film.
Updated Oct 25, 2026 · 3 sources
Every scrim has a purpose, every game is reviewed by the next morning, and every strat earns its place in officials. For a professional Counter-Strike 2 team: coach, in-game leader, analyst and five players. How such a team practises, from the strat book to match day.
Updated Oct 23, 2026 · 2 sources
Every purchase gets a yes from whoever owns the money, finance pays only vendors it has checked, and each department sees what it has already committed this quarter. For a company of about 200 people: how it asks for, approves and pays for things, without a spreadsheet and a chain of emails.
Updated Oct 23, 2026 · 3 sources
Everyone knows the few things that matter this quarter, and whether they're moving. For a company of twenty to two hundred people in several teams. John Doerr's Objectives and Key Results, set up so every team objective shows under the company objective it serves and the weekly check in is a record, not a memory.
Updated Oct 23, 2026 · 3 sources
1 · Read it
One story follows a real case from start to finish. What people look at, the rules, and what must stay true, with the sources the recipe was written from.
2 · Make it yours
Every recipe names the choices that change the setup: who logs what, which things you lend out, what you call them. Answer them and the rest follows.
3 · Run it
Pick your tool on the recipe page, Fibery, Airtable, Notion, Lovable and more, and hand the recipe to your AI assistant; or build it by hand from the model. Same recipe, your kitchen.
Recipes that belong together: everything one kind of organisation runs, picked so the pieces fit. Open a collection to set up the whole thing or just the parts you need.
Shape Up, incident management, OKRs, a sales pipeline, purchase requests and a content calendar: the whole company in one connected setup.
6 recipes →
Deposits, parts on order, build stages with photos and the customer waiting at the end, whether it's a guitar, a yarn batch or a cracked screen.
3 recipes →
Groups where most members never open the tool: a few organisers, a sign-up form, a season or a program to run, and a count at the end of the year.
2 recipes →
Processes people searched for and didn't find. Vote for the one you need with a 👍 on its issue; the most wanted get written first. Or write it yourself and take the byline.
Add the recipe-writer skill to Claude or any AI assistant, tell it how your group runs the process, and answer its questions. It writes the recipe in the cookbook's format, with sources, and opens a pull request. A reviewer checks it, it goes live under your name, and anyone can build it anywhere.
Prefer to write by hand? The format is one Markdown file; the checks run on your pull request.