designer-skills

I only want the design skills, not everything

Same three steps. On the Discover list in step 3, just tick the design ones, design-research, design-systems, ui-design, interaction-design, and so on, and leave the rest. Install as few or as many as you like, and come back for more any time.

I only want one specific collection

Each collection also has its own door. Swap the command in step 2 for the one you want, for example:

/plugin marketplace add Owl-Listener/inclusive-design-skills

Then do step 3 the same way.

Prefer Gemini CLI?

Each plugin is also a Gemini CLI extension. From your project root:

git clone https://github.com/Owl-Listener/designer-skills /tmp/designer-skills
mkdir -p .gemini/extensions
cp -r /tmp/designer-skills/.gemini/extensions/. .gemini/extensions/

The five collections

The other four collections each live in their own repo, with their own stars and full detail, and this marketplace pulls their plugins in for you — so the one install above covers all five. This repo is the front door, and the home of the design-practice collection below.

Design practice (this repo)

Agentic skills, commands, and plugins for design, from research to systems, UI, interaction, and delivery. 111 skills and 34 commands across 9 plugins.

Plugins

These nine plugins ship from this repo — none of them has a separate repo, and there is nothing to clone. After adding the marketplace, install one by name:

/plugin install ux-strategy@designer-skills

All commands

What are skills and commands?

Skills are domain knowledge units — nouns. They teach Claude about a design topic: how to create a user persona, how to define design tokens, how to write a non-leading interview question.

Commands are workflows — verbs. They chain skills together to do a complete job: /design-research:discover runs personas, empathy map, and journey map in one go.

You'll mostly reach for commands. The skills run underneath them.

Pick your starting point

I'm starting a new product from scratch

Start with research, even if you think you know the users.

/design-research:discover

Tell Claude: what you're building, who you think the users are, and what problem you're solving. It will run a full discovery cycle — personas, empathy map, journey map — and surface the gaps in your assumptions.

From there, move in sequence:

• /ux-strategy:frame-problem — structure the design challenge before you start designing
• /ui-design:design-screen — when you're ready to build
• /interaction-design:design-interaction — for any flows that have meaningful state or motion
• /design-systems:create-component — when patterns start repeating and you need to systemise them

Minimum install for this path: design-research, ux-strategy, ui-design, interaction-design

I'm working on an existing product

Start with a critique, not new work.

/visual-critique:critique-screen

Drop a screenshot. Get a prioritised fix list covering hierarchy, brand consistency, composition, and typography. This tells you what's actually broken before you add anything new.

Then:

• /prototyping-testing:evaluate — run a heuristic evaluation if you want a fuller audit
• /design-ops:handoff — if you're in a delivery phase and need specs
• /design-systems:audit-system — if you suspect system debt is the root cause

Minimum install for this path: visual-critique, prototyping-testing, design-ops

I have a specific deliverable to produce

Go directly to the plugin that covers it. You don't need everything.

That covers the most common asks. For all 107 skills — including the ones without a command in front of them — see the skill index.

I'm building with AI and need to design the AI experience

This collection covers conventional design. For designing AI products specifically — model interaction, alignment reasoning, error personality, agent orchestration — use the companion collection:

/plugin marketplace add Owl-Listener/ai-design-skills

The two collections are designed to work alongside each other.

Recommended install for most designers

If you're not sure where to start, install these five and you'll have coverage across the full design cycle, plus the router that tells you where to begin:

/plugin install design-research@designer-skills
/plugin install ux-strategy@designer-skills
/plugin install ui-design@designer-skills
/plugin install design-ops@designer-skills
/plugin install designer-toolkit@designer-skills

designer-toolkit is the one carrying /start-here, so install it even if you want nothing else from it.

Add others as you need them. The plugins are lightweight — installing more doesn't slow things down.

A note on sequence

The plugins aren't a strict pipeline, but there's a natural grain to them:

design-research → ux-strategy → ui-design / interaction-design → design-systems → design-ops

Research informs strategy. Strategy shapes UI decisions. Patterns in UI become system components. Systems flow into ops. Working against this grain is fine — but if something feels hard, it's often because a step earlier in the sequence was skipped.

Why this exists

Most design knowledge is written for humans to read and interpret. An agent gets none of that nuance. It reads what we wrote literally, and guesses where we left the meaning out, and the guesses pile up into something hollow. This suite writes the judgment down: what a thing is for, when to use it, and what to never do. Taste, made legible.

Questions?

Open an issue. If something isn't working the way you expected, or if a skill output feels wrong for your context, that's signal worth capturing.

Contributing

Contribute to a collection in the repo that hosts it. The nine design-practice plugins live here, so skills and fixes for them — ux-strategy included — are PRs against this repo. The other four collections take contributions in their own repos, linked in the table above. Add a skill, ship its plugin manifest in the same commit, and open a PR. PRs for new skills or structural changes without a corresponding open issue will be closed without review.

Community Integrations

Tools and plugins built on top of designer-skills:

IntegrationDescriptionMaintainerdesign-library-pluginClaude Code plugin exposing designer-skills via /design-process, with keyword activation across wireframe, prototype, user research, design sprint, and handoff workflows@zeta92

If you've built something on top of this collection and want it listed here, open an issue.

License

MIT.

By MC Dean · MC Percolates on Substack

内容由编辑整理，部分信息来自 GitHub 与项目官网，版权归原作者所有。发现错误？报告问题