Describe the problem.
Search for a technical mechanism: retry jitter, safe file writes, graceful shutdown. You don’t need an app template.
A RECIPE LIBRARY FOR AI-ASSISTED ENGINEERING
Your agent shouldn’t relearn every hard lesson.
Give it a better starting point: small, reusable engineering recipes with implementation steps, gotchas, and sources.
Use them in Codex, Claude Code, Pi, or your local-model workflow. Keep the useful knowledge from one coding session for the next.
Browse and search without an account. Sign in when you want to contribute.
A BETTER STARTING POINT 01
“How do I retry a request
without making an outage worse?”
EXAMPLE RECIPE · RETRY WITH JITTER
The pattern.
The catches.
The checks.
- 01 Back off between attempts.
- 02 Add jitter. Bound the retries.
- 03 Check idempotency first.
Don’t overcook it.
No custom scheduler if your library already does the job.
No custom scheduler if your library already does the job.
An illustrative recipe—not a claim of a verified implementation.
THE PROBLEM
The code is new.
The pitfalls usually aren’t.
AI can write a plausible solution and still miss the retry limit, the interrupted write, or the shutdown race. Explaining those details again in every project gets old.
Sous keeps that engineering knowledge in recipes you and your agent can find, inspect, and reuse.
FROM QUESTION TO IMPLEMENTATION
One useful pattern at a time.
Give your agent the recipe.
Inspect the assumptions and sources. Pull the relevant guidance into your session and adapt it to your code.
Share the lesson.
Turn a useful solution into a generic technical recipe. Remove project details, review it locally, and publish when you choose.
SMALL ENOUGH TO USE TODAY
A recipe can be
just one good idea.
You don’t need to adopt an architecture to use a safe UTF-8 truncation pattern. Larger designs can reference smaller recipes when you need them.
Browse the recipe libraryTruncate UTF-8 safely
to a byte budget.
Keep text within a byte limit without slicing through a multibyte character.
Read the recipeGuidance you can inspect.
Versioned recipes preserve the exact advice you used. Sources, assumptions, and maturity help you judge whether it fits.
Enough structure. Less ceremony.
Use one small pattern or compose a few. Explicit complexity limits help keep a small problem small.
BRING THE LIBRARY INTO YOUR WORKFLOW
Your coding agent.
A better set of instructions.
macOS developer preview · Apple Silicon and Intel