designer-skills vs impeccable
239 design skills, 88 commands and 33 plugins for Claude Code and Gemini CLI — research, design systems, UI, interaction and delivery, written for agents to actually execute. — versus — Design vocabulary skill for coding agents: commands like polish, bolder, critique and audit, plus a 62-rule deterministic detector that catches AI-slop UI before it ships.
Both bring design expertise to coding agents; designer-skills is a sprawling library, Impeccable a tight command vocabulary with deterministic checks.
| designer-skills | impeccable | |
|---|---|---|
| Stars | 3.4k | 113k |
| Forks | 447 | 6.8k |
| Language | Markdown | Rust |
| License | MIT | Apache-2.0 |
| Last activity | today | today |
| Topics | skills | skills |
| Curated connections | 10 | 3 |
designer-skills — the curator's take
The largest coherent skill pack for design work: five collections covering research→systems→UI→interaction→delivery, installable straight from Claude Code's plugin marketplace with genuinely non-technical instructions. If you're a designer adopting agents (or an engineer faking design taste), this is the fastest on-ramp. NOT a design tool itself — it's prompts-as-skills, so output quality tracks the underlying model, and 239 skills means uneven depth: audit the ones you'll actually use rather than installing all five collections on day one.
impeccable — the curator's take
Best when iterating on UI that already exists: name a move and a target, get a focused playbook, then critique/audit with ranked findings — the slop detector needs no LLM. Works across ~20 agents. It steers rather than art-directs from scratch; for whole marketing sites built from one brief with browser verification, taste-skill goes further.