google-stitch-frontend-brief-enhancerlisted

# Frontend Brief Enhancer ## Overview Turn vague UI language into a bounded, implementation-ready brief. Increase specificity without converting guesses into requirements or starting implementation. ## Workflow 1. **Preserve the request.** Quote the user's goal and non-negotiable wording. Inspect `DESIGN.md`, existing components, screenshots, or product copy when available. 2. **Classify every decision.** Separate **Confirmed requirements**, **Reversible assumptions**, and **Unresolved decisions**. Never invent features, workflows, data, metrics, customers, brand assets, or business rules. 3. **Translate vague language.** Convert words such as “premium,” “modern,” or “clean” into observable hierarchy, spacing, typography, color roles, composition, and interaction behavior. Use [ui-ux-keywords.md](references/ui-ux-keywords.md) for precise terms, not decoration by thesaurus. 4. **Specify the experience.** Cover purpose, audience, platform, page structure, content hierarchy, components, relevant states, responsiveness, accessibility, motion, content constraints, and boundaries. State when a category is not applicable or unknown. 5. **Write acceptance criteria.** Make each criterion observable: named viewport behavior, keyboard path, focus treatment, state coverage, token reuse, content integrity, and preserved behavior. Avoid “looks polished” or “works well.” 6. **Stop at the brief.** Use [brief-template.md](references/brief-template.md). Do not write code, install packages,