Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides designers and design ops managers with a set of rigorous protocols for managing the creative process. It focuses on transforming subjective feedback into actionable outcomes through structured critique rules and standardized review gates.
The skills bridge the gap between creative execution and business value, offering methods to audit design debt and translate user outcomes into stakeholder language.
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
Select three design collections
Installs: Three explicitly selected plugins from the Designer Skills suite: design-research, ux-strategy, and design-systems. · Claude Code
Before you start
Claude Code installed, signed in, and open
Download Claude Code from claude.com, install it, sign in, and open it. This is a manual prerequisite and requires no terminal command.
In a Claude Code agent session, enter this command to add the Designer Skills marketplace. This registers where the skills live but does not install them yet.
In the Claude Code agent session, enter this command, open Discover, select design-research, ux-strategy, and design-systems with the arrow keys and space bar, then press enter to install those three plugins.
One interview transcript supplied as pasted text or a file path such as <path-to-transcript>
Optional product or research context
Use the summarize-interview skill on the transcript at <path-to-transcript>, or on the transcript text I paste. Produce a participant profile, 3–5 key themes with supporting quotes, jobs-to-be-done, pain points, workarounds, delighters, surprises, and specific follow-up actions. Mark each insight as explicitly stated or inferred.
Use the metrics-definition skill for <feature-or-design-decision>. Recommend 3–5 primary UX metrics that balance behavioral and attitudinal evidence. For each metric, provide its definition, measurement method, data source, target, measurement frequency, and owner, and connect it to the design hypothesis. Clearly identify any baseline information that is still missing.
Existing designs, implementation, or requirements at <path-to-component-materials>
Relevant design-system conventions and constraints
Use the component-spec skill to draft an implementable specification for the <component-name> component. Cover its purpose, anatomy, variants, props or API, states, behavior, accessibility, edge cases, and concise do/don't guidance. Use the supplied design-system conventions and component evidence; label unresolved decisions instead of assuming them.
Claude
Gemini CLI