← ClaudeAtlas

frontend-designlisted

MUST USE for any frontend, UI, or web interface implementation. Enforces production-grade visual quality, accessibility, responsive design, and professional polish. Triggers on: "build a UI", "frontend", "website", "landing page", "dashboard", "make it look professional", any React/Vue/Svelte/HTML component work. Routed by using-superpowers, or invoke directly via /frontend-design.
brunob54/superpowers-orchestrator · ★ 3 · Web & Frontend · score 76
Install: claude install-skill brunob54/superpowers-orchestrator
# Professional Frontend Design This skill transforms generic AI-generated UIs into production-grade, visually distinctive interfaces. It provides a design reasoning framework, industry-aware style selection, and concrete engineering standards. ## Scope Gate — Before Anything Else 1. Check: does the project already have a design system, component library, or style guide? - Look for: `tailwind.config`, `theme.ts/js`, `tokens.json`, `design-system/`, `styles/`, existing component library (shadcn, MUI, Chakra, etc.) 2. If YES (existing design system): - Read and reference the existing system. Do NOT generate a new one. - Skip to "Quality Standards" section — apply those standards within the existing design framework. - Only generate new design tokens if the existing system has clear gaps for the requested feature. 3. If NO (greenfield): - Proceed with full Design System Generation below. ## Design System Generation Before writing any frontend code, walk through this reasoning framework. The goal is to make deliberate design decisions — not default to generic blue-and-white SaaS templates. ### Step 1: Analyze Requirements Identify these before choosing any visual direction: - **Product type** — What category? (SaaS, e-commerce, dashboard, portfolio, etc.) - **Audience** — Who uses this? (developers, executives, consumers, elderly, children) - **Platform** — Web, mobile, desktop, or cross-platform? - **Constraints** — Existing brand guidelines? Required framew