Baton File Schema
The baton file (next-prompt.md) is the communication mechanism between loop iterations. It tells the next agent what to build.
Format
---
page: <filename-without-extension>
---
<prompt-content>Fields
Frontmatter (YAML)
| Field | Type | Required | Description |
|---|---|---|---|
page | string | Yes | Output filename (without .html extension) |
Body (Markdown)
The body contains the full Stitch prompt, which must include:
- One-line description with vibe/atmosphere keywords
- Design System block (required) — copied from
DESIGN.mdSection 6 - Page Structure — numbered list of sections/components
Example
---
page: achievements
---
A competitive, gamified achievements page with terminal aesthetics.
**DESIGN SYSTEM (REQUIRED):**
- Platform: Web, Desktop-first
- Theme: Dark, minimal, data-focused
- Background: Deep charcoal/near-black (#0f1419)
- Primary Accent: Teal/Cyan (#2dd4bf)
- Text Primary: White (#ffffff)
- Font: Clean sans-serif (Inter, SF Pro, or system default)
- Layout: Centered content, max-width container
**Page Structure:**
1. Header with title "Achievements" and navigation
2. Badge grid showing locked/unlocked states with icons
3. Progress section with milestone bars
4. Footer with links to other pagesValidation Rules
Before completing an iteration, validate your baton:
- [ ]
pagefrontmatter field exists and is a valid filename - [ ] Prompt includes the design system block
- [ ] Prompt describes a page NOT already in
SITE.mdsitemap - [ ] Prompt includes specific page structure details