Install a taste.

Overview

Choose your agent.

• Claude Code~/.claude/skills · .claude/skills2 min
• >_Codex~/.agents/skills · .agents/skills2 min
• Cursor~/.cursor/skills · .cursor/skills2 min
• >_Any other agentA folder in your repo plus one line in AGENTS.md2 min

The fastest way: paste a prompt

1. 01

   Open a taste you can use

   Any free taste, or anything on Pro. On its page, signed in, you’ll find Paste into your agent with a tab for each agent.

2. 02

   Copy, paste, send

   The prompt carries a private download link (yours alone, good for seven days), the folder to unzip into, and the instruction to read SKILL.md and apply the taste from then on. Your agent does the rest and reports the skill’s non-negotiables back to you.

3. 03

   Ask for a screen

   You don’t need to describe a style. The skill’s description tells your agent when to use it, and its files cover type, color, spacing, components and motion. The quickstart walks through a first build.

Where skills live

Prefer the zip? Every taste you can download also has a Download zip button; the per-agent guides show the unzip commands for macOS, Linux and Windows.

Quickstart

Your first tasteful app.

About ten minutes: install, one prompt, then steer — without breaking the taste.

1. 01

   Install for your agent

   The quick way: on any taste you can use, copy the Paste into your agent prompt and send it. Or follow the guide for Claude Code, Codex, Cursor or another agent. Use a new project for this first run, with nothing in it but what the install guide put there.

2. 02

   Ask for a product, not a style

   Paste this as-is. It never mentions fonts, colors or mood — that’s the skill’s job — and it’s the exact brief every skill is validated with.

   Starter prompt · webCopy command

   Build a small static site for Ledgerline, a fictional bookkeeping analytics product for freelancers: index.html (landing page) and dashboard.html (app screen), sharing one stylesheet styles.css. No frameworks, no build step, vanilla HTML/CSS (a few lines of JS allowed for menu/toggles).
   
   Landing page: top navigation, hero with headline + subline + primary and secondary CTA, a logos/social-proof strip, three feature sections, pricing (three tiers, one highlighted), a closing CTA, and a footer with columns.
   Dashboard: app shell with side or top navigation, page header, four stat cards (revenue, expenses, profit, overdue invoices), a revenue-over-time chart (inline SVG is fine), a recent-invoices table (≥ 8 rows: client, date, amount, status), and an activity feed.
   Both pages must work at mobile and desktop widths. Use realistic copy and numbers, not lorem ipsum. Make it polished and production-quality.

3. 03

   Check what good looks like

   Compare your pages with the skill’s validated screenshots: they ship in the zip under taste-editorial/references/ — web-*.png for web pages (web-*-mobile.png at phone width) — and on the skill page when you’re signed in. The skill’s SKILL.md lists its non-negotiables — fonts, palette, corners, shadows — and those should all hold. Your pages won’t match the screenshots: a taste is a point of view, not a template.

4. 04

   Steer inside the taste

   • Ask in the skill’s own terms: “make the invoices table denser”, “add a night edition”, “a pricing section in the same voice”.
   • Name your stack once — the skill ships plain CSS variables, Tailwind v4 and v3 configs, and JSON tokens.
   • Avoid style words from elsewhere (“make it pop”, “glassy”, “like Stripe”): they pull your agent back to its defaults.
   • One taste per project. Two installed taste skills argue with each other.

Claude Code

Claude Code.

Two ways in: paste one prompt and let the agent install, or unzip the folder yourself. Shown for Editorial — use your skill’s file name.

Option 1 · paste a prompt (recommended)

1. 01

   Copy the prompt from the taste page

   Signed in, open any taste you can use and choose the Claude Code tab under Paste into your agent. Copy it.

2. 02

   Paste it into your agent and send

   Claude Code downloads the package through a private link, unzips it into ~/.claude/skills, reads SKILL.md and confirms the taste’s non-negotiables. Skills load live. If the skills folder didn’t exist when your session started, run /reload-skills (or start a new session).

Option 2 · unzip it yourself

1. 01

   Download

   In your library, choose Download zip next to the skill. It unpacks to one folder, taste-editorial. If your browser renamed the file (say, with “(1)”), use its actual name in the commands below.

2. 02

   Install

   For every project on this machine — into ~/.claude/skills:

   macOS / LinuxCopy command

   $ mkdir -p ~/.claude/skills && unzip -o ~/Downloads/taste-editorial-1.0.0.zip -d ~/.claude/skills

   Windows · PowerShellCopy command

   PS> Expand-Archive -Force $HOME\Downloads\taste-editorial-1.0.0.zip $HOME\.claude\skills

   Or for one repository — from its root, into .claude/skills. Commit it to share the taste with your team in a private repository; in a public one, add .claude/skills/ to .gitignore — the license doesn’t allow publishing the package.

   macOS / Linux · repository rootCopy command

   $ mkdir -p .claude/skills && unzip -o ~/Downloads/taste-editorial-1.0.0.zip -d .claude/skills

   Windows · PowerShell · repository rootCopy command

   PS> Expand-Archive -Force $HOME\Downloads\taste-editorial-1.0.0.zip .claude\skills

3. 03

   Check it’s there

   From a terminal — each prints the path if the skill is in place:

   Machine-wide installCopy command

   $ ls ~/.claude/skills/taste-editorial/SKILL.md

   Repository install · from its rootCopy command

   $ ls .claude/skills/taste-editorial/SKILL.md

   Type / in Claude Code and look for taste-editorial in the list. Skills load live. If the skills folder didn’t exist when your session started, run /reload-skills (or start a new session).

4. 04

   Build

   Ask for a screen — no need to name the skill or describe a style. For a first run, paste the quickstart prompt as-is. Type /taste-editorial, or just ask for a screen — Claude loads the skill when the request matches its description.

   If the output looks generic, see troubleshooting.

Verified against Claude Code’s skills documentation, October 2026.

Codex

Codex.

Two ways in: paste one prompt and let the agent install, or unzip the folder yourself. Shown for Editorial — use your skill’s file name.

Option 1 · paste a prompt (recommended)

1. 01

   Copy the prompt from the taste page

   Signed in, open any taste you can use and choose the Codex tab under Paste into your agent. Copy it.

2. 02

   Paste it into your agent and send

   Codex downloads the package through a private link, unzips it into ~/.agents/skills, reads SKILL.md and confirms the taste’s non-negotiables. Codex detects new skills automatically. If it doesn’t appear, restart Codex.

Option 2 · unzip it yourself

1. 01

   Download

   In your library, choose Download zip next to the skill. It unpacks to one folder, taste-editorial. If your browser renamed the file (say, with “(1)”), use its actual name in the commands below.

2. 02

   Install

   Codex works inside a Git repository — in a new folder, run git init first.

   For every project on this machine — into ~/.agents/skills:

   macOS / LinuxCopy command

   $ mkdir -p ~/.agents/skills && unzip -o ~/Downloads/taste-editorial-1.0.0.zip -d ~/.agents/skills

   Windows · PowerShellCopy command

   PS> Expand-Archive -Force $HOME\Downloads\taste-editorial-1.0.0.zip $HOME\.agents\skills

   Or for one repository — from its root, into .agents/skills. Commit it to share the taste with your team in a private repository; in a public one, add .agents/skills/ to .gitignore — the license doesn’t allow publishing the package.

   macOS / Linux · repository rootCopy command

   $ mkdir -p .agents/skills && unzip -o ~/Downloads/taste-editorial-1.0.0.zip -d .agents/skills

   Windows · PowerShell · repository rootCopy command

   PS> Expand-Archive -Force $HOME\Downloads\taste-editorial-1.0.0.zip .agents\skills

3. 03

   Check it’s there

   From a terminal — each prints the path if the skill is in place:

   Machine-wide installCopy command

   $ ls ~/.agents/skills/taste-editorial/SKILL.md

   Repository install · from its rootCopy command

   $ ls .agents/skills/taste-editorial/SKILL.md

   Run /skills in Codex and look for taste-editorial. Codex detects new skills automatically. If it doesn’t appear, restart Codex.

4. 04

   Build

   Ask for a screen — no need to name the skill or describe a style. For a first run, paste the quickstart prompt as-is. Mention $taste-editorial in your prompt, or just ask for a screen — Codex picks the skill from its description.

   If the output looks generic, see troubleshooting.

Verified against Codex’s skills documentation, October 2026.

Cursor

Cursor.

Two ways in: paste one prompt and let the agent install, or unzip the folder yourself. Shown for Editorial — use your skill’s file name.

Option 1 · paste a prompt (recommended)

1. 01

   Copy the prompt from the taste page

   Signed in, open any taste you can use and choose the Cursor tab under Paste into your agent. Copy it.

2. 02

   Paste it into your agent and send

   Cursor downloads the package through a private link, unzips it into ~/.cursor/skills, reads SKILL.md and confirms the taste’s non-negotiables. Cursor discovers skills when it starts — restart Cursor after installing. (It also reads .agents/skills, .claude/skills and .codex/skills.)

Option 2 · unzip it yourself

1. 01

   Download

   In your library, choose Download zip next to the skill. It unpacks to one folder, taste-editorial. If your browser renamed the file (say, with “(1)”), use its actual name in the commands below.

2. 02

   Install

   For every project on this machine — into ~/.cursor/skills:

   macOS / LinuxCopy command

   $ mkdir -p ~/.cursor/skills && unzip -o ~/Downloads/taste-editorial-1.0.0.zip -d ~/.cursor/skills

   Windows · PowerShellCopy command

   PS> Expand-Archive -Force $HOME\Downloads\taste-editorial-1.0.0.zip $HOME\.cursor\skills

   Or for one repository — from its root, into .cursor/skills. Commit it to share the taste with your team in a private repository; in a public one, add .cursor/skills/ to .gitignore — the license doesn’t allow publishing the package.

   macOS / Linux · repository rootCopy command

   $ mkdir -p .cursor/skills && unzip -o ~/Downloads/taste-editorial-1.0.0.zip -d .cursor/skills

   Windows · PowerShell · repository rootCopy command

   PS> Expand-Archive -Force $HOME\Downloads\taste-editorial-1.0.0.zip .cursor\skills

3. 03

   Check it’s there

   From a terminal — each prints the path if the skill is in place:

   Machine-wide installCopy command

   $ ls ~/.cursor/skills/taste-editorial/SKILL.md

   Repository install · from its rootCopy command

   $ ls .cursor/skills/taste-editorial/SKILL.md

   Type / in Agent chat and search for taste-editorial. Cursor discovers skills when it starts — restart Cursor after installing. (It also reads .agents/skills, .claude/skills and .codex/skills.)

4. 04

   Build

   Ask for a screen — no need to name the skill or describe a style. For a first run, paste the quickstart prompt as-is. Type /taste-editorial in Agent chat, or just ask for a screen — the agent chooses the skill when it’s relevant.

   If the output looks generic, see troubleshooting.

Verified against Cursor’s skills documentation, October 2026.

Other agents

Other agents.

Any agent that reads AGENTS.md — or a rules file — can use a taste. Pick one of the two routes below, not both.

1. 01

   Route A — the skills folder

   Many agents load Agent Skills on their own from .agents/skills in your repository. From the repository root:

   macOS / LinuxCopy command

   $ mkdir -p .agents/skills && unzip -o ~/Downloads/taste-editorial-1.0.0.zip -d .agents/skills

   Windows · PowerShellCopy command

   PS> Expand-Archive -Force $HOME\Downloads\taste-editorial-1.0.0.zip .agents\skills

   Ask for a screen. If the taste shows up, you’re done — skip route B.

2. 02

   Route B — a folder plus AGENTS.md

   If your agent ignored route A, remove .agents/skills/taste-editorial and unzip into design/ instead:

   macOS / LinuxCopy command

   $ mkdir -p design && unzip -o ~/Downloads/taste-editorial-1.0.0.zip -d design

   Windows · PowerShellCopy command

   PS> Expand-Archive -Force $HOME\Downloads\taste-editorial-1.0.0.zip design

   Then add this line to AGENTS.md at the repository root (or your agent’s rules file — GEMINI.md, a Cursor rule, a Copilot instructions file):

   AGENTS.mdCopy command

   Before building or styling any UI, read design/taste-editorial/SKILL.md and follow it — it overrides framework and component-library defaults. Load the files it points to when it says to.

3. 03

   Check it’s there

   Route ACopy command

   $ ls .agents/skills/taste-editorial/SKILL.md

   Route BCopy command

   $ ls design/taste-editorial/SKILL.md

   Committing the folder is fine in a private repository. In a public one, add it to .gitignore — the license doesn’t allow publishing the package.

4. 04

   Build

   Ask for a screen. If the first answer looks generic, say “use the design skill in design/” once — the pointer does the rest.

Troubleshooting

When it looks generic.

The failures we saw while testing skills on real agents, and what fixes each.

The output ignores the taste

• Check the path: SKILL.md must sit one folder deep — ~/.claude/skills/taste-editorial/SKILL.md, or .claude/skills/taste-editorial/SKILL.md inside a repository. Unzipping into a folder already named after the skill leaves it two deep.
• A brand-new skills folder isn’t always watched yet: in Claude Code run /reload-skills; in Codex or Cursor, restart the app.
• Name the skill once in your prompt (see your agent’s guide), then carry on as usual.
• Agents ship built-in skills of their own (Codex, for one, has a site-building skill). If your output mixes looks, name the taste skill explicitly so it leads.

Some screens follow it, some don’t

• Long sessions drift. Name the skill again for the new screen, or ask the agent to re-read the skill’s components and layouts files.
• Remove other design skills or style rules from the project — they compete.

It fights my framework or component library

• Tell the agent your stack. Every skill ships tokens/ as CSS variables, Tailwind v4 @theme, a Tailwind v3 config and JSON.
• With a component library (shadcn/ui, MUI…), ask the agent to restyle its components with the skill’s tokens. The skill wins over library defaults.

The fonts look wrong

• Skills use open-licensed fonts loaded from their source — no font files ship in the package. Offline, or to self-host them, download them from the sources listed in the skill’s LICENSE.md. The fallback stacks keep the look close meanwhile.

Can’t sign in

• A sign-in link works once and expires after 15 minutes — request a new one. Check spam for “Your Taste Stack sign-in link”. Google and GitHub sign in to the same account when they use the same email.

Downloads

• Download from your library while signed in; you always get the latest version. Re-download any time.

Still stuck? hello@tastestack.dev — include your agent and what you asked it.

FAQ

Questions.

Licensing, updates, Pro — and what a taste can and can’t do.