Make a new recipe card

A ready-made prompt for Copilot, or any other assistant, that produces a new recipe written in the same style and format as the rest of these pages.

How to use it

Change the three lines at the top - what you want to make, whether it uses active starter or discard, and anything else that matters.
Press Copy.
Paste it into Copilot and send.

Everything below the top three lines is the house style, and is worth leaving alone unless you want to change how all the pages read.

=== EDIT THESE THREE LINES ===============================================
WHAT I WANT TO MAKE: focaccia with rosemary and sea salt
STARTER TYPE: active starter at peak        (or: discard, straight from the fridge)
ANYTHING ELSE: should be doable in one day, no overnight proof
==========================================================================

Write this up as a single recipe page for my sourdough website.

ABOUT THE SITE
The site documents a sourdough starter called Snow that I hand out as dried
flakes. It already has pages for reviving the flakes, feeding the starter, the
general bread method, and a handful of recipes. Readers are mostly beginners
who have never baked with sourdough before.

HOUSE RULES
- Metric by weight, in grams. Never cups. Oven temperatures in Celsius with
  Fahrenheit in brackets.
- Plain British English. Calm, dry, direct. No exclamation marks, no "delicious",
  no "perfect", no marketing voice, no emoji.
- Explain WHY a step matters when it is not obvious, in one short sentence.
  Assume the reader has never done it before and will panic at the first odd
  smell or slack dough.
- Be honest about timing. Say what the dough should LOOK like, not just how many
  hours, because kitchen temperature changes everything.
- Include a short troubleshooting section for the two or three things most
  likely to go wrong, with the actual cause rather than vague reassurance.
- Never claim a recipe is foolproof.

WHAT TO PRODUCE
A complete, standalone HTML file, ready to drop into the recipes folder. Match
the existing pages exactly:

1. Standard head: utf-8, viewport, robots noindex/nofollow, title
   "<Recipe name> - Snow", a one-line meta description, a favicon link
   <link rel="icon" href="../assets/favicon.svg" type="image/svg+xml">
   and <link rel="stylesheet" href="../assets/style.css">
2. A skip link as the first thing in the body:
   <a class="skip" href="#main">Skip to content</a>
3. The standard site header with the full nav (Home, About Snow, Revive,
   Feeding, The method, Recipes, Troubleshooting, Share it on, Give) using
   ../ paths, with <a href="./" aria-current="page">Recipes</a> for the
   recipes link.
4. <main class="wrap" id="main"> containing:
   - <h1> recipe name
   - <p class="lede"> two sentences saying what it is and why it is worth making
   - <p><span class="tag-active">Needs active starter</span>
     <span class="tag-untested">Collected</span></p>
     Use tag-discard instead of tag-active if it uses discard. Use
     tag-untested unless I tell you I have actually baked it, in which
     case use tag-tested and the word Tested.
   - <ul class="meta"> with three <li> items: yield, total time, bake
     temperature and time. Bold the numbers with <b>.
   - Ingredients as a <table> with <th>Ingredient</th> and
     <th class="num">Amount</th>, amounts in <td class="num">.
   - The method. Use <div class="day"><span class="label">Step 1 · what</span>
     ...</div> blocks for anything with waiting between stages, or a plain
     <ol> for a quick recipe.
   - Notes in <div class="panel tip">, warnings in <div class="panel warn">,
     reassurance in <div class="panel good">, neutral asides in <div class="panel">.
     Each panel starts with an <h3>.
   - A short "Keeping them" section at the end.
   - If the recipe is untested, a <div class="panel"> near the foot saying
     so plainly and inviting corrections.
5. The standard footer with the three-column <nav class="sitemap"> block
   (Start here / Keep it going / More) and the colophon paragraph, copied
   exactly from any existing recipe page.

Use   between numbers and units (500 g, 220 °C). Use -
for dashes and - for ranges. No inline styles. No JavaScript. Do not
invent new CSS classes - only use the ones listed above.

Finally, tell me the filename you would use and one line I can paste into the
recipes index page to link to it, in this form:

<a href="FILENAME.html"><strong>Recipe name</strong><span>Collected ·
  one short line on what it is.</span></a>

What you get back

A finished HTML file in the same visual style as every other recipe here, plus the filename and the one-line snippet to add it to the recipes index. Save the file into the recipes/ folder, paste the snippet into recipes/index.html, commit, and it is live.

Check it before you trust it

An assistant will confidently invent a hydration, a bake time or a proofing window that is simply wrong. Before you publish anything, sanity-check the numbers against a recipe you already trust, and ideally bake it once. The whole point of these pages is that someone unfamiliar with sourdough can follow them and get bread.

Things worth asking for

A same-day version as well as the overnight one. Many people will not plan 18 hours ahead.
What to do with the leftovers, or how it freezes.
A flavour variations table, as on the mini loaves page.
Scaling - half quantities, or double.
Which step is the one people get wrong, called out explicitly.