Release: v0.3.0

New: Visual Tokens

Brand direction now auto-derives concrete visual values (colors, typography, spacing) during recipe-blueprint. Prototypes reference these tokens directly, producing consistent visuals across multiple prototypes.

• Token values are auto-derived from directional sections and reference products
• prototype-generator uses tokens as CSS custom properties when available (Path A), with fallback to directional inference (Path B) or design-principles-only (Path C)

New: recipe-refine-visuals

Optional side-workflow for design experts to refine auto-derived Visual Tokens with professional judgment. Updates the same brand-direction.md — downstream consumers are unaware which path produced the tokens.

New: Design Context in PRD

PRD now carries abstract design intent for downstream UI specification:

• Design principles, tone & voice, guardrails (do/don't with preferred alternatives), and visual reference links
• Stable AC IDs (AC-001 format) across all requirements for downstream traceability

Inspiration

The Visual Tokens concept was inspired by DESIGN.md (Google Stitch) — a format for capturing design systems in plain markdown that AI coding agents can consume. This release adapts the idea for the discovery phase: auto-deriving concrete tokens from directional decisions rather than requiring a complete design system upfront.

How it fits together

recipe-blueprint → brand-direction.md (direction + auto-derived tokens)
                          ↑ optional
              recipe-refine-visuals (expert refinement)
                          ↓
              prototype-generator (tokens applied directly)

recipe-define → PRD with Design Context (abstract intent for UI Spec)