Frontend Design Skill
Design and implement memorable frontend interfaces with a clear, intentional aesthetic. The output must be real, working code — not just mood boards. This skill is about design thinking + execution: every visual choice should be rooted in purpose and context.
When to Use
Use this skill when the user wants to:
- Create a new web page, landing page, dashboard, or app UI
- Design or redesign frontend components or screens
- Improve typography, layout, color, motion, or overall visual polish
- Convert a concept or brief into a high‑fidelity, coded interface
Inputs to Gather (or Assume)
Before coding, identify:
- Purpose & audience: What problem does this UI solve? Who uses it?
- Brand/voice: Any reference brands, tone, or visual inspiration?
- Technical constraints: Framework, library, CSS strategy, accessibility, performance
- Content constraints: Required copy, assets, data, features
If the user did not provide this, ask 2–4 targeted questions, or state reasonable assumptions in a short preface.
Design Thinking (Required)
Commit to a single, bold aesthetic direction. Name it and execute it consistently. Examples:
- Brutalist / raw / utilitarian
- Editorial / magazine / typographic
- Luxury / refined / minimal
- Retro‑futuristic / cyber / neon
- Art‑deco / geometric / ornamental
- Handcrafted / organic / textured
Avoid generic AI aesthetics. No “default” fonts, color schemes, or stock layouts.
Before writing code, define the system:
- Visual direction — one sentence that describes the vibe
- Differentiator — what should be memorable about this UI?
- Typography system — display + body fonts, scale, weight, casing
- Color system — dominant, accent, neutral; define as CSS variables
- Layout strategy — grid rhythm, spacing scale, hierarchy plan
- Motion strategy — 1–2 meaningful interaction moments
If the user wants code only, skip the explanation but still follow this internally.
Implementation Principles
- Working code: HTML/CSS/JS or framework code that runs as‑is
- Semantic & accessible: headings, labels, focus states, keyboard nav
- Responsive: fluid layouts, breakpoints, responsive typography
- Tokenized styling: CSS variables for colors, spacing, radii, shadows
- Modern layout: prefer CSS Grid/Flex, avoid brittle positioning hacks
Aesthetic Guidelines
Typography
- Typography should define the voice of the design
- Avoid default fonts (Inter, Roboto, Arial, system stacks)
- Use a distinct display font + a refined body font
- Implement a clear hierarchy (size, weight, spacing, casing)
Color & Theme
- Commit to a palette with a strong point‑of‑view
- Avoid timid, overused gradients (e.g., purple‑to‑pink on white)
- Use contrast intentionally and check legibility
Composition & Layout
- Encourage asymmetry, scale contrast, overlap, or grid breaks
- Use negative space deliberately (or controlled density if maximalist)
- Create visual rhythm and hierarchy through spacing and alignment
Detail & Atmosphere
- Add texture or depth when appropriate (noise, grain, subtle patterns)
- Use shadows/glows only when they serve the concept
- Consider unique borders, masks, or clip‑paths for distinct shapes
Motion & Interaction
- Use motion sparingly but meaningfully
- Favor one standout interaction over many tiny ones
- Honor
prefers-reduced-motion
Avoid
- Cookie‑cutter hero + 3 card layouts
- Generic gradients and default font choices
- Unmotivated decorative elements
- Overly flat, characterless component libraries
Deliverables
- Provide full code with file names or component boundaries
- Make customization easy with CSS variables or config objects
- If assets are needed, provide inline SVGs or generative CSS patterns
Quality Checklist (Self‑validate)
- Aesthetic direction is unmistakable
- Typography feels intentional and expressive
- Layout and spacing are consistent and purposeful
- Color palette feels cohesive and legible
- Interactions enhance the experience without clutter
- Code runs as provided and is production‑ready
Remember: a design is only as strong as its commitment. Choose a direction and execute it relentlessly.
1---2name: frontend-design3description: Design and implement distinctive, production-ready frontend interfaces with strong aesthetic direction. Use when asked to create or restyle web pages, components, or applications (HTML/CSS/JS, React, Vue, etc.).4license: MIT (source: https://github.com/mitsuhiko/agent-stuff/blob/e70765---67# Frontend Design Skill89Design and implement memorable frontend interfaces with a clear, intentional aesthetic. The output must be real, working code — not just mood boards. This skill is about **design thinking + execution**: every visual choice should be rooted in purpose and context.1011## When to Use1213Use this skill when the user wants to:14- Create a new web page, landing page, dashboard, or app UI15- Design or redesign frontend components or screens16- Improve typography, layout, color, motion, or overall visual polish17- Convert a concept or brief into a high‑fidelity, coded interface1819## Inputs to Gather (or Assume)2021Before coding, identify:22- **Purpose & audience**: What problem does this UI solve? Who uses it?23- **Brand/voice**: Any reference brands, tone, or visual inspiration?24- **Technical constraints**: Framework, library, CSS strategy, accessibility, performance25- **Content constraints**: Required copy, assets, data, features2627If the user did not provide this, ask **2–4 targeted questions**, or state reasonable assumptions in a short preface.2829## Design Thinking (Required)3031Commit to a **single, bold aesthetic direction**. Name it and execute it consistently. Examples:32- Brutalist / raw / utilitarian33- Editorial / magazine / typographic34- Luxury / refined / minimal35- Retro‑futuristic / cyber / neon36- Art‑deco / geometric / ornamental37- Handcrafted / organic / textured3839**Avoid generic AI aesthetics.** No “default” fonts, color schemes, or stock layouts.4041Before writing code, define the system:421. **Visual direction** — one sentence that describes the vibe432. **Differentiator** — what should be memorable about this UI?443. **Typography system** — display + body fonts, scale, weight, casing454. **Color system** — dominant, accent, neutral; define as CSS variables465. **Layout strategy** — grid rhythm, spacing scale, hierarchy plan476. **Motion strategy** — 1–2 meaningful interaction moments4849If the user wants code only, skip the explanation but still follow this internally.5051## Implementation Principles5253- **Working code**: HTML/CSS/JS or framework code that runs as‑is54- **Semantic & accessible**: headings, labels, focus states, keyboard nav55- **Responsive**: fluid layouts, breakpoints, responsive typography56- **Tokenized styling**: CSS variables for colors, spacing, radii, shadows57- **Modern layout**: prefer CSS Grid/Flex, avoid brittle positioning hacks5859## Aesthetic Guidelines6061### Typography62- Typography should define the voice of the design63- Avoid default fonts (Inter, Roboto, Arial, system stacks)64- Use a **distinct display font** + a **refined body font**65- Implement a clear hierarchy (size, weight, spacing, casing)6667### Color & Theme68- Commit to a palette with a strong point‑of‑view69- Avoid timid, overused gradients (e.g., purple‑to‑pink on white)70- Use contrast intentionally and check legibility7172### Composition & Layout73- Encourage asymmetry, scale contrast, overlap, or grid breaks74- Use negative space deliberately (or controlled density if maximalist)75- Create visual rhythm and hierarchy through spacing and alignment7677### Detail & Atmosphere78- Add texture or depth when appropriate (noise, grain, subtle patterns)79- Use shadows/glows only when they serve the concept80- Consider unique borders, masks, or clip‑paths for distinct shapes8182### Motion & Interaction83- Use motion sparingly but meaningfully84- Favor one standout interaction over many tiny ones85- Honor `prefers-reduced-motion`8687## Avoid8889- Cookie‑cutter hero + 3 card layouts90- Generic gradients and default font choices91- Unmotivated decorative elements92- Overly flat, characterless component libraries9394## Deliverables9596- Provide full code with file names or component boundaries97- Make customization easy with CSS variables or config objects98- If assets are needed, provide inline SVGs or generative CSS patterns99100## Quality Checklist (Self‑validate)101102- Aesthetic direction is unmistakable103- Typography feels intentional and expressive104- Layout and spacing are consistent and purposeful105- Color palette feels cohesive and legible106- Interactions enhance the experience without clutter107- Code runs as provided and is production‑ready108109**Remember:** a design is only as strong as its commitment. Choose a direction and execute it relentlessly.