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-design-423description: 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.).4---5
6# Frontend Design Skill
7
8Design 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.
9
10## When to Use
11
12Use this skill when the user wants to:
13- Create a new web page, landing page, dashboard, or app UI
14- Design or redesign frontend components or screens
15- Improve typography, layout, color, motion, or overall visual polish
16- Convert a concept or brief into a high‑fidelity, coded interface
17
18## Inputs to Gather (or Assume)
19
20Before coding, identify:
21- **Purpose & audience**: What problem does this UI solve? Who uses it?
22- **Brand/voice**: Any reference brands, tone, or visual inspiration?
23- **Technical constraints**: Framework, library, CSS strategy, accessibility, performance
24- **Content constraints**: Required copy, assets, data, features
25
26If the user did not provide this, ask **2–4 targeted questions**, or state reasonable assumptions in a short preface.
27
28## Design Thinking (Required)
29
30Commit to a **single, bold aesthetic direction**. Name it and execute it consistently. Examples:
31- Brutalist / raw / utilitarian
32- Editorial / magazine / typographic
33- Luxury / refined / minimal
34- Retro‑futuristic / cyber / neon
35- Art‑deco / geometric / ornamental
36- Handcrafted / organic / textured
37
38**Avoid generic AI aesthetics.** No “default” fonts, color schemes, or stock layouts.
39
40Before writing code, define the system:
411. **Visual direction** — one sentence that describes the vibe
422. **Differentiator** — what should be memorable about this UI?
433. **Typography system** — display + body fonts, scale, weight, casing
444. **Color system** — dominant, accent, neutral; define as CSS variables
455. **Layout strategy** — grid rhythm, spacing scale, hierarchy plan
466. **Motion strategy** — 1–2 meaningful interaction moments
47
48If the user wants code only, skip the explanation but still follow this internally.
49
50## Implementation Principles
51
52- **Working code**: HTML/CSS/JS or framework code that runs as‑is
53- **Semantic & accessible**: headings, labels, focus states, keyboard nav
54- **Responsive**: fluid layouts, breakpoints, responsive typography
55- **Tokenized styling**: CSS variables for colors, spacing, radii, shadows
56- **Modern layout**: prefer CSS Grid/Flex, avoid brittle positioning hacks
57
58## Aesthetic Guidelines
59
60### Typography
61- Typography should define the voice of the design
62- Avoid default fonts (Inter, Roboto, Arial, system stacks)
63- Use a **distinct display font** + a **refined body font**
64- Implement a clear hierarchy (size, weight, spacing, casing)
65
66### Color & Theme
67- Commit to a palette with a strong point‑of‑view
68- Avoid timid, overused gradients (e.g., purple‑to‑pink on white)
69- Use contrast intentionally and check legibility
70
71### Composition & Layout
72- Encourage asymmetry, scale contrast, overlap, or grid breaks
73- Use negative space deliberately (or controlled density if maximalist)
74- Create visual rhythm and hierarchy through spacing and alignment
75
76### Detail & Atmosphere
77- Add texture or depth when appropriate (noise, grain, subtle patterns)
78- Use shadows/glows only when they serve the concept
79- Consider unique borders, masks, or clip‑paths for distinct shapes
80
81### Motion & Interaction
82- Use motion sparingly but meaningfully
83- Favor one standout interaction over many tiny ones
84- Honor `prefers-reduced-motion`
85
86## Avoid
87
88- Cookie‑cutter hero + 3 card layouts
89- Generic gradients and default font choices
90- Unmotivated decorative elements
91- Overly flat, characterless component libraries
92
93## Deliverables
94
95- Provide full code with file names or component boundaries
96- Make customization easy with CSS variables or config objects
97- If assets are needed, provide inline SVGs or generative CSS patterns
98
99## Quality Checklist (Self‑validate)
100
101- Aesthetic direction is unmistakable
102- Typography feels intentional and expressive
103- Layout and spacing are consistent and purposeful
104- Color palette feels cohesive and legible
105- Interactions enhance the experience without clutter
106- Code runs as provided and is production‑ready
107
108**Remember:** a design is only as strong as its commitment. Choose a direction and execute it relentlessly.