Install Elite Taste
Connect your coding agent to Paul Elite’s design judgment. One command for Claude Code, or a per-project setup for Cursor, Codex and the rest — a few minutes either way.
An MCP server your agent calls
Elite Taste runs as a hosted MCP server. Your agent asks it for the design rules, layout and component guidance, and a static audit of the UI it writes.
The result is an interface with clearer hierarchy, spacing and surfaces — without replacing your components, framework or brand. Installing just connects your agent to the server; nothing runs on your machine but a small config file.
Pick how you install
Claude Code has a one-click plugin. Every other agent connects per project with an API key.
One command, no key to manage. You sign in once in the browser.
Best if Claude Code is your agent.Install the plugin →Create a key, then run one command inside each project.
Best for Cursor, Codex, or scripted setups.Set up per project →Claude Code
Three steps, and no API key anywhere — Claude signs you in through the browser.
Install the plugin
Run this in Claude Code:
/plugin install elite-taste --marketplace paul-elite/elite-taste-pluginOn Claude Code older than 2.1.275, add the marketplace first: /plugin marketplace add paul-elite/elite-taste-plugin, then /plugin install elite-taste@elite-taste.
Approve it in the browser
The first time Claude uses Elite Taste, a browser tab opens for you to log in and approve access. That’s the whole sign-in — there’s no key to copy or store. To sign in again later: /mcp → elite-taste → Authenticate. To disconnect: Settings → Connected agents.
Set it up for a project (optional)
The plugin works in every project out of the box. To tune it for one, run /elite-taste:setup there and choose influence, brand, density and motion.
Cursor, Codex and other agents
Create one key, then run the installer in each project you want it in.
Create an API key
In the dashboard, open API keys → Create. The key is shown once, so copy it straight into your shell profile or a secrets manager.
export ELITE_TASTE_API_KEY=et_live_…Keep it secretNever commit the key. The installer doesn’t write it to any file — configs point at the variable by name.
Run the installer
From the project root, run the command for your agent:
npx elite-taste init --agent claude # Claude Code
npx elite-taste init --agent cursor # Cursor
npx elite-taste init --agent codex # Codex
# options: --global --influence strict|balanced|flexibleConfirm it’s connected
Run the doctor to check the key and the server:
npx elite-taste doctor
✓ ELITE_TASTE_API_KEY is set
✓ https://elite-taste.vercel.app: plan pro, 12/3000 calls this monthThe files the installer adds
Small config files that point your agent at the server. No secrets land on disk — a key is always referenced by variable name.
.claude/skills/elite-taste/SKILL.md and .mcp.json — the HTTP server, with the header reading ${ELITE_TASTE_API_KEY}.cursor/rules/elite-taste.mdc and .cursor/mcp.json — header reads ${env:ELITE_TASTE_API_KEY}AGENTS.md block, plus a config.toml snippet printed for you to paste in.elite-taste.json — your project settings (influence, brand, density). No secrets.After it’s connected
Restart your agent so it loads the new server, then just ask.
Talk to it the way you already do — for example, “Apply Elite’s taste to this dashboard, keep our brand colours.” It audits the files, shows a refinement plan, applies what you approve, then re-audits and screenshots the result.