designer-skills

In the author's own words, from each skill's SKILL.md — showing the first 30 of 111 files.

• design-critique

  Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).

  design-ops/skills/design-critique/SKILL.md on GitHub (opens in a new tab)

• design-debt-audit

  Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).

  design-ops/skills/design-debt-audit/SKILL.md on GitHub (opens in a new tab)

• design-impact-reporting

  Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).

  design-ops/skills/design-impact-reporting/SKILL.md on GitHub (opens in a new tab)

• design-qa-checklist

  Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.

  design-ops/skills/design-qa-checklist/SKILL.md on GitHub (opens in a new tab)

• design-review-process

  Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.

  design-ops/skills/design-review-process/SKILL.md on GitHub (opens in a new tab)

• design-sprint-plan

  Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.

  design-ops/skills/design-sprint-plan/SKILL.md on GitHub (opens in a new tab)

• handoff-spec

  Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).

  design-ops/skills/handoff-spec/SKILL.md on GitHub (opens in a new tab)

• team-workflow

  Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.

  design-ops/skills/team-workflow/SKILL.md on GitHub (opens in a new tab)

• version-control-strategy

  Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use `design-system-governance` (design-systems).

  design-ops/skills/version-control-strategy/SKILL.md on GitHub (opens in a new tab)

• affinity-diagram

  Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

  design-research/skills/affinity-diagram/SKILL.md on GitHub (opens in a new tab)

• behavioural-analytics

  Read funnels, retention curves, and event data as a designer — separating a design problem from a tracking artefact. Use when handed product data you did not design and asked why people drop off. For choosing what to measure, use `metrics-definition` (ux-strategy); for running a controlled test, use `a-b-test-design` (prototyping-testing).

  design-research/skills/behavioural-analytics/SKILL.md on GitHub (opens in a new tab)

• card-sort-analysis

  Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).

  design-research/skills/card-sort-analysis/SKILL.md on GitHub (opens in a new tab)

• diary-study-plan

  Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use `usability-test-plan`.

  design-research/skills/diary-study-plan/SKILL.md on GitHub (opens in a new tab)

• empathy-map

  Build a Says, Thinks, Does, Feels map for one user or segment. Use when sharing user understanding quickly. For a composite archetype with goals and behaviours use `user-persona`; for cross-session themes use `affinity-diagram`.

  design-research/skills/empathy-map/SKILL.md on GitHub (opens in a new tab)

• interview-script

  Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use `summarize-interview`.

  design-research/skills/interview-script/SKILL.md on GitHub (opens in a new tab)

• jobs-to-be-done

  Map functional, emotional, and social jobs with outcome expectations. Use when reframing decisions around motivation rather than features. For who the user is, use `user-persona`.

  design-research/skills/jobs-to-be-done/SKILL.md on GitHub (opens in a new tab)

• journey-map

  Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing).

  design-research/skills/journey-map/SKILL.md on GitHub (opens in a new tab)

• qual-quant-triangulation

  Reconcile what the numbers say with what users say, and design the study that settles it rather than restates it. Use when behavioural data and research findings point different ways. For reading the data on its own, use `behavioural-analytics`; for synthesising interviews on their own, use `affinity-diagram`.

  design-research/skills/qual-quant-triangulation/SKILL.md on GitHub (opens in a new tab)

• research-repository

  Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use `affinity-diagram`.

  design-research/skills/research-repository/SKILL.md on GitHub (opens in a new tab)

• summarize-interview

  Turn one interview transcript into themes, supporting quotes, and action items. Use immediately after a session. For synthesising many sessions at once, use `affinity-diagram`.

  design-research/skills/summarize-interview/SKILL.md on GitHub (opens in a new tab)

• survey-design

  Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use `a-b-test-design` (prototyping-testing).

  design-research/skills/survey-design/SKILL.md on GitHub (opens in a new tab)

• usability-test-plan

  Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use `test-scenario` (prototyping-testing).

  design-research/skills/usability-test-plan/SKILL.md on GitHub (opens in a new tab)

• user-persona

  Build research-grounded personas with goals, frustrations, and behavioural patterns. Use when decisions need a consistent user reference. For one session's emotional snapshot use `empathy-map`; for motivation framing use `jobs-to-be-done`.

  design-research/skills/user-persona/SKILL.md on GitHub (opens in a new tab)

• accessibility-audit

  Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

  design-systems/skills/accessibility-audit/SKILL.md on GitHub (opens in a new tab)

• component-spec

  Specify one component — props, states, variants, accessibility, and usage rules. Use when defining a library component. For the reusable doc scaffold use `documentation-template`; for a problem-solution pattern use `pattern-library`.

  design-systems/skills/component-spec/SKILL.md on GitHub (opens in a new tab)

• design-system-governance

  Define how the system evolves — contribution model, versioning, deprecation, and change management. Use when multiple teams contribute. For driving uptake use `design-system-adoption` (designer-toolkit); for design file history use `version-control-strategy` (design-ops).

  design-systems/skills/design-system-governance/SKILL.md on GitHub (opens in a new tab)

• design-token

  Define and organise tokens for colour, spacing, type, and elevation with naming and usage rules. Use when establishing the token layer. For auditing existing usage use `design-token-audit` (designer-toolkit); for multi-brand mapping use `theming-system`.

  design-systems/skills/design-token/SKILL.md on GitHub (opens in a new tab)

• documentation-template

  Generate a reusable documentation scaffold for components, patterns, or guidelines. Use when standardising how the system is documented. For the content of one component's spec, use `component-spec`.

  design-systems/skills/documentation-template/SKILL.md on GitHub (opens in a new tab)

• icon-system

  Specify an icon system — grid, sizing, stroke weight, naming, categories, and implementation. Use when standardising iconography. For broader illustration, use `illustration-style` (ui-design).

  design-systems/skills/icon-system/SKILL.md on GitHub (opens in a new tab)

• localization-design

  Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use `ux-writing` (designer-toolkit).

  design-systems/skills/localization-design/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• claude-code-tipsby ykdojo 45+ tips for getting the most out of Claude Code, from basics to advanced - includes a custom status line script and Claude Code running it… 10.3k stars · 9 skills
• oh-my-hermesby rlaope ⚚ The coding harness with Hermes Agent wired into IDE. 5.1k stars · 30 skills
• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 431k stars · 5 skills
• difyby langgenius Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-h… 160k stars
• cavemanby JuliusBrussee 🪨 why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman. 118k stars · 22 skills
• OpenMontageby calesthio World's first open-source, agentic video production system. 12 production pipelines, 100+ tools, 700+ agent skill and production-knowledge… 76.5k stars · 30 skills