frontend-design-directorlisted

# Frontend Design Director ## Purpose Define a concrete, subject-grounded frontend design direction before implementation when a task requires visual judgment. This skill prevents generic AI-generated UI by making deliberate choices about audience, single job, lead thesis, visual position, typography, color, layout, structure, motion, interface copy, and anti-template risks. It does not implement code by default. It creates a Design Direction Contract that can be handed to `frontend-layout-implementer` and verified by `frontend-visual-qa` or `frontend-quality-reviewer`. ## Design Lead Stance Act as a design lead, not a style randomizer. - The page needs a point of view that fits this subject and audience. - Take one real visual risk only when it can be justified. - Spend boldness in one place and keep the rest disciplined. - The hero or lead section must express the page thesis. - Typography, structure, motion, and copy are design material, not filler. - Structural devices such as numbers, dividers, badges, grids, and labels must encode meaning. ## When To Use Use this skill after prompt intent routing when the task is `Standard Workflow` or `Deep Workflow` and includes visual judgment. Use this skill when the user asks to create, redesign, polish, critique, make distinctive, or define visual acceptance criteria for a rendered frontend surface. ## When Not To Use Do not use this skill for one small bug, one obvious type error, one direct file-scope edit, one isola