Recipe Style Guide

This document defines how recipes are written in the Kester Family Cookbook.

Goals

Every recipe should:

• Be easy to cook.
• Import cleanly into AnyList.
• Reflect how the Kester family actually cooks.
• Be maintainable as a long-term cookbook.

Writing Style

• Write in clear, direct language.
• Prefer active voice.
• Assume the reader can cook basic techniques.
• Avoid unnecessary storytelling inside recipes.
• Keep explanations in editorial sections, not cooking steps.

Recipe Names

• Use descriptive, family-recognizable names.
• Avoid unnecessary adjectives.
• Keep names stable once a recipe reaches Approved status.

Ingredients

• List ingredients in order of use whenever practical.
• Use consistent units and naming.
• Group ingredients into logical sections for complex recipes.

Instructions

• Break instructions into Prepare, Cook, and Serve when appropriate.
• Each step should describe one clear action.
• Include temperatures and target doneness when they matter.
• Avoid embedding long explanations inside steps.

Planned Transformations

When a recipe is intentionally designed to become another meal:

• Include a Planned Transformation section.
• Explain what to reserve.
• Describe preparation before leaving for work.
• Describe final assembly for the second meal.

Editorial Sections

Keep testing notes, cooking feedback, revision history, and project notes after the cooking instructions.

Versioning

• Increment recipe versions for meaningful cooking changes.
• Keep the YAML version and the visible description version synchronized.

Consistency

When revising an existing recipe, improve it without changing the family's established cooking style unless there is a deliberate editorial decision to do so.