Engineering recipes

Put your best work on repeat.

Turn the way your team builds software into recipes that humans and AI can execute, validate, and improve.

Define it once. Validate every run. Improve it together.

Explore recipes See how it works

Hand-painted pop-up storybook of an open recipe book rising into layered engineering workstations connected by a turquoise execution path.

Example recipe

Create a typed API endpoint

Resource: widgets
Method: POST

Goal

Ship a typed POST endpoint for widgets.
Inputs

Resource name, HTTP method, and project conventions.
Steps

Derive the route and handler, create the handler, add success and validation-failure tests.
Validation

Confirm types, tests, and handler behavior before shipping.
Output

A completed work package ready to review and merge.

AI execution

Let an engine walk the graph

Feed the Recipe to an execution engine. It follows ordered steps, applies rules, and pauses where validation or human judgment is required.

Derive the route and handler name from inputs
Create the handler against your codebase
Add success and validation-failure tests
Validate output before the work package is complete

Human SOP

Read it like a playbook

The same Recipe reads as a supervised standard operating procedure—goals, decisions, and checks written for the person doing the work.

Know the goal before touching the codebase
Follow ordered steps without tribal knowledge
Apply rules and instructions at decision points
Validate results the same way every run

Goal

The outcome the Recipe exists to produce—clear enough to judge success.

Inputs

Parameters that shape the run, such as resource name and HTTP method.

Steps

An ordered path from intent to completed work—derive, create, test, validate.

Rules

Instructions and constraints that keep every run aligned with team standards.

Validation

Checks that prove the output is correct before trust increases.

Outputs

The completed work package—code, tests, and evidence you can review.

Storybook open book with layered terraces and a turquoise path representing a reusable engineering package.

Supervised

Humans stay in the loop. Every step is visible; gates pause for judgment.

Delegated

Proven Recipes run with fewer interruptions, while validation still protects the outcome.

Unattended

High-trust Recipes execute without babysitting—backed by evidence, not hope.

Desktop

Local execution with filesystem and tooling access to the developer’s environment.

CLI

Headless runs for local workflows, scripts, and automation without a UI.

CI

The same runtime packaged for pipelines and ephemeral environments.

Beyond

Built for future execution environments—without changing the Recipe itself.