taste-skill

# Taste Skill Use the existing stack and brand context to deliver a real, visually distinctive frontend. This skill is not for dense admin tools, data tables, native mobile interfaces, or ordinary one-line UI fixes. ## Route - For implementing or reviewing a website: read [references/web-design.md](references/web-design.md). - For generating visual concepts or section-specific assets before implementation: read [references/visual-concepts.md](references/visual-concepts.md). Load only the relevant guide. If the user asks for both concept work and implementation, use the concept output as evidence for the implementation rather than creating an unrelated second direction. ## Working contract - Inspect the existing routes, components, styles, content, and brand assets that affect the requested surface. Inspect supplied URLs or images before claiming to use them. - Infer a coherent visual direction from audience, message, brand, and conversion goal. Ask only when two materially different directions remain equally plausible. - Preserve framework, routes, copy meaning, analytics, and accessibility behavior unless the user asks to change them. - Prefer real brand and product assets. Generate or source new assets only when they serve a clear section role. - Implement the requested surface rather than stopping at a plan or mockup unless the user requested only those artifacts. - Inspect the rendered result at relevant desktop and mobile sizes, fix visible or functional failures, and recheck affected views. Completion means the requested page or concepts exist, the design system is coherent, key interactions and responsive states work, the rendered result has been inspected, and failures found during inspection have been fixed and rechecked.