Skill · Coding

frontend-taste

Builds pages and components that don't look AI-generated: picks a design direction first, uses real copy, sets hierarchy, covers empty, loading and error states, and avoids common tells like purple gradients and emoji icons. Use when asked to build or restyle a page, landing page, dashboard or component, make a UI look better or less generic, or 'make it look designed'.

The skill itself. Agents read the name and description first and load the rest only when a task matches.

frontend-taste/SKILL.md
---
name: frontend-taste
description: "Builds pages and components that don't look AI-generated: picks a design direction first, uses real copy, sets hierarchy, covers empty, loading and error states, and avoids common tells like purple gradients and emoji icons. Use when asked to build or restyle a page, landing page, dashboard or component, make a UI look better or less generic, or 'make it look designed'."
---

# Frontend taste

Build pages and components that look designed by a person with a point of view, not generated.

## Steps

1. Before writing code, pick a direction and write it down in five lines: two or three reference sites or products the UI should feel like, a type scale (font, sizes, weights), a palette (one neutral ramp, one accent, semantic colors for success, warning and error), a spacing scale (for example 4, 8, 12, 16, 24, 32, 48) and a corner radius. If the repo already has a design system, tokens or a Tailwind theme, use those instead and say so.
2. Write real copy and realistic data for the user's own product: its actual features, plausible numbers, long and short names, a value that wraps. Ask for the product details if you don't have them. No placeholder Latin filler text, and no invented testimonials, customer logos or usage stats presented as real; mark any placeholder clearly.
3. Set hierarchy first: one clear primary action per screen, one heading level per section, secondary info in muted text. Test it: name the first thing the eye lands on. If it isn't the most important thing, fix size, weight or contrast before adding anything.
4. Choose density on purpose. Dashboards and tools can be dense; marketing pages need room. Align to a grid and take every spacing value from the scale.
5. Build every state: empty, loading (a skeleton that matches the layout), error with a way to recover, and very long content.
6. Check responsive layouts at 360px, 768px and 1280px, and check accessibility basics: contrast of at least 4.5:1 for body text and 3:1 for large text and UI controls, visible focus rings, labels on inputs, alt text, a sensible keyboard order.
7. Self-review against the tells below. If you can take screenshots (a browser tool or Playwright), take them at each width and look at them before saying done. If you can't, say the visual check is still needed.

## Avoid these tells

- Purple-to-blue gradients, glowing blobs, glassmorphism by default.
- Emoji as icons; mixed icon sets.
- Everything centered; a hero with a headline, a subline, two buttons and nothing else.
- Identical cards in a three-column grid, each with an icon, a title and two lines.
- Every element with a shadow, large rounded corners and a border at once.
- Vague copy: big promises and buzzwords ("Unlock your potential", "Revolutionize") instead of what the product does.

## Rules

- No colors, font sizes or spacing values outside the chosen scale.
- Don't add decoration to hide weak hierarchy.
- Use the codebase's existing components and styles before inventing new ones.

## Example output

A short design-decisions note (direction, references, type scale, palette, which tells you avoided and why), then the code.