Who writes recipes, and how to submit yours

Most recipes start with Lee, written from apps he has shipped. Outlaw and Crew members can also turn their own builds into recipes. Lee reviews every one before it goes live, and published recipes carry your name.

How to submit a recipe

1. Open the Build Journal entry for the feature you built.
2. In the side panel, choose Share as a recipe.
3. Give it a clear title and a one-line summary, pick a category, and write the recipe. The form starts you with sections to fill in, and your prompts and fixes from the entry come along automatically. Screenshots stay private.
4. Confirm you wrote it and submit.

What happens next

Lee reads it, usually within a few days, and does one of three things:

• Publishes it with "Shared by" and your name. You earn XP and the Recipe Author badge.
• Asks for changes with a note. Open the entry, read the note, update the recipe and submit again.
• Declines it with a reason. You can rework it and try again.

You get an email either way, and the entry's side panel always shows where it stands.

What makes a good recipe

• It solves one thing. "Referral codes on a waitlist" beats "my whole app".
• Someone else could build it. Write the decisions, the data, the screens and the rules, not just what you clicked.
• It names what breaks. The fixes section is where a recipe earns its keep.
• It has a test. A short list of checks that prove it works.
• No secrets. Never paste API keys, passwords or customer data.

Lee may tidy wording or structure before publishing. The recipe stays yours to keep using in your own projects.