StackMap
Subscribe

designer-skills vs taste-skill

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 — Agent skill that art-directs coding agents into polished company websites — one design system, real photos and icons, restrained motion — verified in a real browser by a finish gate.

The curated verdict

Both make coding agents better designers; designer-skills is a broad 239-skill library across research, systems and UI, while taste-skill is one opinionated website-build skill with a browser-enforced finish gate.

designer-skillstaste-skill
Stars3.4k119k
Forks4478.0k
LanguageMarkdownJavaScript
LicenseMITMIT
Last activitytoday11 days ago
Topicsskillsskills
Curated connections93

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.

taste-skill — the curator's take

Install when your agent ships landing pages that all look like the same purple-gradient template: it enforces real art direction and checks the result in Chrome instead of trusting the agent's word. Opinionated by design — it imposes its own taste, so skip it when you already have a brand system to follow (feed that in instead) or when you're building app UI/dashboards rather than marketing sites. Needs Node 22+ and a local Chromium.