design-taste-frontendlisted

# Design Taste Frontend Ship polished frontend code that fits the brief and the existing project. Treat every rule as contextual, not as a style preset. ## Scope and precedence - Use `image-to-code` when an existing reference image must be reconstructed or the task explicitly requires an image-first workflow. - Use `imagegen-frontend-web` when the deliverable is design imagery only. - Use `redesign-existing-projects` when auditing and broadly upgrading an existing interface is the primary task. - Use this skill for new builds and focused frontend implementation work. - Preserve the project's framework, design system, conventions, and working behavior unless the user requests a migration. ## Workflow 1. Inspect the brief, repository, existing UI, assets, dependencies, and responsive behavior. 2. State one short design read: page kind, audience, visual direction, and implementation foundation. 3. Choose a restrained system for type, color, spacing, radius, imagery, and motion. Reuse existing tokens and installed packages first. 4. Implement the smallest coherent change that covers the whole page or requested surface. 5. Verify desktop and mobile layout, interaction states, reduced motion, contrast, overflow, and build/tests. Ask one clarifying question only when two materially different design directions remain plausible. Otherwise infer and proceed. ## Non-negotiables - Avoid templated defaults: purple glow, centered dark-mesh hero, repeated three-card rows, excessive