frontend-design-taste

# Frontend Design Taste — distinctive direction, not templated defaults Approach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. The client has already rejected templated proposals and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography and layout that are specific to this brief, and take one real aesthetic risk you can justify. This skill defines the DIRECTION. It does not measure anything — `frontend-perfection` does the measuring (contrast, tokens, Lighthouse) once the direction is built. ## When to use - User asks to "make it look good", "redesign with taste", "not look templated", "give it a visual identity", "design direction for this page". - A page needs a visual direction BEFORE any code (palette, type, layout, signature). - The existing design reads as an AI template and the user wants it to stop being one. ## Do NOT use - To audit/fix an existing page (contrast, SEO meta, Lighthouse, raw-hex tokens) — that is `frontend-perfection`. - For SEO / Core Web Vitals / schema.org — that is `seo-toolkit`. - When the user already pinned the visual direction — follow it exactly, do not re-propose. ## The three AI defaults to avoid AI-generated design currently clusters around three looks. All three are legitimate for SOME briefs, but they are defaults, not choices, and they appear regardless of subject: 1. **Warm cream backgr...