Taste Skill: art direction for the pages your agent builds
A developer redesigned a project site with it and posted 0 FAIL at 1440, 768 and 390 in the pull request
- Who
- An open-source skill by Leon Lin (Leonxlnx), for people who build websites, landing pages and dashboards with a coding agent.
- When
- First published in February 2026, rebuilt as v2 in October; the latest release is v2.1.5 (2026-10-24).
- Where
- Installs as a Claude Code or Codex plugin or with npx skills. Runs on your own machine with Node 22+ and Chrome, Edge or Chromium.
What was hard
Ask an agent for a landing page and you get the same screen every time: a centred headline, a little label above it, a row of icon cards, a soft gradient. Nothing in it is wrong, but nothing says whose page it is, so you end up asking for fixes one by one.
What it does about it
Taste Skill doesn't leave the look to the model's defaults. A script deals three directions, the agent picks one, and the page grows from one sentence tying the client's own material to that direction. Pictures come from open archives with their credits, and once it is built the agent measures the page in a real browser at three widths and fixes what it sees in the screenshots.




What people made with it
Redesigned the GitHub Pages site of their MCP project with a Cursor agent and this skill: card rows became composed sections, and four open-collection images went in with credits.
Inspect: 0 FAIL across 1440/768/390; screenshots are attached above.
Ran the skill's redesign audit on index.html with Claude Code and applied only the low-risk fixes: a focus ring, a skip link, button feedback and hero copy readable on phones.
After: Nav links glide (through Lenis) and stop right below the header

Recommends putting the new v2 into Claude Code or Codex and having it give a vibe-coded site a checkup at desktop, tablet and phone widths.
It opens your pages at desktop, tablet and phone widths
How it runs inside
- 1
Claude Code · Codex → design-taste-frontend
Reads the brief and SKILL.mdIt reads the brief and first lists what only this client has.skills/taste-skill/SKILL.md - 2
Claude Code · Codex → draw.mjs
draw.mjs --options 3Deals three of twenty researched directions at random; the agent picks the one that carries the subject's idea.skills/taste-skill/scripts/draw.mjs - 3
draw.mjs → Claude Code · Codex
--direction <id> → direction.jsonDeals the chosen direction's type, palette, hero and sections from the library into .taste-skill/direction.json.skills/taste-skill/library/directions.json - 4
Claude Code · Codex → assets.mjs
assets.mjs "<query>"Searches open collections such as Openverse, Wikimedia Commons and the Met, and keeps each picture's credit.skills/taste-skill/scripts/assets.mjs - 5
Claude Code · Codex → inspect.mjs
inspect.mjs <page>Opens the page in a real browser at 1440, 768 and 390, measures it and saves screenshots. Any FAIL means not done.skills/taste-skill/scripts/inspect.mjs - 6
Claude Code · Codex → The page and its screenshots
Looks, fixes the top threeReads its own screenshots, scores them against a juror's rubric and fixes the top three problems, up to three rounds.skills/taste-skill/references/critique.md
What goes in, what comes out
Is it for you
Good for
- Building a one-pager for a shop, an event or a portfolio with an agent
- Giving a vibe-coded site a checkup at desktop, tablet and phone widths
- Tidying dashboards, admin views and settings screens
- React, Vue, Svelte or plain HTML alike
Not for
- A build takes roughly 30 to 45 minutes and a few hundred thousand tokens (per the README).
- The pictures come from open archives, not from your business; the README suggests swapping in your own when you have them.
- Finding pictures needs network access.
- Without Node 22 or Chrome the inspector cannot run, and screenshots from another browser tool stand in (SKILL.md).
Reviewed by Devalley’s editor before publishing. How the column is made