Owl-Listener/designer-skills

DirSkills catalogs 25 skills from this repository, across 5 categories: Automation, Data, Frontend, Quality, Writing.

2.1K stars335 forksView on GitHub
2w ago

Accessibility Audit

Accessibility Audit examines an existing interface against WCAG criteria, identifies barriers, and provides severity-rated findings with remediation steps. Use it when you have a design or build to assess now, not for planning future assistive-technology testing sessions.
Quality
2.1K335
🗂️
2w ago

Affinity Diagram

Affinity Diagram clusters qualitative data points into themes and insight statements. Use it when synthesising across multiple sessions or sources to create a structured hierarchy with supporting evidence.
Data
2.1K335
🗂️
2w ago

Card Sort Analysis

Card Sort Analysis analyzes open or closed card sort results into a proposed grouping and label set. Use it after running a sort study to inform navigation and content organization.
Frontend
2.1K335
🧩
2w ago

Component Spec

Component Spec specifies one component's props, states, variants, accessibility, and usage rules. Use when defining a library component.
Frontend
2.1K335
💬
2w ago

Design Critique

Design Critique facilitates structured team critique sessions, guiding framing, feedback rules, and actionable outcomes. Use it when running a session with people in the room to keep feedback constructive and aligned.
Frontend
2.1K335
🔍
2w ago

Design Debt Audit

Design Debt Audit inventories and prioritizes accumulated design inconsistencies across a product so teams can plan remediation. Use it before redesigns or when UI drift, accessibility gaps, and structural debt have built up.
Frontend
2.1K335
📊
2w ago

Design Impact Reporting

Design Impact Reporting measures and communicates design's contribution to business and user outcomes in stakeholder language. Use it when reporting results upward to leadership or cross-functional partners.
Data
2.1K335
📋
2w ago

Design QA Checklist

Design QA Checklist builds a systematic checklist for verifying that a build matches the design specification, used at implementation review.
Quality
2.1K335
🚦
2w ago

Design Review Process

Design Review Process establishes review gates, criteria, checkpoints, and approval flows so design work ships with consistent quality. Use it when work ships without consistent review; for individual sessions, use design-critique.
Frontend
2.1K335
🧭
2w ago

Design Sprint Plan

Design Sprint Plan plans and facilitates structured design sprints that take teams from challenge framing to tested prototype in a focused week. Use it for classic 5-day, mini, remote, or discovery sprints when you need to compress discovery and alignment into days.
Frontend
2.1K335
🏛️
2w ago

Design System Governance

Design System Governance defines ownership, contribution, versioning, deprecation, and breaking-change processes so multiple teams can evolve a design system without fragmentation. Use it to establish or refine how changes are proposed, reviewed, and released.
Frontend
2.1K335
🎨
2w ago

Design Token

Design Token defines and organises design tokens for color, spacing, type, and elevation with naming and usage rules. Use it when establishing the token layer.
Frontend
2.1K335
📓
2w ago

Diary Study Plan

Diary Study Plan designs a longitudinal diary study with prompts, cadence, duration, participant criteria, and an analysis framework. Use it when user behavior unfolds over days or weeks and you need in-context, in-the-moment data.
Frontend
2.1K335
🗺️
2w ago

Empathy Map

Empathy Map builds a Says, Thinks, Does, Feels map for one user or segment, used to share user understanding quickly. It helps align teams around synthesized user research and identify goals, pain points, and design insights.
Frontend
2.1K335
📋
2w ago

Handoff Spec

Handoff Spec writes implementation handoffs with measurements, behaviors, assets, states, and edge cases so developers can build a design accurately.
Frontend
2.1K335
📝
2w ago

Interview Script

Interview Script creates a structured user interview script for qualitative research, covering introduction, warm-up, core exploration, specific scenarios, and wrap-up. Use it before running interviews to get non-leading, open-ended questions, probing techniques, and facilitator notes.
Writing
2.1K335
🎯
2w ago

Jobs to Be Done

Jobs to Be Done maps functional, emotional, and social jobs with outcome expectations to understand user motivations. Use it to reframe decisions around motivation rather than features.
Frontend
2.1K335
🗺️
2w ago

Journey Map

Journey Map maps one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use it when improving an existing experience or analyzing a user journey.
Frontend
2.1K335
📚
2w ago

Research Repository

Research Repository helps teams organize UX research findings into tagged, searchable insights so past studies are reused and evidence accumulates. Use it to design tagging conventions and repository workflows.
Data
2.1K335
🎙️
2w ago

Summarize Interview

Summarize Interview turns one interview transcript into themes, supporting quotes, and action items. Use it immediately after a user interview to extract structured insights for stakeholders.
Data
2.1K335
📋
2w ago

Survey Design

Survey Design creates unbiased survey instruments with well-formed questions, appropriate scales, and sound sampling so quantitative data can be trusted. Use it when you need to measure attitudes, prevalence, or change at scale.
Data
2.1K335
👥
2w ago

Team Workflow

Team Workflow designs a design team's operating rhythm covering task management, collaboration rituals, and tooling. Use it when a team's day-to-day cadence needs structure.
Automation
2.1K335
📋
2w ago

Usability Test Plan

Usability Test Plan designs a comprehensive usability study, including research questions, methodology, participant criteria, task metrics, and facilitation guide. Use when planning a usability test for designs or prototypes, especially before writing test scenarios.
Quality
2.1K335
👤
2w ago

User Persona

User Persona builds research-grounded personas with goals, frustrations, and behavioral patterns. Use it when product or UX decisions need a consistent user reference.
Frontend
2.1K335
🗂️
2w ago

Version Control Strategy

Version Control Strategy defines how to version design files, component libraries, design tokens, and assets with branching, naming, and changelog practices. Use it when design file history is chaotic or teams need consistent collaboration and release workflows.
Frontend
2.1K335