HowToUse

How to use a Generative Recipe

The recipe is the start. Not a blank chat.

Do this

1. Open a recipe from [RecipeIndex] or Files.
2. Copy the recipe text (the schema, not a generated HTML file unless you are comparing).
3. Paste it into an AI. Grok, Claude, Codex, whatever you actually use.
4. Say this, or close to it:

Build this from the recipe. Follow intent, vibe, constraints, and must-nots. Ask before you add extras. Give me a working prototype in the output format the recipe names.

1. Run what you get.
2. Write down what felt wrong. Not "the JS is messy." The experience.
3. Edit the recipe. Build again.

That is the whole method. Iterate the schema. Treat generated code as a rendering.

What "working" means on pass one

Playable or usable. Not polished. Not feature-complete. If a capable model cannot get you a prototype from the recipe, the recipe is still missing design decisions.

Common stalls

• You pasted a vibe sentence instead of the schema.
• You let the model invent platform, deps, or scope.
• You started debugging files and abandoned the recipe.
• Audio, libraries, or build tools crept in against the constraints.

Tighten must-nots and output format. Feed it again.

Next

• What a recipe is: [WhatIsARecipe]
• First worked example: [SquigglyCatapult]
• Catalog: [RecipeIndex]