What problem does it solve? Without a User Experience Document, code planners fall back to generic component-library defaults, producing internally consistent but visually bland output. This Skill walks you through authoring a UXD that anchors visual and interaction decisions to concrete reference apps, brand-voice choices, and polish criteria before implementation begins. ## Core Features & Use Cases - Template-Driven Authoring: Loads the UXD template and walks through all required sections, from aesthetic anchors and design tokens to accessibility-as-delight and anti-patterns. - Reference-Anchor Discipline: Rejects reference apps without screenshots and brand voices stated only as adjectives, enforcing concrete visual decisions. - ASAE Quality Gate: Runs a design-domain validation pass on the draft before saving, checking state catalogs, contrast ratios, and asset existence. - Use Case: Before running a D2R code plan for a new SvelteKit app, invoke this Skill to produce an approved UXD with screenshots, palette hex values, and per-component state catalogs saved to the project planning directory. ## Quick Start Ask the assistant to write a UXD for your project using the write-uxd skill, providing the project name and filename prefix.
