Elite Taste
Paul Elite's design taste, for Claude Code, Cursor and Codex

Your components.
My taste.

An installable skill that brings a designer's judgment into the UI your agent writes: hierarchy, spacing, surfaces and composition. It refines what you already have. It doesn't replace your component library.

/plugin install elite-taste --marketplace paul-elite/elite-taste-plugin
68 → 100
audit score, same dashboard
0
components replaced
9
MCP tools
33
rules, all confirmed
Same dashboard, refined in place

It ships the taste, not the boxes.

Your agent keeps the components and the brand. The engine resolves hierarchy, spacing and surfaces — and the audit score climbs from 68 to 100.

Audit 68 → 100
app/dashboard/page.tsx — Elite Taste

Overview

October · compared with September

Revenue$48,290+12.5% vs Sep
Customers2,341+4.1% vs Sep
Churn1.9%−0.3 pts vs Sep
MRR$12,840+8.2% vs Sep

Revenue

Last 12 months

Revenue by plan

Enterprise$21.4k
Team$15.9k
Starter$10.9k

Recent customers

Northwind LabsEnterprise$4,200
Tidewater PressTeam$1,150
Saltbox BakeryStarter$290
Works in the agents you already use
  • Claude Code
  • Cursor
  • Codex
  • Windsurf
  • Zed

Same dashboard. Same Tailwind. Same brand colour.

The left is what an agent generates by default. The right follows the engine's refinement plan. Scores are the engine's real audit of each file.

Sample data

Overview

October · compared with September

Revenue$48,290+12.5% vs Sep
Customers2,341+4.1% vs Sep
Churn1.9%−0.3 pts vs Sep
MRR$12,840+8.2% vs Sep

Revenue

Last 12 months

Revenue by plan

Enterprise$21.4k
Team$15.9k
Starter$10.9k

Recent customers

Northwind LabsEnterprise$4,200
Tidewater PressTeam$1,150
Saltbox BakeryStarter$290
1

Install

One command adds the plugin. The first time Claude uses it, you sign in from the browser.

/plugin install elite-taste
2

Ask

Talk to your agent the way you already do.

“Apply Elite’s taste to this dashboard, keep our purple.”
3

Review

The agent audits, shows a plan, applies what you approve, then re-audits and screenshots.

tokens → components → screens

What changes

  • Visual hierarchy: size, colour and space before weight and boxes
  • Spacing, rhythm and alignment
  • Surfaces: what deserves a card, a shadow, a border
  • Composition of screens and empty states
  • Contrast, focus and target sizes

What stays yours

  • Your component library and framework
  • Your brand colours, logo and typefaces
  • Behaviour, data, routes and props
  • Accessibility attributes and focus order
  • Anything you exclude in .elite-taste.json

The taste, written down

Version 0.8.0: rules drawn from Paul Elite's shipped work (his written rules, commits and code) and confirmed by him. Questions he hasn't answered yet are never applied, and any rule that's only inferred is labelled unconfirmed.

Read the full spec and how it's maintained

Start free. Upgrade when you want audits and refinement plans.