frontend-designlisted

# Frontend Design Use this skill whenever the task touches frontend appearance or interaction: building UI, editing app screens, improving UX, styling components, creating web artifacts, React/Next.js work, HTML/CSS/JS pages, dashboards, landing pages, forms, charts, motion, responsiveness, or visual polish. The goal is clean, intentional, production-grade UI that looks designed for the product, not generated from a generic template. ## Operating Rules 1. Read the existing app first. Match its framework, component patterns, spacing scale, state management, naming, and design system unless the user asks for a new direction. 2. Make the actual usable interface, not a marketing explanation of features. Avoid visible instructional copy unless the product genuinely needs it. 3. Prefer conservative, durable UI for tools, SaaS, settings, dashboards, admin, CRM, and operational apps: dense enough to scan, restrained, predictable, and efficient. 4. For expressive sites, portfolios, games, and editorial pages, choose a clear visual direction tied to the subject. Distinctive is good; random decoration is not. 5. Check responsive behavior. Text must fit inside buttons, cards, sidebars, tables, and compact controls at mobile and desktop sizes. 6. Verify the result when possible with the browser/dev server/screenshot flow available in the environment. ## Anti-Slop Defaults Do not default to: - Purple, indigo, violet, or blue-purple gradients. - Beige/cream/tan monochrome pages, dark