taste-skill
Skill4 starsChanged 21 days agoMITView on GitHub
Strict layout and taste rules for public pages and app screens (tasteskill v2, rules only). Use when building, redesigning or reviewing how a page looks, or when it looks generic, templated or "AI-made". Covers headlines, margins, voids, eyebrows, numbering, rules/lines, gradients, shadows, palettes, card rows, type scale, spacing, colour and components.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- wolverin0/claude-skillstheir own version, first seen Nov 15, 2026
- ychampion/ystacktheir own version, first seen Nov 15, 2026
- Markssuave/Markssuave-Agent-skillstheir own version, first seen Nov 8, 2026
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
- nadavnaveh/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use animation-vocabulary, emil-design-eng and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
boraoztuncSkillanimation-vocabulary
Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.
Also in 3 projects that use this
VercelSkillemil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Also in 4 projects that use this
tekgnosis-netSkillapple-design
Comprehensive Apple Design System for building stylish, premium UIs with Apple's design language. Covers design tokens, typography, color, layout patterns, components, animations, responsive design, iconography, and dark mode — for both web (HTML/CSS/JS) and SwiftUI. Use this skill whenever the user wants an Apple-style UI, a clean minimal design, a product landing page, a design system, premium pricing cards, app-like web experiences, or mentions wanting something that looks like apple.com, iOS, or macOS. Also trigger when users say things like "make it look premium", "clean modern design", "minimal elegant UI", "sleek interface", or reference Apple's design language — even if they don't explicitly say "Apple style". Trigger for ANY design task where quality and polish matter.
Also in 3 projects that use this
GoogleSkillprototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Also in 5 projects that use this
MicrosoftSkillimpeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.
Also in 3 projects that use this
GoogleSkillgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Also in 4 projects that use this
- +4 more from google
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- huytieu/COG-second-brain★ 1.3ksame name
- wolverin0/claude-skills★ 41same name
- podo/design-agent-skills★ 32same name
- wrg32786/aigent-os★ 26same name
- PIXARTSeu/Synapse★ 9same name
- welshDog/HyperCode-V2.4★ 5same name
- alunadev/ald-skills★ 4same name
- Roentek/Claude_Code_Boilerplate_Framework★ 4same name
- ychampion/ystack★ 4same name
- nadavnaveh/skills★ 3same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- eli5Skill
- frontend-designSkill
- ui-ux-pro-maxSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Not installed: the Node scripts (draw/lint/inspect/assets/scenes.mjs), the asset library, and the references type.md (Google Fonts links), …
- Very specific: line 21
Project rules win over this skill: no Google Fonts, CDNs or other third-party requests (fonts are self-hosted, see D-006).
- Distinctive: line 104
No image is better than a placeholder, an icon, or an abstract shape.
- Distinctive: line 107
Every found picture is downloaded into the project, credited on the page and listed in the report.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Adapted from Leonxlnx/taste-skill (MIT, commit 12af471), skills/taste-skill. Change: rules only.
Kept verbatim: the "House rules" and "Laws of the craft" sections of SKILL.md, and the
references layout.md, tells.md, critique.md, copy.md and colour.md.
Not installed: the Node scripts (draw/lint/inspect/assets/scenes.mjs), the asset library, and the
references type.md (Google Fonts links), scenes.md (CDN scripts), imagery.md (network downloads,
picsum hotlinks), motion.md (dim text below 4.5:1) and app-screens.md (script-driven). -->taste-skill (rules only)
The upstream skill runs a ten-step pipeline driven by its own scripts. This install keeps only the
rules. Wherever a rule or reference mentions inspect.mjs, lint.mjs, draw.mjs, assets.mjs,
scenes.mjs, a "dealt" direction sheet or a library file, those are not installed: check the
rule yourself (screenshots at 1280px and 390px, see .claude/agents/coder.md) and pick the
direction from the story and docs/DESIGN_DECISIONS.md instead.
Project rules win over this skill: no Google Fonts, CDNs or other third-party requests (fonts are
self-hosted, see D-006); text contrast at least 4.5:1; respect reduced motion; the one look in
docs/DESIGN_DECISIONS.md. Never fetch or download anything for a page without the owner's approval.
References (read when you need the detail): references/layout.md (composition, margins, voids),
references/tells.md (the registry of generated-page tells), references/critique.md (how to review a
page), references/copy.md (writing the words), references/colour.md (palette and contrast).
House rules
These hold on every build, whatever the direction. inspect.mjs measures them.
| Rule | Instead |
Headlines: two lines or fewer, at every width. Every h1–h6, and the main line of the first screen whatever its tag. | Cut words. Then widen the measure. Size last. |
A clear title on the first screen, in the page's one h1, and a heading on every section. | Say what this is: the name with what it does, the product with what it is for, the event with its date and place. |
| Equal outer margins; no section huddled on one side with the other half of the screen empty. | Close every void with something on its far side: the section's picture, a second column, a list, a figure. |
| No blank stretches taller than about half a screen. | The normal section gap. A deliberate rest is a placed picture or a field of colour, once per page. |
Statements are paragraphs. An intro sentence or a quotation set large is marked up as <p> or <blockquote>, stays at statement size (36px or less on desktop, 24px on a phone) and runs to about 25 words, three lines. | Larger than that it is a headline and the two-line rule applies. In blind tests jurors read a 42px sentence over four lines as a four-line headline. |
| No eyebrows. No small label above a heading, no pill badge above the headline, no "New ·" chip. | Put the information in the heading or the first sentence, or drop it. |
| No monospace outside real code blocks. | The text face. Tabular figures where numbers align. |
| No index numbering. No 01 / 02 / 03, no (001), no "Step 2". | Order shown by position, size, or the words. A real <ol> if order matters. |
| No thin rules. No hairline dividers, no 1px outlined boxes, no grid lines, crosshairs or crop marks. | Space. A step in background tone. A change of scale. A filled shape. |
| No gradients. Not as backgrounds, not on buttons, not in text. | Flat colour, or a real photograph. A neutral scrim under text on a photo is the one exception. |
| No shadows on things at rest. No glows. | A tone step between surfaces. Shadows only on what truly floats: a menu, a dialog. |
| No assistant palette. No yellow-cream ground with terracotta or rust; no violet or indigo. | The dealt palette. |
| No tiny uppercase letter-spaced labels. | Sentence case at a readable size. |
| No icon-topped feature cards, no rows of identical cards. | The dealt section blueprint. |
| No glass. No backdrop blur panels, no floating pill navigation. | A plain bar: wordmark, a few links, one action. |
| No emoji, no gradient blobs, no decorative shapes, no fake dashboards of grey bars. | A real picture, a real interface fragment, or nothing. |
| No styled accent word in a headline (italic, serif, coloured, underlined). | One face, one colour. The words carry the emphasis. |
| Two typefaces at most, usually one. | The dealt type system. |
Three places keep their own conventions and are left alone by the inspector: real code in
<pre>/<code> (monospace is correct there), real tables and form fields (they may have lines), and
a real interface fragment whose root carries the attribute data-ui (the product's own borders and
menus; see references/imagery.md §7).
Why these, honestly. Some are what the study measured: among the 247 sites, those the panel scored
7.5 or higher used icon feature cards 1% of the time against 28% for sites under 6.5, pill badges 14%
against 34%, gradients 22% against 52%, shadows 24% against 48%, tiny tracked caps 16% against 57%.
Others are the owner's taste and go against current gallery fashion: monospace labels, index numbers
and hairline grids are actually more common on award sites than on weak ones, which is exactly why
generators imitate them and why they now read as costume. They are banned here without exception.
references/tells.md keeps the dated registry.
Removing ornament leaves space. Never fill it with another ornament. Fill it with scale (make the main thing larger), with the full content, with a picture made for this subject, or with a field of flat colour. Leave it empty on purpose once per page at most.
Laws of the craft
Short form. Numbers are from the study unless marked as house style.
Type
- Two or three sizes do the visible work: one very large, one small, nothing in between. Median headline-to-body ratio on the studied sites is 4.3; the best go far beyond (largest type: median 8.4vw on the top sites against 5.0vw on the weak ones).
- Display type: tracking -0.02 to -0.05em, leading 0.85–1.05. Text: 16–20px, leading 1.45–1.6, 45–75 characters per line.
- Five sizes on a page is the ceiling. One family is normal (a third of the studied sites); two is the limit.
- Left-aligned by default. Centre at most one moment.
Space
- One grid, one pair of tight margins (16–32px), used everywhere; large things run to the edges. Text blocks share two or three left edges on the whole page.
- Asymmetry inside the grid, never in the frame: the two outer margins are equal, and an off-centre heading is answered by something at the far side of the grid.
- The gap between sections is clearly larger than any gap inside one: 120–240px on desktop (the study's median is about 240).
- Each section has a different composition from its neighbours; none is a card grid.
Colour
- One ground, one ink, one accent. The accent appears on the action and perhaps one other thing.
- Running text in the full ink. A page set in soft grey reads unfinished.
- Surfaces are separated by a small step in tone, never by a line or a shadow.
- A section may change the whole field colour. Nothing fades into anything.
Imagery
- One dominant image beats six small ones. On the top-scored sites the hero media covers at least half the first screen 68% of the time.
- Same crop ratios, same treatment, square corners unless the direction says otherwise (73% of the studied sites leave media square).
- No image is better than a placeholder, an icon, or an abstract shape. A picture drawn for this subject, in its colours and with care, is better than either. A real picture of its world, found and credited, is better still.
- Every found picture is downloaded into the project, credited on the page and listed in the report. None is presented as the client's own.
- Nothing ever lies on top of a headline or a statement (the inspector fails it).
Components
- Buttons: flat, one fill colour, either square-cornered or fully round, decided once (top sites: 52% square, 23% pill; the 9–16px "soft" radius is the weak-site default). Most strong heroes have no button at all, or one.
- Navigation: wordmark, three to five plain links, one action. No bar chrome.
- A control explains how to use it by its form, its label and its place. When it seems to need a
sentence on how to operate it, redesign the control instead of adding the sentence. What a field
accepts is different. First remove the limit where you can: a date picker, or a parser that takes
any common format. A limit that remains, such as password rules or file type and size, stays visible
beside the field and is tied to it with
aria-describedby. - The footer is a designed close, not a sitemap: on most strong sites the name returns at full width.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

