The ui ux pro max skill, Impeccable and Taste Skill solve different problems, so the choice usually makes itself. If your agent should look design answers up before it builds, including rules for 22 stacks such as SwiftUI, Flutter and WPF, take UI UX Pro Max. If the interface already exists and you want named commands to critique and polish it, take the Impeccable skill. If you are building a company website from scratch, take Taste Skill. That split is most of the answer to impeccable vs ui ux pro max: one searches before building, the other reviews what is built.
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ui-ux-pro-maxnextlevelbuilder/ui-ux-pro-max-skill | Plugin | 146k | yesterday | MIT | A | — | Claude Code |
| impeccablepbakaus/impeccable | Skill | 104k | today | Apache-2.0 | A | 131 | Claude Code |
| design-taste-frontendLeonxlnx/taste-skill | Skill | 111k | yesterday | MIT | A | 184 | Claude Code, Codex |
Install
/plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill/plugin install ui-ux-pro-maxnpx agentmods add skills/pbakaus/impeccable/impeccablenpx agentmods add skills/leonxlnx/taste-skill/taste-skillEach name opens the mod's page: the scan, the token cost and every other way to install it.
A database, a command set and a website kit
On the first run, UI UX Pro Max calls search.py with a query, because it is a database with a search script. Impeccable starts with /impeccable init, which reads your code, asks what it can’t infer and writes PRODUCT.md. Taste Skill classifies the client’s business as one of six kinds (software, gaming, tech, product, service, place) and copies its assets folder into your project, where the build starts from assets/starter.html.
BM25 search, PRODUCT.md and dealt palettes
Search is the whole method in UI UX Pro Max. For a new page the skill tells the agent to run --design-system, which fires five searches across product types, styles, palettes, landing patterns and font pairings, then ranks styles with BM25. The output is a design system: pattern, style, colours, type, effects and anti-patterns. Add --persist and it lands in design-system/<project>/MASTER.md, which later runs won’t overwrite without --force. Three optional dials (variance, motion, density, each 1 to 10) shift the result without a new query.
What it does not do is touch your code. The README says so directly: search results are guidance and “do not automatically rewrite your app”.
Your own project files steer Impeccable. Every command reads PRODUCT.md, and /impeccable document captures your current look in DESIGN.md. It also sorts surfaces into modes. A landing page gets the Persuade treatment, while app UI, dashboards and admin screens are Operate, where the skill asks for restraint over expression. For a brand-new design it fetches a set of visual directions from the impeccable.style catalog. It covers native iOS and Android screens as well, which Taste Skill, whose description names only websites, does not.
Scripts make the visual calls in the taste skill. start.mjs deals a palette and a Google Fonts pairing for the page kind, and a second script deals one of eleven hero layouts. The skill’s instruction is blunt: “Deal, never choose by taste.” Each deal keeps a history file so the next page comes out different. Violet and lavender are banned from the page’s own design, and cafes, hotels, shops and services get no WebGL or scroll effects at all. For a cafe, shop or studio site that is the point: no effects, and the layout checked at four widths. The output starts as plain HTML; the README says the tokens and checks port to React, Vue, Svelte or Astro.
Who looks at the rendered page?
Nothing in the UI UX Pro Max skill does. The repository keeps a separate stack/ folder that explains the gap: most AI design fails “because the model never sees what it built”. That stack adds Anthropic’s frontend-design skill for taste, Playwright MCP and Chrome DevTools MCP for screenshots, and a design-review subagent. Install only the plugin and you get the knowledge layer alone, so pair it with a browser MCP if you want the result checked.
Three routes lead to Impeccable’s detector, which has 62 deterministic rules and needs no LLM or API key. The Claude Code plugin wires it into a PostToolUse hook on Edit|Write, plus a Stop hook with a 30-second timeout labelled “Design deep pass”. Without the hook, the README admits, the detector runs only when someone remembers. From the terminal, npx impeccable detect scans source or a URL and can print GitHub Actions annotations; it exits with code 2 on findings, so a CI job can fail on slop. On JSX or TSX it applies pattern rules only. Contrast and tiny-text rules need a rendered page, so point it at your dev server. The third route is a Chrome extension that overlays the same findings on any live page.
Taste Skill checks in a headless browser it starts itself. Its consistency.mjs renders the page in headless Chrome at 1440, 1024, 768 and 390 pixels and prints PASS, WARN or FAIL per rule, over 100 checks in all. The skill tells the agent to use only these scripts, “never a windowed browser or a browser tool”, so a browser MCP you already run stays out of the loop.
Reference files, seven skills and a 37 MB asset folder
Rules in UI UX Pro Max load on demand: the full list sits in references/quick-reference.md, and the skill tells the agent not to read it every time. The Claude Code plugin brings seven skills, not one: besides ui-ux-pro-max there are design, design-system, ui-styling, brand, banner-design and slides.
Before every UI edit, small ones included, Impeccable has the agent read reference/craft-floor.md, on top of the playbook for the command you named. Its working files go under .impeccable/ in your project.
Taste Skill is the heaviest of the three. Before the first page the agent must read four reference files in full, about 98 KB of text at this commit. The assets folder it copies into your project is about 37 MB.
Runtimes, API keys and network calls
For UI UX Pro Max you need Python 3. Its search script uses only the standard library and makes no network calls. The bundled design skill is different: logos, mockups and icons go through Gemini and want GEMINI_API_KEY. The README also advertises a premium version with brand identity, logo and slide skills; this page covers only the open repository.
A native engine binary does Impeccable’s work. If it is not shipped next to the skill, the launcher downloads it once from the project’s GitHub releases and refuses any download whose checksum isn’t recorded. Two behaviours need your attention before you run it unattended. Hooks in Claude Code run even when you deny the model’s commands, so the first edit can trigger that download. And live mode’s Apply, when no chat session is polling, launches codex or claude with approvals and sandboxing off. Set IMPECCABLE_LIVE_COPY_AGENT=chat or off if that is a problem. Telemetry is on until you run npx impeccable telemetry off or set DO_NOT_TRACK=1. One licence detail: package.json says Apache-2.0, but the Grok plugin manifest declares MIT.
You need Node 22+ and Chrome, Edge or Chromium for Taste Skill, with ffmpeg optional. It needs no API keys and goes online only to fetch extra photographs, Google Fonts or brand icons.
frontend-design, the single-file baseline
Anthropic’s frontend design skill, frontend-design, is where this field started. Impeccable says it began from it, and the UI UX Pro Max stack installs it as its taste layer. It is one SKILL.md and a licence file, with no scripts and no data. It has the agent plan a small token system, review the plan against the brief, then build, taking screenshots only if the environment supports them. It installs with the example-skills plugin from anthropics/skills.
Questions
Does UI UX Pro Max need an API key?
The main skill does not: its search script needs Python 3, uses only the standard library and makes no network calls. The plugin also installs a separate design skill for logos, mockups and icons, and that one asks for a Gemini API key.
Can Taste Skill design dashboards or app screens?
Its description lists landing pages and company, product, shop, cafe, hotel, studio and SaaS sites. Dashboards and app screens are not named. Impeccable has a separate Operate mode for app UI, dashboards and admin screens.
Sources
nextlevelbuilder/ui-ux-pro-max-skill at b7d5353
README.md · .claude/skills/ui-ux-pro-max/SKILL.md · .claude/skills/ui-ux-pro-max/scripts/core.py · .claude/skills/design/SKILL.md · .claude-plugin/plugin.json · skill.json · stack/README.md
pbakaus/impeccable at c3bb418
README.md · plugin/skills/impeccable/SKILL.md · plugin/skills/impeccable/scripts/impeccable · plugin/hooks/hooks.json · package.json · plugin/.grok-plugin/plugin.json
Leonxlnx/taste-skill at 9b4bf93
README.md · skills/taste-skill/SKILL.md
anthropics/skills at ca45fc4
skills/frontend-design/SKILL.md · .claude-plugin/marketplace.json
More comparisons
Andrej Karpathy skill: four rules in a CLAUDE.md, nothing that enforces them
Four rules in a 358-word file, no hooks, next to Superpowers and TDD Guard.
Obsidian skills for Claude Code: kepano/obsidian-skills and claude-obsidian
kepano's skills are plain Markdown; claude-obsidian hashes notes and can roll back.
Humanizer skill, Stop Slop and No AI Slop
Humanizer is a 5,219-word file read on every use; Stop Slop a 361-word list of bans.
Marketing skills for Claude Code: four packs compared
Four packs: one turns off TLS checks, one needs your API key, one hooks every Bash.
Figma MCP servers: which ones read, which ones edit
Framelink only reads a frame; Talk to Figma and Figma Console edit it. Figma's own: 6 calls/mo.
Playwright MCP vs Chrome DevTools MCP
Playwright MCP also runs Firefox and WebKit. Chrome DevTools MCP traces Chrome and reports stats.