frontend-aesthetics
A design guidance skill that improves frontend aesthetics by avoiding generic 'AI slop' design patterns.
Install
mkdir -p .claude/skills/frontend-aesthetics && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2553" && unzip -o skill.zip -d .claude/skills/frontend-aesthetics && rm skill.zipInstalls to .claude/skills/frontend-aesthetics
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Prevents generic AI-generated designs by guiding typography, color, motion, and background choices. Use when creating frontend designs, landing pages, dashboards, or any UI/UX work. Helps avoid the "AI slop" aesthetic.Key capabilities
- →Apply distinctive typography pairings
- →Implement cohesive color and theme palettes
- →Orchestrate CSS-based motion and micro-interactions
- →Create layered background effects
- →Enforce Tailwind v4 spacing and configuration rules
How it works
The skill guides design choices by enforcing specific aesthetic principles that avoid common AI-generated patterns, focusing on high-contrast typography, cohesive themes, and intentional motion.
Inputs & outputs
When to use frontend-aesthetics
- →Design landing page typography
- →Develop high-contrast color palettes
- →Refine UI component styling
- →Plan motion interactions
About this skill
Frontend Aesthetics Skill
Based on Anthropic's formula for improving frontend design through steerability.
The Problem
LLMs converge toward generic, "on distribution" outputs. In frontend design, this creates what users call the "AI slop" aesthetic - Inter fonts, purple gradients on white backgrounds, and minimal animations.
Instructions
Make creative, distinctive frontends that surprise and delight. Focus on these four dimensions:
Typography
Choose fonts that are beautiful, unique, and interesting.
Never use: Inter, Roboto, Open Sans, Lato, Arial, default system fonts
Good choices:
- Code aesthetic: JetBrains Mono, Fira Code, Space Grotesk
- Editorial: Playfair Display, Crimson Pro, Newsreader
- Technical: IBM Plex family, Source Sans 3
- Distinctive: Bricolage Grotesque, Syne, Outfit, Plus Jakarta Sans
- Premium: Cabinet Grotesk, Satoshi, General Sans, Clash Display
Pairing principle: High contrast = interesting. Display + monospace, serif + geometric sans, variable font across weights.
Use extremes: 100/200 weight vs 800/900, not 400 vs 600. Size jumps of 3x+, not 1.5x.
Pick one distinctive font, use it decisively. Load from Google Fonts.
Color & Theme
Commit to a cohesive aesthetic. Use CSS variables for consistency.
Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
Draw inspiration from:
- IDE themes (Dracula, Nord, One Dark, Catppuccin, Tokyo Night)
- Cultural aesthetics (Japanese minimalism, Scandinavian design, Brutalism)
- Industry-specific palettes (Finance: navy/gold, Health: teal/white, Gaming: neon/dark)
Avoid: Purple gradients on white backgrounds (the ultimate AI slop indicator)
Motion
Use animations for effects and micro-interactions.
- Prioritize CSS-only solutions for HTML
- Use Motion library for React when available
- Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions
Backgrounds
Create atmosphere and depth rather than defaulting to solid colors.
- Layer CSS gradients (radial + linear combinations)
- Use geometric patterns or grids
- Add contextual effects that match the overall aesthetic
- Consider noise textures, grain, or subtle animations
Tailwind CSS v4 Compatibility
CRITICAL: Tailwind v4 has breaking changes. Follow these rules:
Spacing
- Never use:
space-x-*,space-y-*(removed in v4) - Always use:
gap-*with flex/grid containers instead
// WRONG (Tailwind v3 only)
<div className="flex space-x-4">
// CORRECT (Tailwind v4 compatible)
<div className="flex gap-4">
Config Loading
- Tailwind v4 doesn't auto-load
tailwind.config.ts - Add
@config "../tailwind.config.ts"to your CSS file if using a config
/* app/globals.css */
@import "tailwindcss";
@config "../tailwind.config.ts";
CSS Reset Conflicts
- Don't add custom
* { margin: 0 }resets - they breakmx-auto,my-*utilities - Let Tailwind's preflight handle resets
Package.json
- Add
"type": "module"to avoid Node.js ESM warnings
What to Avoid
- Overused font families (Inter, Roboto, Arial, system fonts)
- Clichéd color schemes (purple gradients on white)
- Predictable layouts and component patterns
- Cookie-cutter design that lacks context-specific character
- Space Grotesk (even this is becoming overused)
space-x-*andspace-y-*utilities (usegap-*instead)
Key Principle
Interpret creatively and make unexpected choices that feel genuinely designed for the context. Vary between light and dark themes, different fonts, different aesthetics.
You still tend to converge on common choices across generations. Avoid this: it is critical that you think outside the box!
Example: Theme Ideas
Instead of the default "tech purple":
- Obsidian Terminal: Deep black (#0a0a0a), electric green (#00ff9f), JetBrains Mono
- Editorial Luxury: Cream (#faf9f6), deep navy (#1a1a2e), Playfair Display + Source Sans
- Neon Brutalist: Pure white, bold black, hot pink accent (#ff006e), IBM Plex Mono
- Nordic Minimal: Cool gray (#e5e5e5), slate blue (#475569), Outfit
- Retro Computing: Amber on dark (#ffb000 on #1a1a1a), VT323 or IBM Plex Mono
When not to use it
- →When the project requires standard system fonts for accessibility
- →When the design must strictly adhere to a corporate style guide
Prerequisites
Limitations
- →Requires manual implementation of design principles
- →Tailwind v4 compatibility constraints limit legacy utility usage
How it compares
It actively discourages generic 'AI slop' by mandating non-standard font choices and specific design constraints that force more creative output.
Compared to similar skills
frontend-aesthetics side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| frontend-aesthetics (this skill) | 9 | 8mo | No flags | Intermediate |
| ui-styling | 12 | 9mo | Review | Beginner |
| tailwind-design-system | 34 | 2mo | No flags | Intermediate |
| figma | 22 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
ui-styling
mrgoonie
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
tailwind-design-system
wshobson
Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
figma
openai
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
design-system-patterns
wshobson
Build scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating design tokens, implementing theme switching, building component libraries, or establishing design system foundations.
interaction-design
wshobson
Design and implement microinteractions, motion design, transitions, and user feedback patterns. Use when adding polish to UI interactions, implementing loading states, or creating delightful user experiences.
web-design-reviewer
github
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.