flyee 0.1.0

package/core/skills/state-machine/SKILL.md

@@ -0,0 +1,264 @@
+---
+name: state-machine
+description: Local project state management with .flyee/ directory. Derived state dashboard, work hierarchy (Sprint→Phase→Task), decisions register. Absorbed from GSD-2 state.ts patterns.
+---
+
+# State Machine
+
+> **Absorbed from:** GSD-2 `state.ts`, `GSD-WORKFLOW.md`, `STATE.md`
+> **Purpose:** Give the agent a "memory" — know where it is, what was done, what's next.
+
+---
+
+## 🎯 PURPOSE
+
+Without a state machine, every new session starts from zero. The agent has to re-discover:
+- What sprint is active?
+- Which tasks are done?
+- What was the last decision?
+
+The `.flyee/` directory solves this with **derived state** — a single file that answers "where am I?"
+
+---
+
+## 📁 .flyee/ DIRECTORY
+
+Created automatically when the agent starts work. **Partially gitignored.**
+
+```
+.flyee/                              ← Project state root
+├── STATE.md                         ← 🔴 DERIVED (gitignored) — "where am I?"
+├── DECISIONS.md                     ← ✅ VERSIONED — append-only decision log
+├── session-lock.json                ← 🔴 GITIGNORED — crash recovery lock
+├── cost-log.jsonl                   ← 🔴 GITIGNORED — LLM cost tracking
+└── sprints/                         ← ✅ VERSIONED — work hierarchy
+    └── S{NN}/                       ← Sprint (≈ GSD-2 Milestone)
+        ├── CONTEXT.md               ← Sprint context & constraints
+        ├── ROADMAP.md               ← Phases with checkboxes + boundary maps
+        ├── SUMMARY.md               ← Written when sprint completes
+        └── phases/                  ← Phase (≈ GSD-2 Slice)
+            └── P{NN}/
+                ├── PLAN.md          ← Tasks with must-haves
+                ├── SUMMARY.md       ← Written when phase completes
+                ├── continue.md      ← Resume point (ephemeral, gitignored)
+                └── tasks/
+                    ├── T{NN}-PLAN.md    ← Task plan + Truths/Artifacts/Key Links
+                    └── T{NN}-SUMMARY.md ← Written when task completes
+```
+
+### .gitignore entries for .flyee/
+
+```gitignore
+# Flyee state (ephemeral)
+.flyee/STATE.md
+.flyee/session-lock.json
+.flyee/cost-log.jsonl
+.flyee/**/continue.md
+```
+
+---
+
+## 📊 STATE.md — Derived Dashboard
+
+**Generated, never edited manually.** Updated after every task/phase completion.
+
+```markdown
+# Project State
+
+> Auto-generated by @flyee state-machine. Do NOT edit manually.
+> Last updated: 2026-03-31T17:00:00Z
+
+## Active Work
+
+| Field | Value |
+|-------|-------|
+| **Sprint** | S09 — Blog & CMS |
+| **Phase** | P02 — Frontend Components (2/4 tasks done) |
+| **Task** | T03 — BlogCard component |
+| **Status** | executing |
+
+## Progress
+
+### S09 — Blog & CMS
+- [x] P01 — Backend API (3/3 tasks) ✅
+- [ ] P02 — Frontend Components (2/4 tasks)
+  - [x] T01 — BlogList page structure
+  - [x] T02 — Markdown parser
+  - [ ] **T03 — BlogCard component** ← ACTIVE
+  - [ ] T04 — Pagination
+- [ ] P03 — CMS Admin (0/3 tasks)
+- [ ] P04 — SEO & Meta (0/2 tasks)
+
+## Previous Sprints
+- S01–S08: ✅ Complete
+- S09: 🟡 In Progress (Phase 2/4)
+- S10–S18: ⏳ Pending
+
+## Next Action
+Implement BlogCard component per T03-PLAN.md must-haves.
+```
+
+### Derivation Rules
+
+1. **Sprint = active** if: has CONTEXT.md but no SUMMARY.md, and all dependency sprints are complete
+2. **Phase = active** if: first incomplete phase in ROADMAP.md with dependencies satisfied
+3. **Task = active** if: first incomplete task in active phase PLAN.md
+4. **Status** values: `pre-planning`, `planning`, `executing`, `verifying`, `summarizing`, `blocked`, `complete`
+
+---
+
+## 📖 DECISIONS.md — Append-Only Register
+
+**Versioned. Never delete entries. Only append.**
+
+```markdown
+# Decisions Register
+
+> Append-only log of technical decisions made during project execution.
+> Each entry is immutable once written.
+
+---
+
+## D001 — Use RSC for blog posts (2026-03-31)
+
+**Context:** Blog posts need fast initial load and SEO.
+**Decision:** Use React Server Components for blog rendering.
+**Rationale:** SSR performance, SEO friendliness, reduces client bundle.
+**Sprint:** S09 | **Phase:** P02 | **Task:** T01
+
+---
+
+## D002 — md-ast for Markdown parsing (2026-03-31)
+
+**Context:** Need to parse markdown with frontmatter for blog posts.
+**Decision:** Use md-ast (already in project) instead of adding remark.
+**Rationale:** Zero new dependencies. Already used for docs.
+**Sprint:** S09 | **Phase:** P02 | **Task:** T02
+```
+
+### When to write a decision
+
+- Choosing between 2+ viable options
+- Rejecting a common approach for a specific reason
+- Making a trade-off (performance vs simplicity, etc.)
+- Any decision that future-you would wonder "why did we do this?"
+
+---
+
+## 🔄 STATE DERIVATION PROTOCOL
+
+When the agent starts a session:
+
+```
+1. IF .flyee/STATE.md exists:
+   → Read it. Know "where am I?"
+   → Check continue.md in active phase → if exists, RESUME from there
+
+2. IF .flyee/STATE.md does NOT exist:
+   → Read .flyee/sprints/ directory
+   → Derive state from ROADMAP/PLAN files
+   → Generate STATE.md
+
+3. IF .flyee/ does NOT exist:
+   → This is a new project or first @flyee session
+   → Create .flyee/ with minimal STATE.md
+   → ASK user about current project state
+```
+
+### State Update Triggers
+
+| Event | Action |
+|-------|--------|
+| Task completed | Mark checkbox in PLAN.md, re-derive STATE.md |
+| Phase completed | Write phase SUMMARY.md, mark in ROADMAP.md, re-derive |
+| Sprint completed | Write sprint SUMMARY.md, re-derive |
+| Decision made | Append to DECISIONS.md |
+| Session start | Read STATE.md + check continue.md |
+| Session end | Write continue.md if mid-task |
+
+---
+
+## 📋 ROADMAP.md FORMAT
+
+```markdown
+# S09 — Blog & CMS
+
+## Phases
+
+### P01 — Backend API
+- [x] T01 — Post CRUD endpoints
+- [x] T02 — Markdown storage
+- [x] T03 — Category system
+**Status:** ✅ Complete
+
+### P02 — Frontend Components
+depends: P01
+- [x] T01 — BlogList page structure
+- [x] T02 — Markdown parser
+- [ ] T03 — BlogCard component
+- [ ] T04 — Pagination
+**Status:** 🟡 In Progress
+
+### P03 — CMS Admin
+depends: P01
+- [ ] T01 — Post editor
+- [ ] T02 — Media upload
+- [ ] T03 — Draft/publish flow
+**Status:** ⏳ Pending
+
+## Boundary Map
+
+### P01 → P02
+**Produces:**
+- `types/post.ts` → Post, Author interfaces
+- `api/posts/route.ts` → GET /api/posts, POST /api/posts
+
+**Consumes:** nothing (leaf)
+
+### P01 → P03
+**Produces:**
+- `api/posts/route.ts` → PUT, DELETE handlers
+- `types/post.ts` → Post interface
+
+**Consumes:** nothing (leaf)
+
+### P02, P03 → P04
+**Produces:**
+- `components/BlogCard.tsx` → BlogCard component
+- `pages/admin/posts/` → CMS pages
+
+**Consumes from P01:**
+- `api/posts/route.ts` → all handlers
+```
+
+---
+
+## 🏗️ CREATING A NEW SPRINT
+
+When `/new-task` or `/new-project` creates a sprint:
+
+```
+1. Create .flyee/sprints/S{NN}/
+2. Write CONTEXT.md (decisions, constraints, goals)
+3. Write ROADMAP.md (phases, tasks, boundary map)
+4. Update STATE.md
+5. IF connected to Flyee SaaS: sync via bridge.py
+```
+
+---
+
+## ⚡ QUICK REFERENCE
+
+```bash
+# Check current state
+cat .flyee/STATE.md
+
+# Check decisions
+cat .flyee/DECISIONS.md
+
+# Check sprint roadmap
+cat .flyee/sprints/S09/ROADMAP.md
+
+# Check active task plan
+cat .flyee/sprints/S09/phases/P02/tasks/T03-PLAN.md
+```

package/core/skills/stitch-loop/README.md

@@ -0,0 +1,54 @@
+# Stitch Build Loop Skill
+
+Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern.
+
+## Install
+
+```bash
+npx add-skill google-labs-code/stitch-skills --skill stitch-loop --global
+```
+
+## What It Does
+
+Enables continuous, autonomous website development through a "baton" system:
+
+1. Agent reads task from `next-prompt.md`
+2. Generates page via Stitch MCP tools
+3. Integrates into site structure
+4. Writes next task to continue the loop
+
+## Prerequisites
+
+- Stitch MCP Server access
+- A `DESIGN.md` file (generate with the `design-md` skill)
+- A `SITE.md` file for project context
+
+## Example Prompt
+
+```text
+Read my next-prompt.md and generate the page using Stitch, then prepare the next iteration.
+```
+
+## Skill Structure
+
+```
+stitch-loop/
+├── SKILL.md              — Core pattern instructions
+├── README.md             — This file
+├── resources/
+│   ├── baton-schema.md   — Baton file format spec
+│   └── site-template.md  — SITE.md/DESIGN.md templates
+└── examples/
+    ├── next-prompt.md    — Example baton
+    └── SITE.md           — Example site constitution
+```
+
+## Works With
+
+- **`design-md` skill**: Generate `DESIGN.md` from existing Stitch screens
+- **CI/CD**: GitHub Actions can trigger new iterations on push
+- **Agent chains**: Dispatch to other agents (Jules, etc.)
+
+## Learn More
+
+See [SKILL.md](./SKILL.md) for complete instructions.

package/core/skills/stitch-loop/SKILL.md

@@ -0,0 +1,203 @@
+---
+name: stitch-loop
+description: Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern
+allowed-tools:
+  - "stitch*:*"
+  - "chrome*:*"
+  - "Read"
+  - "Write"
+  - "Bash"
+---
+
+# Stitch Build Loop
+
+You are an **autonomous frontend builder** participating in an iterative site-building loop. Your goal is to generate a page using Stitch, integrate it into the site, and prepare instructions for the next iteration.
+
+## Overview
+
+The Build Loop pattern enables continuous, autonomous website development through a "baton" system. Each iteration:
+1. Reads the current task from a baton file (`next-prompt.md`)
+2. Generates a page using Stitch MCP tools
+3. Integrates the page into the site structure
+4. Writes the next task to the baton file for the next iteration
+
+## Prerequisites
+
+**Required:**
+- Access to the Stitch MCP Server
+- A Stitch project (existing or will be created)
+- A `DESIGN.md` file (generate one using the `design-md` skill if needed)
+- A `SITE.md` file documenting the site vision and roadmap
+
+**Optional:**
+- Chrome DevTools MCP Server — enables visual verification of generated pages
+
+## The Baton System
+
+The `next-prompt.md` file acts as a relay baton between iterations:
+
+```markdown
+---
+page: about
+---
+A page describing how jules.top tracking works.
+
+**DESIGN SYSTEM (REQUIRED):**
+[Copy from DESIGN.md Section 6]
+
+**Page Structure:**
+1. Header with navigation
+2. Explanation of tracking methodology
+3. Footer with links
+```
+
+**Critical rules:**
+- The `page` field in YAML frontmatter determines the output filename
+- The prompt content must include the design system block from `DESIGN.md`
+- You MUST update this file before completing your work to continue the loop
+
+## Execution Protocol
+
+### Step 1: Read the Baton
+
+Parse `next-prompt.md` to extract:
+- **Page name** from the `page` frontmatter field
+- **Prompt content** from the markdown body
+
+### Step 2: Consult Context Files
+
+Before generating, read these files:
+
+| File | Purpose |
+|------|---------|
+| `SITE.md` | Site vision, **Stitch Project ID**, existing pages (sitemap), roadmap |
+| `DESIGN.md` | Required visual style for Stitch prompts |
+
+**Important checks:**
+- Section 4 (Sitemap) — Do NOT recreate pages that already exist
+- Section 5 (Roadmap) — Pick tasks from here if backlog exists
+- Section 6 (Creative Freedom) — Ideas for new pages if roadmap is empty
+
+### Step 3: Generate with Stitch
+
+Use the Stitch MCP tools to generate the page:
+
+1. **Discover namespace**: Run `list_tools` to find the Stitch MCP prefix
+2. **Get or create project**: 
+   - If `stitch.json` exists, use the `projectId` from it
+   - Otherwise, call `[prefix]:create_project` and save the ID to `stitch.json`
+3. **Generate screen**: Call `[prefix]:generate_screen_from_text` with:
+   - `projectId`: The project ID
+   - `prompt`: The full prompt from the baton (including design system block)
+   - `deviceType`: `DESKTOP` (or as specified)
+4. **Retrieve assets**: Call `[prefix]:get_screen` to get:
+   - `htmlCode.downloadUrl` — Download and save as `queue/{page}.html`
+   - `screenshot.downloadUrl` — Download and save as `queue/{page}.png`
+
+### Step 4: Integrate into Site
+
+1. Move generated HTML from `queue/{page}.html` to `site/public/{page}.html`
+2. Fix any asset paths to be relative to the public folder
+3. Update navigation:
+   - Find existing placeholder links (e.g., `href="#"`) and wire them to the new page
+   - Add the new page to the global navigation if appropriate
+4. Ensure consistent headers/footers across all pages
+
+### Step 4.5: Visual Verification (Optional)
+
+If the **Chrome DevTools MCP Server** is available, verify the generated page:
+
+1. **Check availability**: Run `list_tools` to see if `chrome*` tools are present
+2. **Start dev server**: Use Bash to start a local server (e.g., `npx serve site/public`)
+3. **Navigate to page**: Call `[chrome_prefix]:navigate` to open `http://localhost:3000/{page}.html`
+4. **Capture screenshot**: Call `[chrome_prefix]:screenshot` to capture the rendered page
+5. **Visual comparison**: Compare against the Stitch screenshot (`queue/{page}.png`) for fidelity
+6. **Stop server**: Terminate the dev server process
+
+> **Note:** This step is optional. If Chrome DevTools MCP is not installed, skip to Step 5.
+
+### Step 5: Update Site Documentation
+
+Modify `SITE.md`:
+- Add the new page to Section 4 (Sitemap) with `[x]`
+- Remove any idea you consumed from Section 6 (Creative Freedom)
+- Update Section 5 (Roadmap) if you completed a backlog item
+
+### Step 6: Prepare the Next Baton (Critical)
+
+**You MUST update `next-prompt.md` before completing.** This keeps the loop alive.
+
+1. **Decide the next page**: 
+   - Check `SITE.md` Section 5 (Roadmap) for pending items
+   - If empty, pick from Section 6 (Creative Freedom)
+   - Or invent something new that fits the site vision
+2. **Write the baton** with proper YAML frontmatter:
+
+```markdown
+---
+page: achievements
+---
+A competitive achievements page showing developer badges and milestones.
+
+**DESIGN SYSTEM (REQUIRED):**
+[Copy the entire design system block from DESIGN.md]
+
+**Page Structure:**
+1. Header with title and navigation
+2. Badge grid showing unlocked/locked states
+3. Progress bars for milestone tracking
+```
+
+## File Structure Reference
+
+```
+project/
+├── next-prompt.md      # The baton — current task
+├── stitch.json         # Stitch project ID (persist this!)
+├── DESIGN.md           # Visual design system (from design-md skill)
+├── SITE.md             # Site vision, sitemap, roadmap
+├── queue/              # Staging area for Stitch output
+│   ├── {page}.html
+│   └── {page}.png
+└── site/public/        # Production pages
+    ├── index.html
+    └── {page}.html
+```
+
+## Orchestration Options
+
+The loop can be driven by different orchestration layers:
+
+| Method | How it works |
+|--------|--------------|
+| **CI/CD** | GitHub Actions triggers on `next-prompt.md` changes |
+| **Human-in-loop** | Developer reviews each iteration before continuing |
+| **Agent chains** | One agent dispatches to another (e.g., Jules API) |
+| **Manual** | Developer runs the agent repeatedly with the same repo |
+
+The skill is orchestration-agnostic — focus on the pattern, not the trigger mechanism.
+
+## Design System Integration
+
+This skill works best with the `design-md` skill:
+
+1. **First time setup**: Generate `DESIGN.md` using the `design-md` skill from an existing Stitch screen
+2. **Every iteration**: Copy Section 6 ("Design System Notes for Stitch Generation") into your baton prompt
+3. **Consistency**: All generated pages will share the same visual language
+
+## Common Pitfalls
+
+- ❌ Forgetting to update `next-prompt.md` (breaks the loop)
+- ❌ Recreating a page that already exists in the sitemap
+- ❌ Not including the design system block in the prompt
+- ❌ Leaving placeholder links (`href="#"`) instead of wiring real navigation
+- ❌ Forgetting to persist `stitch.json` after creating a new project
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| Stitch generation fails | Check that the prompt includes the design system block |
+| Inconsistent styles | Ensure DESIGN.md is up-to-date and copied correctly |
+| Loop stalls | Verify `next-prompt.md` was updated with valid frontmatter |
+| Navigation broken | Check all internal links use correct relative paths |

package/core/skills/stitch-loop/examples/SITE.md

@@ -0,0 +1,73 @@
+---
+stitch-project-id: 13534454087919359824
+---
+# Project Vision & Constitution
+
+> **AGENT INSTRUCTION:** Read this file before every iteration. It serves as the project's "Long-Term Memory." If `next-prompt.md` is empty, pick the highest priority item from Section 5 OR invent a new page that fits the project vision.
+
+## 1. Core Identity
+* **Project Name:** Oakwood Furniture Co.
+* **Stitch Project ID:** `13534454087919359824`
+* **Mission:** A premium online furniture showroom showcasing handcrafted, sustainable wood furniture.
+* **Target Audience:** Design-conscious homeowners, interior designers, eco-minded buyers.
+* **Voice:** Warm, refined, artisanal, and trustworthy.
+
+## 2. Visual Language (Stitch Prompt Strategy)
+*Strictly adhere to these descriptive rules when prompting Stitch. Do NOT use code.*
+
+* **The "Vibe" (Adjectives):**
+    * *Primary:* **Warm** (Inviting, cozy, natural materials).
+    * *Secondary:* **Minimal** (Clean layouts, breathing room, gallery-like).
+    * *Tertiary:* **Artisanal** (Handcrafted feel, attention to detail).
+
+* **Color Philosophy (Semantic):**
+    * **Backgrounds:** Warm barely-there cream (#FCFAFA). Soft, inviting canvas.
+    * **Accents:** Deep muted teal-navy (#294056) for CTAs and highlights.
+    * **Text:** Charcoal near-black (#2C2C2C) for headlines, soft gray (#6B6B6B) for body.
+
+## 3. Architecture & File Structure
+* **Root:** `site/public/`
+* **Asset Flow:** Stitch generates to `queue/` -> Validate -> Move to `site/public/`.
+* **Navigation Strategy:**
+    * **Global Header:** Logo, Shop, Collections, About, Contact.
+    * **Global Footer:** Sustainability, Craftsmanship, Shipping Info, Social Links.
+
+## 4. Live Sitemap (Current State)
+*The Agent MUST update this section when a new page is successfully merged.*
+
+* [x] `index.html` - Homepage with hero and featured collections.
+* [x] `collections.html` - Overview of furniture categories.
+* [x] `about.html` - Our story and craftsmanship philosophy.
+* [ ] `contact.html` - Contact form and showroom locations.
+
+## 5. The Roadmap (Backlog)
+*If `next-prompt.md` is empty or completed, pick the next task from here.*
+
+### High Priority
+- [ ] **Product Detail Page:** Template for individual furniture items.
+- [ ] **Contact Page:** Contact form with showroom map.
+
+### Medium Priority
+- [ ] **Sustainability Page:** Our commitment to eco-friendly practices.
+- [ ] **Care Guide:** How to maintain wood furniture.
+
+## 6. Creative Freedom Guidelines
+*When the backlog is empty, follow these guidelines to innovate.*
+
+1. **Stay On-Brand:** New pages must fit the "Warm + Minimal + Artisanal" vibe.
+2. **Enhance the Core:** Support the furniture shopping experience.
+3. **Naming Convention:** Use lowercase, descriptive filenames.
+
+### Ideas to Explore
+*Pick one, build it, then REMOVE it from this list.*
+
+- [ ] `materials.html` - Showcase of wood types and finishes
+- [ ] `custom.html` - Custom furniture ordering process
+- [ ] `gallery.html` - Customer homes featuring our furniture
+- [ ] `blog.html` - Design tips and furniture care articles
+
+## 7. Rules of Engagement
+1. Do not recreate pages in Section 4.
+2. Always update `next-prompt.md` before completing.
+3. Consume ideas from Section 6 when you use them.
+4. Keep the loop moving.

package/core/skills/stitch-loop/examples/next-prompt.md

@@ -0,0 +1,25 @@
+---
+page: contact
+---
+A warm, inviting contact page for Oakwood Furniture Co.
+
+**DESIGN SYSTEM (REQUIRED):**
+- Platform: Web, Desktop-first
+- Theme: Light, minimal, photography-first
+- Background: Warm barely-there cream (#FCFAFA)
+- Surface: Crisp very light gray (#F5F5F5) for cards
+- Primary Accent: Deep muted teal-navy (#294056) for buttons and links
+- Text Primary: Charcoal near-black (#2C2C2C) for headlines
+- Text Secondary: Soft warm gray (#6B6B6B) for body copy
+- Font: Modern sans-serif (Manrope or similar), clean and approachable
+- Buttons: Subtly rounded corners (8px), comfortable padding
+- Cards: Gently rounded corners (12px), whisper-soft shadows on hover
+- Layout: Centered content, max-width container, generous whitespace
+- No harsh shadows, no aggressive colors - serene and trustworthy
+
+**Page Structure:**
+1. **Header:** Navigation with logo, Shop, Collections, About, Contact (active)
+2. **Hero Section:** Warm headline "Get in Touch" with a brief welcome message
+3. **Contact Form:** Name, email, message fields with the teal-navy submit button
+4. **Showroom Info:** Address, hours, and an embedded map or beautiful showroom photo
+5. **Footer:** Sustainability, Craftsmanship, Shipping links, and social icons

package/core/skills/stitch-loop/resources/baton-schema.md

@@ -0,0 +1,61 @@
+# 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
+
+```yaml
+---
+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:
+
+1. **One-line description** with vibe/atmosphere keywords
+2. **Design System block** (required) — copied from `DESIGN.md` Section 6
+3. **Page Structure** — numbered list of sections/components
+
+## Example
+
+```markdown
+---
+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 pages
+```
+
+## Validation Rules
+
+Before completing an iteration, validate your baton:
+
+- [ ] `page` frontmatter field exists and is a valid filename
+- [ ] Prompt includes the design system block
+- [ ] Prompt describes a page NOT already in `SITE.md` sitemap
+- [ ] Prompt includes specific page structure details