Design taste for Claude Code.
Agave is a Claude Code skill that gives Claude the instincts of a senior product designer. Not a prompt template. Not a component library. A design philosophy it internalizes and applies to every piece of UI it writes.
SKILL.md (~300 lines) — The decision layer:
- 7 design principles: hierarchy, color intent, typography, spacing, restraint, consistency, personality
- A 7-question "Senior Designer Filter" Claude runs before outputting any component
- A pushback protocol — Claude flags bad design decisions and suggests alternatives
- An anti-pattern registry: component soup, template sameness, lazy gradients, over-decoration, and more
- Guidance on atmospheric gradients, mixed-size metrics, dark inversion, split-color headlines
- Responsive awareness, motion principles, states checklist
component-taste.md (~190 lines) — The reference companion:
- What "good" vs "bad" looks like for 10 common components
- Cards, modals, tables, forms, navigation, buttons, empty states, badges, toasts, dashboards
- Framework-agnostic — principles only, no code examples
Without Agave, Claude gives you a card with a blue top-border, 1px solid borders, and a generic gradient hero.
With Agave: soft layered shadows, generous radius, color accents inside the card, proper spacing hierarchy, atmospheric gradient blooms, mixed-size metric numbers, and contrast ratios that actually pass accessibility.
- Create the skill folder:
mkdir -p ~/.claude/skills/agave- Copy both files:
cp SKILL.md ~/.claude/skills/agave/
cp component-taste.md ~/.claude/skills/agave/- That's it. Claude Code auto-loads the skill whenever you're working on UI.
Claude Code has a Skills feature. Place a SKILL.md file in ~/.claude/skills/<name>/ and Claude automatically loads it when the task is relevant. No need to re-explain your design preferences every conversation.
Think of it like onboarding a designer — except you do it once and it sticks forever.
Agave is opinionated. It believes:
- Subtle shadows over borders. Borders feel dated. Layered shadows feel modern.
- Color accents inside cards, not on top-borders. A colored top-border on a rounded card looks dated.
- Gradients are a tool, not decoration. Atmospheric blooms and surface gradients are beautiful. Gradient buttons and gradient text are not.
- Minimal with pops. Mostly quiet UI with strategic moments of color or richness.
- Cards should be earned. Not everything needs a container. A hero metric can float free.
- One accent color, used with discipline. More restraint = more impact.
Agave works with any stack — Tailwind, vanilla CSS, shadcn, Material UI, whatever. It teaches principles, not patterns. The same skill improves React dashboards, marketing landing pages, and WordPress themes equally.
Open an issue or PR if you have design opinions worth encoding. The bar is high — every line should make Claude's output measurably better.
MIT