frontend-design

Generated source view for the actual executable engineering/frontend-design skill. The durable routing article is Frontend and Design Skills. Source: skills/engineering/frontend-design/SKILL.md

Runtime Source

Bundled Resources

These files are part of the executable skill folder and must be preserved with the skill source.

Description

Distinctive, production-grade frontend interfaces that reject generic AI aesthetics. Use when creating UI components, landing pages, design systems, or any frontend work. Triggers on "make it look good", "design direction", "avoid generic", "art direction", "design taste", "landing page", "UI design", or any frontend creation task. Based on anthropics/skills (259K weekly installs).

Skill Source

---
name: frontend-design
description: Distinctive, production-grade frontend interfaces that reject generic AI aesthetics. Use when creating UI components, landing pages, design systems, or any frontend work. Triggers on "make it look good", "design direction", "avoid generic", "art direction", "design taste", "landing page", "UI design", or any frontend creation task. Based on anthropics/skills (259K weekly installs).
origin: personal
source_slug: frontend-design
---

# Frontend Design

Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Real working code with exceptional attention to aesthetic details and creative choices.

## Design Thinking (Before Coding)

Commit to a BOLD aesthetic direction:

- **Purpose**: What problem does this interface solve? Who uses it?
- **Tone**: Pick an extreme — brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian
- **Constraints**: Technical requirements (framework, performance, accessibility)
- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone remembers?

Choose a clear conceptual direction and execute with precision. Bold maximalism and refined minimalism both work — the key is intentionality, not intensity.

## Frontend Aesthetics Pillars

### Typography
Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial, Inter, Roboto, system fonts. Pair a distinctive display font with a refined body font. Unexpected, characterful choices.

### Color & Theme
Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.

### Motion
Animations for effects and micro-interactions. CSS-only for HTML, Motion library for React. High-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions. Scroll-triggering and hover states that surprise.

### Spatial Composition
Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.

### Backgrounds & Visual Details
Atmosphere and depth over solid colors. Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, grain overlays.

## NEVER Use

- Overused font families (Inter, Roboto, Arial, system fonts)
- Cliched color schemes (purple gradients on white backgrounds)
- Predictable layouts and component patterns
- Cookie-cutter design that lacks context-specific character

Interpret creatively. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations.

Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code. Minimalist designs need restraint, precision, and careful attention to spacing, typography, and subtle details.

## Kevin's Design Context

Read `wiki/design/design-system.md` for current design tokens before starting any UI work.
See also: `wiki/design/aesthetic-systems.md` for art direction archetypes.
Before hand-rolling animated or uncommon components, read `wiki/design/component-library-sources.md` and route component-source decisions through `animated-component-libraries` (Magic UI, React Bits, Skiper UI, Cult UI).

## Related Skills

- `web-design-guidelines` — Vercel Web Interface Guidelines compliance
- `vercel-react-best-practices` — Performance optimization for React
- `frontend-design-taste` — Kevin's personal art direction skill
- `modern-web-design` — Design trends and implementation patterns
- `animated-component-libraries` — Pre-built animated/shadcn component source selection

<!-- folded-skills:auto:start -->
## Folded Skill References

These former standalone skills are bundled here as references to keep the runtime list compact. Load only the reference that matches the user's exact product, framework, or failure mode.

| Former skill | Reference | Description |
| --- | --- | --- |
| `claude-frontend-design` | [`references/skills/claude-frontend-design/SKILL.md`](references/skills/claude-frontend-design/SKILL.md) | Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics. |
<!-- folded-skills:auto:end -->

---

Timeline

• 2026-07-15 | Generated a browseable source page from the actual executable skill file. Source: skills/engineering/frontend-design/SKILL.md