recipe-refine-visualslisted

**Context**: Refine the Visual Tokens section of `docs/product/design/brand-direction.md` with design expertise. This recipe reads the existing brand direction (including auto-derived tokens from `recipe-blueprint`) and lets a design expert override specific values with professional judgment. The output is the same `brand-direction.md` file — downstream consumers (prototype-generator, UI Spec) read it without knowing which path produced the tokens. ## When to Use - After `recipe-blueprint` has completed and `brand-direction.md` exists with auto-derived Visual Tokens - When a design expert is available and wants to refine the visual system - **This recipe is entirely optional** — auto-derived tokens are sufficient for prototype generation ## Orchestrator Definition **Execution Protocol**: 1. **Follow the refinement flow** defined below 2. **Stop at every `[STOP — BLOCKING]` marker** — present findings and CANNOT proceed until user explicitly confirms ## Workflow Overview ``` Input (existing brand-direction.md with auto-derived tokens) ↓ 1. Context Reading → Read brand direction + design principles + personas ↓ 2. Token Review → Present current tokens with their derivation rationale ↓ 3. Expert Refinement → User specifies overrides [Stop: User confirms changes] ↓ Output: Updated Visual Tokens in docs/product/design/brand-direction.md ``` ## Execution Decision Flow ### 1. Context Reading **Gate: `docs/product/design/brand-direction.md` must exist with a