Apps that already work, written as recipes.

Each recipe has the ingredients, the steps, and the mistakes the author already made. Give it to your AI and build your own.

MacREC

recorder · macOS
  • 2 s pre-buffer in memory
  • −42 dB sound threshold
  • 3 s of silence closes a chunk
  • 45 s max per chunk
  • Apple speech filter
  • 0 third-party packages
noise never reaches the API

From recipe to running app

A recipe is not code. It is every decision made before the code.

  1. Pick a recipe

    Each one comes from a real app that works.

  2. Give it to your AI

    Claude Code, Cursor, Codex. The recipe sets the order of the steps and when each one is done.

  3. Check the result

    A final checklist shows if your app matches the author's, item by item.

What's in a recipe

Every recipe follows the same structure.

The dish
What the app does, who it is for, what sets it apart.
Ingredients
Frameworks, APIs and permissions, and why each one.
Method
Steps in order, each with a “done when”.
Chef's notes
The interface details that make it feel right.
Don't let it burn
Mistakes that cost the author hours, and how to avoid them.
Parameters
Exact numbers: thresholds, timings, sizes.
Done right
The checklist to verify the result.
Variations
Ways to adapt it.

Recipes

The first recipe is being tested by invited cooks.

Built a good app? Turn it into a recipe.

Your decisions and your mistakes are worth more than the code. Write them down once and let others build from them.

Author sign-ups soon