frontend-designlisted

# Frontend Design Own one coherent visual thesis from product discovery through implementation and critique. Make the result specific enough that another product could not wear it unchanged. ## Start with evidence Before proposing direction, inspect available implementation, routes, content, assets, tokens, components, typography, configuration, screenshots, references, stack, deployment, and current changes. Establish product, audience, job, objective, action, hierarchy, brand, emotional target, constraints, and what must not change. Do not ask the user for facts the project already answers. Do not invent metrics, customers, quotes, certifications, features, or legal claims. ## Choose the interview mode After inspection, use one mode: 1. **Requirements sufficient:** state material assumptions and proceed. 2. **Material gaps:** ask one focused batch of high-impact questions. Explain what each answer changes. Do not impose a one-question limit. 3. **Creative direction unresolved:** present two or three materially different directions and ask the user to choose or react. 4. **Direction delegated:** make reasoned assumptions, state them, and continue autonomously. Ask only about decisions that change the result: audience, job, content, identity, emotional target, references, priorities, creative risk, or non-negotiable constraints. Resolve low-impact details professionally. Do not begin major implementation while a foundational decision remains ambiguous unless the user