Skip to content
Back to search

designer-skills

MarketplaceWorks with Claude CodeGitHub

The Designer Skills suite: agentic skills, commands, and plugins for design in the agent era — design practice, AI product design, UX program management, design leadership, and inclusive design. One install surfaces every collection: the design-practice plugins ship from this repo, and the other four collections are pulled in from their own repos.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/owl-listener-designer-skills/badge.svg)](/listings/owl-listener-designer-skills)

HTML

<a href="/listings/owl-listener-designer-skills"><img src="/api/listings/owl-listener-designer-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These skills run inside an AI coding assistant. The easiest place to use them is Claude Code, and it takes three steps. No terminal required.

**1. Get Claude Code.** It's a free app from Anthropic (claude.com). Download it, sign in, and open it. You only do this once.

**2. Add the suite.** In Claude Code, type this and press enter:

/plugin marketplace add Owl-Listener/designer-skills

This just tells Claude where the skills live. Nothing installs yet.

**3. Pick what you want.** Type `/plugin` and press enter, then open the **Discover** tab. You'll see all the collections. Move with the arrow keys, press space to tick the ones you want, and enter to install. That's it.

**4. Don't know which skill you need?** Type `/designer-toolkit:start-here` and say what you're working on. It names the stage you're at, gives you one command to run now and the two that follow it, and tells you what you can skip. Use it whenever you're unsure where a piece of work begins.

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/

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 306 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "designer-skills",
  4. "version": "2.0.0",
  5. "description": "The Designer Skills suite: agentic skills, commands, and plugins for design in the agent era \u2014 design practice, AI product design, UX program management, design leadership, and inclusive design. One install surfaces every collection: the design-practice plugins ship from this repo, and the other four collections are pulled in from their own repos.",
  6. "owner": {
  7. "name": "MC Dean",
  8. "url": "https://marieclairedean.substack.com/"
  9. },
  10. "plugins": [
  11. {
  12. "name": "design-research",
  13. "description": "User research skills for designers: personas, empathy maps, journey maps, interview scripts, usability testing, card sorting, behavioural analytics, and reconciling data with research.",
  14. "source": "./design-research",
  15. "category": "design"
  16. },
  17. {
  18. "name": "design-systems",
  19. "description": "Design system skills: component specs, design tokens, naming conventions, spacing and grid systems, accessibility standards, and documentation.",
  20. "source": "./design-systems",
  21. "category": "design"
  22. },
  23. {
  24. "name": "ux-strategy",
  25. "description": "UX strategy skills: information architecture, content strategy, navigation patterns, user flows, task analysis, and competitive UX audits.",
  26. "source": "./ux-strategy",
  27. "category": "design"
  28. },
  29. {
  30. "name": "ui-design",
  31. "description": "UI design skills: color palettes, typography systems, layout grids, responsive breakpoints, dark mode specs, visual hierarchy, and brand alignment.",
  32. "source": "./ui-design",
  33. "category": "design"
  34. },
  35. {
  36. "name": "interaction-design",
  37. "description": "Interaction design skills: micro-interactions, animation principles, state machines, gesture patterns, error handling UX, and feedback patterns.",
  38. "source": "./interaction-design",
  39. "category": "design"
  40. },
  41. {
  42. "name": "prototyping-testing",
  43. "description": "Prototyping and testing skills: wireframe specs, usability heuristics, heuristic evaluations, accessibility audits, A/B test design, and benchmark analysis.",
  44. "source": "./prototyping-testing",
  45. "category": "design"
  46. },
  47. {
  48. "name": "design-ops",
  49. "description": "Design operations skills: handoff specs, design critique facilitation, design sprint planning, team workflows, QA checklists, and design debt audits.",
  50. "source": "./design-ops",
  51. "category": "design"
  52. },
  53. {
  54. "name": "designer-toolkit",
  55. "description": "Designer utility skills: design rationale, case study structure, design presentations, UX writing, design system adoption, and design negotiation — plus the /start-here router.",
  56. "source": "./designer-toolkit",
  57. "category": "design"
  58. },
  59. {
  60. "name": "visual-critique",
  61. "description": "Visual critique skills: hierarchy analysis, brand consistency checks against mood/voice/tokens, composition evaluation, and typography audits \u2014 with a /critique-screen command that compiles a prioritised fix list.",
  62. "source": "./visual-critique",
  63. "category": "design"
  64. },
  65. {
  66. "name": "program-planning",
  67. "description": "Plan and scope UX programs: roadmaps, dependency maps, capacity planning, prioritisation.",
  68. "source": {
  69. "source": "git-subdir",
  70. "url": "https://github.com/Owl-Listener/ux-pgm-skills.git",
  71. "path": "program-planning"
  72. },
  73. "category": "product"
  74. },
  75. {
  76. "name": "stakeholder-comms",
  77. "description": "Stakeholder mapping, status reporting, executive updates, alignment workshops, escalation.",
  78. "source": {
  79. "source": "git-subdir",
  80. "url": "https://github.com/Owl-Listener/ux-pgm-skills.git",
  81. "path": "stakeholder-comms"
  82. },
  83. "category": "product"
  84. },
  85. {
  86. "name": "delivery-execution",
  87. "description": "Cycle orchestration, risk registers, blocker triage, launch readiness, retrospectives.",
  88. "source": {
  89. "source": "git-subdir",
  90. "url": "https://github.com/Owl-Listener/ux-pgm-skills.git",
  91. "path": "delivery-execution"
  92. },
  93. "category": "product"
  94. },
  95. {
  96. "name": "cross-functional-alignment",
  97. "description": "Intake, decision logs, working agreements, RACI, and OKR linkage across functions.",
  98. "source": {
  99. "source": "git-subdir",
  100. "url": "https://github.com/Owl-Listener/ux-pgm-skills.git",
  101. "path": "cross-functional-alignment"
  102. },
  103. "category": "product"
  104. },
  105. {
  106. "name": "measurement-ops",
  107. "description": "Program health: KPIs, dashboards, research ops, design ops metrics, impact reporting.",
  108. "source": {
  109. "source": "git-subdir",
  110. "url": "https://github.com/Owl-Listener/ux-pgm-skills.git",
  111. "path": "measurement-ops"
  112. },
  113. "category": "product"
  114. },
  115. {
  116. "name": "process-design",
  117. "description": "How the team works: workflows, governance, rituals, scaling playbooks, retrospectives.",
  118. "source": {
  119. "source": "git-subdir",
  120. "url": "https://github.com/Owl-Listener/ux-pgm-skills.git",
  121. "path": "process-design"
  122. },
  123. "category": "product"
  124. },
  125. {
  126. "name": "people-management",
  127. "description": "1:1s, feedback, growth plans, performance reviews, career ladders, difficult conversations.",
  128. "source": {
  129. "source": "git-subdir",
  130. "url": "https://github.com/Owl-Listener/design-leadership-skills.git",
  131. "path": "people-management"
  132. },
  133. "category": "design"
  134. },
  135. {
  136. "name": "team-building",
  137. "description": "Hiring loops, job specs, portfolio review, onboarding, team topology, psychological safety.",
  138. "source": {
  139. "source": "git-subdir",
  140. "url": "https://github.com/Owl-Listener/design-leadership-skills.git",
  141. "path": "team-building"
  142. },
  143. "category": "design"
  144. },
  145. {
  146. "name": "design-strategy",
  147. "description": "Design vision, strategy docs, org-level principles, investment cases, portfolio prioritisation.",
  148. "source": {
  149. "source": "git-subdir",
  150. "url": "https://github.com/Owl-Listener/design-leadership-skills.git",
  151. "path": "design-strategy"
  152. },
  153. "category": "design"
  154. },
  155. {
  156. "name": "org-influence",
  157. "description": "Executive narrative, influence mapping, advocacy, securing resources, managing up.",
  158. "source": {
  159. "source": "git-subdir",
  160. "url": "https://github.com/Owl-Listener/design-leadership-skills.git",
  161. "path": "org-influence"
  162. },
  163. "category": "design"
  164. },
  165. {
  166. "name": "operating-cadence",
  167. "description": "Design reviews at scale, planning cadence, decision frameworks, delegation, operating rhythm.",
  168. "source": {
  169. "source": "git-subdir",
  170. "url": "https://github.com/Owl-Listener/design-leadership-skills.git",
  171. "path": "operating-cadence"
  172. },
  173. "category": "design"
  174. },
  175. {
  176. "name": "leadership-craft",
  177. "description": "Self-leadership, change leadership, conflict resolution, mentorship, leadership ethics.",
  178. "source": {
  179. "source": "git-subdir",
  180. "url": "https://github.com/Owl-Listener/design-leadership-skills.git",
  181. "path": "leadership-craft"
  182. },
  183. "category": "design"
  184. },
  185. {
  186. "name": "model-interaction-design",
  187. "description": "Interaction patterns for AI products: mixed-initiative flow, handoff protocols, error personality.",
  188. "source": {
  189. "source": "git-subdir",
  190. "url": "https://github.com/Owl-Listener/ai-design-skills.git",
  191. "path": "claude-plugin/model-interaction-design"
  192. },
  193. "category": "ai"
  194. },
  195. {
  196. "name": "ai-alignment-reasoning",
  197. "description": "Alignment reasoning and harm anticipation translated into practitioner design skills.",
  198. "source": {
  199. "source": "git-subdir",
  200. "url": "https://github.com/Owl-Listener/ai-design-skills.git",
  201. "path": "claude-plugin/ai-alignment-reasoning"
  202. },
  203. "category": "ai"
  204. },
  205. {
  206. "name": "system-behavior-shaping",
  207. "description": "Shape system behaviour: defaults, guardrails, refusals, and behavioural contracts.",
  208. "source": {
  209. "source": "git-subdir",
  210. "url": "https://github.com/Owl-Listener/ai-design-skills.git",
  211. "path": "claude-plugin/system-behavior-shaping"
  212. },
  213. "category": "ai"
  214. },
  215. {
  216. "name": "evaluation",
  217. "description": "Evaluate agentic experiences: behaviour evals, trust calibration, failure analysis.",
  218. "source": {
  219. "source": "git-subdir",
  220. "url": "https://github.com/Owl-Listener/ai-design-skills.git",
  221. "path": "claude-plugin/evaluation"
  222. },
  223. "category": "ai"
  224. },
  225. {
  226. "name": "design-agent-orchestration",
  227. "description": "Design how agents collaborate, hand off, and stay legible to people.",
  228. "source": {
  229. "source": "git-subdir",
  230. "url": "https://github.com/Owl-Listener/ai-design-skills.git",
  231. "path": "claude-plugin/design-agent-orchestration"
  232. },
  233. "category": "ai"
  234. },
  235. {
  236. "name": "prompt-architecture",
  237. "description": "Structure prompts and context as a design material, not an afterthought.",
  238. "source": {
  239. "source": "git-subdir",
  240. "url": "https://github.com/Owl-Listener/ai-design-skills.git",
  241. "path": "claude-plugin/prompt-architecture"
  242. },
  243. "category": "ai"
  244. },
  245. {
  246. "name": "cognitive-accessibility",
  247. "description": "Design for how people actually think: cognitive load, plain language, wayfinding, focus, memory, error recovery.",
  248. "source": {
  249. "source": "git-subdir",
  250. "url": "https://github.com/Owl-Listener/inclusive-design-skills.git",
  251. "path": "cognitive-accessibility"
  252. },
  253. "category": "accessibility"
  254. },
  255. {
  256. "name": "inclusive-interaction",
  257. "description": "Multi-modal interactions that adapt to how people move, perceive, and communicate.",
  258. "source": {
  259. "source": "git-subdir",
  260. "url": "https://github.com/Owl-Listener/inclusive-design-skills.git",
  261. "path": "inclusive-interaction"
  262. },
  263. "category": "accessibility"
  264. },
  265. {
  266. "name": "accessible-content",
  267. "description": "Structure content that works for screen readers, cognitive differences, and diverse literacy levels.",
  268. "source": {
  269. "source": "git-subdir",
  270. "url": "https://github.com/Owl-Listener/inclusive-design-skills.git",
  271. "path": "accessible-content"
  272. },
  273. "category": "accessibility"
  274. },
  275. {
  276. "name": "inclusive-personas",
  277. "description": "User stories, personas, and scenarios that include disability from the start.",
  278. "source": {
  279. "source": "git-subdir",
  280. "url": "https://github.com/Owl-Listener/inclusive-design-skills.git",
  281. "path": "inclusive-personas"
  282. },
  283. "category": "accessibility"
  284. },
  285. {
  286. "name": "adaptive-interfaces",
  287. "description": "Design systems that respect user preferences and adapt to individual needs.",
  288. "source": {
  289. "source": "git-subdir",
  290. "url": "https://github.com/Owl-Listener/inclusive-design-skills.git",
  291. "path": "adaptive-interfaces"
  292. },
  293. "category": "accessibility"
  294. },
  295. {
  296. "name": "accessibility-decisions",
  297. "description": "Document, communicate, and maintain accessibility decisions across teams and time.",
  298. "source": {
  299. "source": "git-subdir",
  300. "url": "https://github.com/Owl-Listener/inclusive-design-skills.git",
  301. "path": "accessibility-decisions"
  302. },
  303. "category": "accessibility"
  304. }
  305. ]
  306. }
README.md · README · 255 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # The Designer Skills Pack
  2. Design skills for the agent era, written so an AI agent can actually use them.
  3. **273 skills and 76 commands across 33 plugins, in five collections**, for [Claude Code](https://docs.anthropic.com/en/docs/claude-code) and [Gemini CLI](https://github.com/google-gemini/gemini-cli).
  4. **Not sure which skill you need? Start with the [skill index](./INDEX.md)** — every skill in this repo arranged by the situation you're in, plus the pairs most often mistaken for each other.
  5. ## Getting started (no coding needed)
  6. These skills run inside an AI coding assistant. The easiest place to use them is Claude Code, and it takes three steps. No terminal required.
  7. **1. Get Claude Code.** It's a free app from Anthropic (claude.com). Download it, sign in, and open it. You only do this once.
  8. **2. Add the suite.** In Claude Code, type this and press enter:
  9. ```
  10. /plugin marketplace add Owl-Listener/designer-skills
  11. ```
  12. This just tells Claude where the skills live. Nothing installs yet.
  13. **3. Pick what you want.** Type `/plugin` and press enter, then open the **Discover** tab. You'll see all the collections. Move with the arrow keys, press space to tick the ones you want, and enter to install. That's it.
  14. **4. Don't know which skill you need?** Type `/designer-toolkit:start-here` and say what you're working on. It names the stage you're at, gives you one command to run now and the two that follow it, and tells you what you can skip. Use it whenever you're unsure where a piece of work begins.
  15. ### I only want the design skills, not everything
  16. 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.
  17. ### I only want one specific collection
  18. Each collection also has its own door. Swap the command in step 2 for the one you want, for example:
  19. ```
  20. /plugin marketplace add Owl-Listener/inclusive-design-skills
  21. ```
  22. Then do step 3 the same way.
  23. ### Prefer Gemini CLI?
  24. Each plugin is also a Gemini CLI extension. From your project root:
  25. ```
  26. git clone https://github.com/Owl-Listener/designer-skills /tmp/designer-skills
  27. mkdir -p .gemini/extensions
  28. cp -r /tmp/designer-skills/.gemini/extensions/. .gemini/extensions/
  29. ```
  30. ## The five collections
  31. | Collection | Plugins | What it covers |
  32. | --- | --- | --- |
  33. | Design practice (this repo) | 9 | Research, systems, UX strategy, UI, interaction, prototyping & testing, design ops, the designer's toolkit, visual critique. |
  34. | [AI product design](https://github.com/Owl-Listener/ai-design-skills) | 6 | Designing agentic experiences: model interaction, alignment reasoning, system behaviour, evaluation, agent orchestration, prompt architecture. |
  35. | [UX program management](https://github.com/Owl-Listener/ux-pgm-skills) | 6 | Running design programs: planning, stakeholder comms, delivery, alignment, measurement, process design. |
  36. | [Design leadership](https://github.com/Owl-Listener/design-leadership-skills) | 6 | Leading design: people, teams, strategy, org influence, operating cadence, leadership craft. |
  37. | [Inclusive design](https://github.com/Owl-Listener/inclusive-design-skills) | 6 | Accessible by default: cognitive accessibility, inclusive interaction, accessible content, inclusive personas, adaptive interfaces, accessibility decisions. |
  38. 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.
  39. ---
  40. ## Design practice (this repo)
  41. Agentic skills, commands, and plugins for design, from research to systems, UI, interaction, and delivery. **111 skills and 34 commands across 9 plugins.**
  42. ### Plugins
  43. | Plugin | Skills | Commands | Description |
  44. | --- | --- | --- | --- |
  45. | design-research | 14 | 4 | User research, qualitative and quantitative: personas, empathy maps, journey maps, interviews, usability testing, card sorting, surveys, behavioural analytics, and qual-quant triangulation. |
  46. | design-systems | 11 | 3 | Build and maintain design systems: tokens, components, accessibility, theming, motion, governance, and localization. |
  47. | ux-strategy | 12 | 3 | Shape product direction: competitive analysis, design principles, experience mapping, information architecture, content strategy, and service blueprints. |
  48. | ui-design | 19 | 5 | Craft polished interfaces: layout grids, color systems, typography, responsive design, data viz, Gestalt/perceptual principles, and platform conventions. |
  49. | interaction-design | 22 | 5 | Design meaningful interactions: micro-animations, state machines, gestures, feedback, cognitive laws, forms, onboarding, navigation, search, and conversational UX. |
  50. | prototyping-testing | 10 | 5 | Validate designs: prototyping strategies, usability testing, heuristic evaluation, and A/B experiments. |
  51. | design-ops | 9 | 3 | Streamline operations: critique frameworks, handoff specs, sprint planning, team workflows, design debt, and impact reporting. |
  52. | designer-toolkit | 7 | 4 | Essential utilities: design rationale, presentations, case studies, UX writing, system adoption, and design negotiation. |
  53. | visual-critique | 7 | 2 | Visual critique: hierarchy, brand consistency, composition, typography, colour, affordance, and information density. |
  54. 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:
  55. ```
  56. /plugin install ux-strategy@designer-skills
  57. ```
  58. ### All commands
  59. | Command | Plugin | Description |
  60. | --- | --- | --- |
  61. | `/design-ops:handoff` | design-ops | Run the full handoff workflow — specs, measurements, assets, states, and a QA checklist — and output a developer-ready package. |
  62. | `/design-ops:plan-sprint` | design-ops | Run a design sprint end to end — challenge framing, schedule, exercises, and prototype test plan. |
  63. | `/design-ops:setup-workflow` | design-ops | Set up a team's operating rhythm end to end — rituals, task flow, tooling, review gates, and version control. |
  64. | `/design-research:discover` | design-research | Run a full user research cycle — persona creation, empathy mapping, and journey mapping for a product or feature. |
  65. | `/design-research:interview` | design-research | Prepare an interview script or summarize an interview transcript into structured insights. |
  66. | `/design-research:synthesize` | design-research | Synthesize research data into affinity diagrams, themes, and actionable insights. |
  67. | `/design-research:test-plan` | design-research | Run the full usability study workflow — research questions, participant criteria, tasks, metrics, and facilitation guide. |
  68. | `/design-systems:audit-system` | design-systems | Run a comprehensive audit of an existing design system for consistency, completeness, and accessibility. |
  69. | `/design-systems:create-component` | design-systems | Scaffold a full component specification end to end — props, states, variants, accessibility, and documentation. |
  70. | `/design-systems:tokenize` | design-systems | Extract tokens from an existing design or stylesheet and organise them — naming, structure, and theme mapping. |
  71. | `/designer-toolkit:build-presentation` | designer-toolkit | Build a design presentation end to end — audience framing, narrative structure, and supporting rationale. |
  72. | `/designer-toolkit:start-here` | designer-toolkit | Find where to start in the collection — name what you're working on and get routed to one command, the two that follow it, and the stages you can skip. |
  73. | `/designer-toolkit:write-case-study` | designer-toolkit | Build a portfolio case study end to end — project framing, process narrative, outcomes, and visuals. |
  74. | `/designer-toolkit:write-rationale` | designer-toolkit | Write design rationale for a set of decisions, linking each to user needs, business goals, and principles. |
  75. | `/interaction-design:design-form` | interaction-design | Design a form end to end — structure, decision points, chunking, validation, errors, and completion. |
  76. | `/interaction-design:design-interaction` | interaction-design | Design a complete interaction flow for a feature or component. |
  77. | `/interaction-design:design-onboarding` | interaction-design | Design a first-run experience end to end — activation path, progressive disclosure, and time to first value. |
  78. | `/interaction-design:error-flow` | interaction-design | Design an error flow end to end — prevention, detection, messaging, and recovery paths. |
  79. | `/interaction-design:map-states` | interaction-design | Model a component's states and transitions end to end — states, events, guards, and edge cases. |
  80. | `/prototyping-testing:evaluate` | prototyping-testing | Run a heuristic evaluation end to end — expert review against heuristics with severity ratings and recommended fixes. |
  81. | `/prototyping-testing:experiment` | prototyping-testing | Design an A/B experiment end to end — hypothesis, variants, primary metric, and sample size. |
  82. | `/prototyping-testing:explore-options` | prototyping-testing | Run a parallel exploration end to end — frame the decision, build a spread of behaviourally distinct concepts, pressure-test each, and converge with a decision record. |
  83. | `/prototyping-testing:prototype-plan` | prototyping-testing | Create a prototyping and testing plan for a design initiative. |
  84. | `/prototyping-testing:test-plan` | prototyping-testing | Choose a testing method and build the plan around it — method selection, task scenarios, click tests, and accessibility coverage. |
  85. | `/ui-design:color-palette` | ui-design | Run the full colour workflow — tonal scales, semantic mapping, contrast checks, dark mode, and chart colours — and output a documented palette. |
  86. | `/ui-design:design-screen` | ui-design | Design a complete screen layout from a description or requirements. |
  87. | `/ui-design:platform-audit` | ui-design | Audit a design for iOS and Android convention compliance — navigation, controls, typography, and platform-specific gaps. |
  88. | `/ui-design:responsive-audit` | ui-design | Audit a design's responsive behaviour across breakpoints — layout, touch targets, and content reflow. |
  89. | `/ui-design:type-system` | ui-design | Build a typography system end to end — scale, weights, line heights, measure, and responsive behaviour. |
  90. | `/ux-strategy:benchmark` | ux-strategy | Run a competitive benchmark across a set of products — pattern comparison, gap analysis, and opportunity callouts. |
  91. | `/ux-strategy:frame-problem` | ux-strategy | Structure an ambiguous design challenge into a clear problem definition with constraints and criteria. |
  92. | `/ux-strategy:strategize` | ux-strategy | Develop a complete UX strategy for a product or feature area. |
  93. | `/visual-critique:critique-screen` | visual-critique | Run all seven visual critiques on a screen and output a prioritised fix list. |
  94. | `/visual-critique:critique-ux` | visual-critique | Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list. |
  95. ## What are skills and commands?
  96. **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.
  97. **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.
  98. You'll mostly reach for commands. The skills run underneath them.
  99. ## Pick your starting point
  100. ### I'm starting a new product from scratch
  101. Start with research, even if you think you know the users.
  102. ```
  103. /design-research:discover
  104. ```
  105. 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.
  106. From there, move in sequence:
  107. - `/ux-strategy:frame-problem` — structure the design challenge before you start designing
  108. - `/ui-design:design-screen` — when you're ready to build
  109. - `/interaction-design:design-interaction` — for any flows that have meaningful state or motion
  110. - `/design-systems:create-component` — when patterns start repeating and you need to systemise them
  111. **Minimum install for this path:** design-research, ux-strategy, ui-design, interaction-design
  112. ### I'm working on an existing product
  113. Start with a critique, not new work.
  114. ```
  115. /visual-critique:critique-screen
  116. ```
  117. 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.
  118. Then:
  119. - `/prototyping-testing:evaluate` — run a heuristic evaluation if you want a fuller audit
  120. - `/design-ops:handoff` — if you're in a delivery phase and need specs
  121. - `/design-systems:audit-system` — if you suspect system debt is the root cause
  122. **Minimum install for this path:** visual-critique, prototyping-testing, design-ops
  123. ### I have a specific deliverable to produce
  124. Go directly to the plugin that covers it. You don't need everything.
  125. | What you need to produce | Plugin | Command |
  126. | --- | --- | --- |
  127. | User personas | design-research | — |
  128. | Interview script | design-research | `/design-research:interview` |
  129. | Journey map | design-research | — |
  130. | Competitive analysis | ux-strategy | `/ux-strategy:benchmark` |
  131. | Colour palette | ui-design | `/ui-design:color-palette` |
  132. | Typography system | ui-design | `/ui-design:type-system` |
  133. | Component spec | design-systems | `/design-systems:create-component` |
  134. | Design tokens | design-systems | `/design-systems:tokenize` |
  135. | Usability test plan | prototyping-testing | `/prototyping-testing:test-plan` |
  136. | Developer handoff | design-ops | `/design-ops:handoff` |
  137. | Design rationale | designer-toolkit | `/designer-toolkit:write-rationale` |
  138. | Case study | designer-toolkit | `/designer-toolkit:write-case-study` |
  139. That covers the most common asks. For all 107 skills — including the ones without a command in front of them — see the [skill index](./INDEX.md).
  140. ### I'm building with AI and need to design the AI experience
  141. This collection covers conventional design. For designing AI products specifically — model interaction, alignment reasoning, error personality, agent orchestration — use the companion collection:
  142. ```
  143. /plugin marketplace add Owl-Listener/ai-design-skills
  144. ```
  145. The two collections are designed to work alongside each other.
  146. ## Recommended install for most designers
  147. 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:
  148. ```
  149. /plugin install design-research@designer-skills
  150. /plugin install ux-strategy@designer-skills
  151. /plugin install ui-design@designer-skills
  152. /plugin install design-ops@designer-skills
  153. /plugin install designer-toolkit@designer-skills
  154. ```
  155. `designer-toolkit` is the one carrying `/start-here`, so install it even if you want nothing else from it.
  156. Add others as you need them. The plugins are lightweight — installing more doesn't slow things down.
  157. ## A note on sequence
  158. The plugins aren't a strict pipeline, but there's a natural grain to them:
  159. **design-research → ux-strategy → ui-design / interaction-design → design-systems → design-ops**
  160. 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.
  161. ## Why this exists
  162. 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.
  163. ## Questions?
  164. 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.
  165. ## Contributing
  166. 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.
  167. PRs for new skills or structural changes without a corresponding open issue will be closed without review.
  168. ## Community Integrations
  169. Tools and plugins built on top of designer-skills:
  170. 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
  171. If you've built something on top of this collection and want it listed here, open an issue.
  172. ## License
  173. MIT.
  174. By MC Dean · [MC Percolates on Substack](https://marieclairedean.substack.com)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.