Not in the top 1,000 by GitHub stars
cuellarfr/design-skills
UX and design skills for Claude Code — research, critique, accessibility, journey mapping and more.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/accessibility-audit/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
skills/design-critique/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
skills/design-elevation/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
skills/design-ops/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
skills/design-systems/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
skills/interaction-design/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
skills/journey-mapping/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
skills/ux-research/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
skills/ux-strategy/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
skills/ux-writing/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
7e25e66e87f6 → 7e25e66e87f6
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 7e25e66e87f6
No earlier version was observed for comparison.
View on GitHubAdd to my skills
Verified commit 7e25e66e87f64f9d3dea22198f9e29937e7c48f5
git clone --filter=blob:none --no-checkout https://github.com/cuellarfr/design-skills.git .hotskills/cuellarfr-design-skills && git -C .hotskills/cuellarfr-design-skills checkout --detach 7e25e66e87f64f9d3dea22198f9e29937e7c48f5
# Copy each selected skill directory from .hotskills/cuellarfr-design-skills into .claude/skills/<skill-name>/118GitHub stars
2stars in 7 days
10skills in this repository
0commits in 30 days
Heat
4.4- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
- accessibility-audit
skills/accessibility-audit - design-critique
skills/design-critique - design-elevation
skills/design-elevation - design-ops
skills/design-ops - design-systems
skills/design-systems - interaction-design
skills/interaction-design - journey-mapping
skills/journey-mapping - ux-research
skills/ux-research - ux-strategy
skills/ux-strategy - ux-writing
skills/ux-writing
How it works
accessibility-audit
When your agent uses it
Conduct accessibility audits against WCAG 2.2 guidelines. Evaluate pages, components, and flows for conformance at A, AA, and AAA levels. Identify issues, assess severity, provide code fixes, and generate audit reports. Covers automated testing, manual testing, keyboard navigation, screen reader compatibility, color contrast, and semantic HTML.
What it loads into context
Frontmatter
75 tokensAlways available to the agent
SKILL.md
3,315 tokensWhen the skill is activated
Reference documents
19,141 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core Principle
- WCAG Conformance Levels
- How to Run an Accessibility Audit
- Severity Scoring
- The 80/20: Most Common Issues
- Semantic HTML: The Foundation
- Quick Audit Checklist (For Code Reviews)
- Reference Files
- Templates
- Examples
Files
../../.claude-plugin/marketplace.jsonasset993 bytes../../.claude-plugin/plugin.jsonasset697 bytesSKILL.mdcore13,456 bytesexamples/audit-walkthrough.mddoc11,169 bytesexamples/quick-wins.mddoc5,620 bytesreferences/common-issues-and-fixes.mddoc12,648 bytesreferences/testing-tools-and-techniques.mddoc14,221 bytesreferences/wcag-checklist.mddoc12,111 bytestemplates/accessibility-rules-file.mddoc5,531 bytestemplates/audit-report-template.mddoc5,472 bytestemplates/quick-checklist-template.mddoc2,937 bytes
Read SKILL.md
# Accessibility Audit
You are an expert in web accessibility and WCAG 2.2 conformance. You help teams audit digital products, identify barriers, write compliant code, and build inclusive experiences.
Your work is grounded in WCAG 2.2, WebAIM guidelines, and the four principles of accessibility: Perceivable, Operable, Understandable, and Robust (POUR).
## Core Principle
Accessibility is not a feature — it is a baseline quality requirement. Good accessibility benefits all users, not just those with disabilities. Every interaction you design or code should work for people using keyboards, screen readers, voice control, switch devices, and magnification.
---
## WCAG Conformance Levels
design-critique
When your agent uses it
Evaluate UI designs against usability heuristics, UX laws, interaction patterns, interaction design principles, information architecture, and content quality. Conduct heuristic evaluations, structured design critiques, pattern-based reviews, posture analysis, excise audits, IA evaluations, and UX writing reviews. Provides specific, actionable feedback grounded in established principles rather than subjective opinion.
What it loads into context
Frontmatter
75 tokensAlways available to the agent
SKILL.md
7,198 tokensWhen the skill is activated
Reference documents
21,121 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core Principle
- The Critique Framework
- Nielsen's 10 Usability Heuristics
- UX Laws Quick Reference
- Interaction Design Principles
- Giving Actionable Feedback
- The "Krug Test" — Five Usability Checks
- Information Architecture Evaluation
- Content & UX Writing Evaluation
- Common Design Problems
- Quick Critique Checklist
- Reference Files
- Templates
- Examples
Files
SKILL.mdcore33,308 bytesexamples/common-design-problems.mddoc8,924 bytesexamples/critique-walkthrough.mddoc9,788 bytesexamples/pattern-selection-walkthrough.mddoc10,134 bytesreferences/design-patterns-catalog.mddoc22,145 bytesreferences/heuristics-and-laws.mddoc13,484 bytesreferences/interaction-design-principles.mddoc14,791 bytesreferences/visual-design-principles.mddoc8,820 bytestemplates/design-critique-template.mddoc2,341 bytestemplates/heuristic-evaluation-template.mddoc3,139 bytes
Read SKILL.md
# Design Critique & Evaluation
You are an expert in evaluating digital product designs. You critique interfaces using established heuristics, UX laws, interaction patterns, and interaction design principles — never personal preference. Every piece of feedback you give is grounded in a named principle and includes a specific, actionable recommendation.
Your work draws from Nielsen's 10 usability heuristics, Laws of UX (lawsofux.com), established usability principles, interaction design frameworks, and common interaction design patterns.
## Core Principle
Design critique is not about taste — it's about effectiveness. The question is never "Do I like this?" but always "Does this work for the user trying to accomplish their goal?" Ground every observation in evidence, principles, or research. When you don't know, say "test this" rather than guessing.
---
## The Critique Framework
design-elevation
When your agent uses it
Comprehensive design elevation system that automatically transforms functional visual outputs into polished, professional designs. Use when creating ANY visual output including presentations (pptx), spreadsheets (xlsx), dashboards, reports, HTML artifacts, PDFs, web pages, or data visualizations. Applies systematic design thinking grounded in Tailwind CSS as the canonical design token system. Structures decisions through functional patterns (what users interact with) and perceptual patterns (how the design feels), following Alla Kholmatova's design systems framework. Triggers on ALL requests for visual content creation, ensuring outputs look hand-crafted rather than template-based.
What it loads into context
Frontmatter
125 tokensAlways available to the agent
SKILL.md
2,558 tokensWhen the skill is activated
Reference documents
72,095 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Design Philosophy
- Activation Protocol
- Functional Patterns by Output Type
- Perceptual Patterns
- Design Exemplars
- Critical Design Moves (Quick Reference)
- Resource Loading Priority
- Output Standards
- Silent Execution
Files
SKILL.mdcore10,794 bytesSKILL.mdcore10,794 bytesreferences/carbon-design-system.mddoc18,403 bytesreferences/color-systems.mddoc10,920 bytesreferences/data-visualization.mddoc17,799 bytesreferences/design-exemplars.mddoc12,165 bytesreferences/design-interrogation.mddoc7,490 bytesreferences/elevation-protocol.mddoc10,112 bytesreferences/grid-systems.mddoc9,108 bytesreferences/lightning-design-system.mddoc39,502 bytesreferences/polaris-design-system.mddoc41,023 bytesreferences/spacing-systems.mddoc9,906 bytesreferences/spectrum-design-system.mddoc32,546 bytesreferences/technique-catalog.mddoc11,665 bytesreferences/typography-scales.mddoc7,944 bytes
Read SKILL.md
# Design Elevation System
This skill transforms functional visual outputs into polished, professional designs by applying systematic design thinking and refinement protocols.
## Design Philosophy
Follow Alla Kholmatova's design systems framework: every design decision is either a **functional pattern** (what users interact with — structure, layout, components) or a **perceptual pattern** (how it feels — color, typography, spacing, motion). Both layers must be intentional.
### Canonical Design Tokens: Tailwind CSS
All design decisions should map to **Tailwind CSS** as the shared design language. This means:
- Colors from Tailwind's palette (gray, blue, emerald, amber, rose, violet, etc.)
- Spacing from Tailwind's scale (1 = 0.25rem/4px, 2 = 0.5rem/8px, 4 = 1rem/16px, etc.)
- Typography from Tailwind's type scale (text-xs through text-9xl)design-ops
When your agent uses it
Run design sprints, manage handoff, establish team rituals, documentation standards, and design QA processes. Covers the operational side of design — how teams organize work, collaborate with engineering, and ship quality.
What it loads into context
Frontmatter
49 tokensAlways available to the agent
SKILL.md
4,076 tokensWhen the skill is activated
Reference documents
23,661 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Design Sprints
- Design-to-Development Handoff
- Team Rituals and Cadences
- Documentation Standards
- Design QA
- Process Metrics
- Scaled-Down Operations for Lean Teams
- Common Mistakes
Files
SKILL.mdcore18,359 bytesSKILL.mdcore18,359 bytesSKILL.mdcore18,359 bytesexamples/design-sprint-walkthrough.mddoc15,447 bytesexamples/handoff-walkthrough.mddoc16,581 bytesreferences/design-qa.mddoc12,288 bytesreferences/design-sprints.mddoc13,816 bytesreferences/documentation-standards.mddoc9,293 bytesreferences/handoff-process.mddoc9,840 bytesreferences/team-rituals.mddoc10,577 bytestemplates/design-sprint-template.mddoc5,665 bytestemplates/handoff-checklist-template.mddoc4,338 bytes
Read SKILL.md
# Design Ops & Handoff
Operational processes that make design teams effective — sprints, handoff, rituals, documentation, and quality assurance.
---
## Design Sprints
A 5-day process for solving big problems and testing ideas before committing engineering resources. Based on Jake Knapp's Sprint methodology developed at Google Ventures.
### When to Sprint
| Signal | Sprint Is Right | Sprint Is Wrong |
|--------|----------------|-----------------|design-systems
When your agent uses it
Build, document, and maintain design systems with design tokens, component specifications, pattern libraries, naming conventions, and governance processes. Conduct system audits, define component hierarchies, and establish shared design languages.
What it loads into context
Frontmatter
49 tokensAlways available to the agent
SKILL.md
2,780 tokensWhen the skill is activated
Reference documents
21,295 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core Concepts
- When to Build a Design System
- The Interface Inventory (5-Step Audit)
- Component Specification
- Naming Patterns
- Governance
- System Maturity Levels
- Common Mistakes
- Reference Files
- Templates
- Examples
Files
SKILL.mdcore13,345 bytesexamples/component-spec-walkthrough.mddoc11,786 bytesexamples/system-audit-walkthrough.mddoc7,201 bytesreferences/component-hierarchy.mddoc7,847 bytesreferences/design-tokens.mddoc9,431 bytesreferences/governance-and-maintenance.mddoc9,952 bytesreferences/pattern-documentation.mddoc8,884 bytesreferences/perceptual-patterns.mddoc11,164 bytestemplates/component-spec-template.mddoc4,203 bytestemplates/design-system-audit-template.mddoc5,300 bytestemplates/token-architecture-template.mddoc7,908 bytes
Read SKILL.md
# Design Systems
You are an expert in design systems — the interconnected patterns and shared practices that bring coherence to digital products at scale. Your recommendations are grounded in Brad Frost's Atomic Design methodology, Alla Kholmatova's pattern-driven approach, Nathan Curtis's system governance models, the W3C Design Tokens specification, and real-world systems including Material Design 3, Polaris (Shopify), Carbon (IBM), and Spectrum (Adobe).
*A design system is a product that serves other products. It is never "done." The measure of a good system is not its comprehensiveness on day one — it is whether it is still useful, still used, and still evolving a year later.*
---
## Core Concepts
### Two Types of Patterns
Every design system is built from two inseparable layers (Kholmatova):
interaction-design
When your agent uses it
Design meaningful interactions, microinteractions, animations, state machines, gesture patterns, error prevention, and product behavior. Specify how products respond to user input across all states and contexts using established interaction design principles.
What it loads into context
Frontmatter
48 tokensAlways available to the agent
SKILL.md
4,573 tokensWhen the skill is activated
Reference documents
16,852 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- The Microinteraction Framework
- Product Posture
- Orchestration and Flow
- Narrative Structure in Product Design
- Excise
- State Design
- Responsiveness Thresholds
- Gesture Patterns
- Common Mistakes
- Reference Files
- Templates
- Examples
Files
SKILL.mdcore21,863 bytesSKILL.mdcore21,863 bytesexamples/interaction-audit-walkthrough.mddoc9,860 bytesexamples/microinteraction-walkthrough.mddoc7,798 bytesreferences/error-prevention.mddoc9,606 bytesreferences/microinteractions.mddoc10,355 bytesreferences/motion-principles.mddoc8,334 bytesreferences/product-behavior.mddoc9,372 bytesreferences/state-and-transitions.mddoc8,885 bytestemplates/microinteraction-spec-template.mddoc4,497 bytestemplates/state-inventory-template.mddoc4,270 bytes
Read SKILL.md
# Interaction Design
You are an expert in interaction design — the discipline that defines how products behave in response to human input. Your recommendations are grounded in Dan Saffer's Microinteractions (trigger-rules-feedback-loops framework), Alan Cooper's About Face (product posture, perpetual intermediates, orchestration, excise), Donna Lichaw's The User's Journey (narrative arc, storymapping, peak-end design), the 12 Principles of Animation adapted for UI, David Harel's statecharts for UI state modeling, and motion guidelines from Material Design 3 and Apple HIG.
*Interaction design is the design of behavior. A product's visual appearance is what users see; its interaction design is what they experience. The gap between a product people tolerate and one they love is almost always in the quality of its interactions.*
---
## The Microinteraction Framework
Every interaction — from toggling a switch to submitting a form — consists of four parts (Saffer):
| Part | Definition | Key Question |
|------|-----------|-------------|journey-mapping
When your agent uses it
Create customer journey maps, service blueprints, experience maps, empathy maps, and other alignment diagrams. Guides diagram type selection, content structure, illustration syntax, and alignment workshops.
What it loads into context
Frontmatter
43 tokensAlways available to the agent
SKILL.md
5,372 tokensWhen the skill is activated
Reference documents
22,981 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core Principle
- Diagram Types: When to Use What
- The Mapping Process
- Customer Journey Map: Core Structure
- Service Blueprint: Core Structure
- Empathy Map: Core Structure
- Types of Service Experience
- Moments of Truth
- Time as a Design Object
- Strategic Use of Alignment Diagrams
- Current State vs. Future State Mapping
- Flow Diagrams and Alignment Diagrams: When to Use What
- Common Mistakes
- Quick Reference: Content Checklist
- Reference Files
- Templates
- Examples
Files
SKILL.mdcore25,617 bytesSKILL.mdcore25,617 bytesexamples/cjm-walkthrough.mddoc11,114 bytesexamples/diagram-selection-scenarios.mddoc10,384 bytesreferences/alignment-workshops.mddoc12,115 bytesreferences/customer-journey-maps.mddoc11,751 bytesreferences/experience-maps-and-models.mddoc17,487 bytesreferences/flow-diagramming-visual-vocabulary.mddoc13,863 bytesreferences/service-blueprints.mddoc16,998 bytestemplates/customer-journey-map-template.mddoc3,946 bytestemplates/empathy-map-template.mddoc1,896 bytestemplates/service-blueprint-template.mddoc3,656 bytes
Read SKILL.md
# Journey Mapping & Service Design
You are an expert in alignment diagrams — the family of visualizations that align an individual's experience with an organization's operations. You help teams create journey maps, service blueprints, experience maps, empathy maps, mental model diagrams, and ecosystem models.
Your work is grounded in established alignment diagram methodology and service design practice, including Polaine, Løvlie & Reason's service design framework.
## Core Principle
Alignment diagrams are not deliverables — they are **conversation tools**. A diagram that sits in a drawer failed. A rough diagram that sparks alignment succeeded. Optimize for team understanding, not visual polish.
---
## Diagram Types: When to Use What
ux-research
When your agent uses it
Plan, conduct, and analyze UX research using proven methodologies. Use when planning user research, writing interview scripts, creating test plans, recruiting participants, analyzing qualitative data, or synthesizing findings into actionable insights. Covers generative, evaluative, and continuous discovery research with specific frameworks, scoring rubrics, and templates.
What it loads into context
Frontmatter
71 tokensAlways available to the agent
SKILL.md
2,838 tokensWhen the skill is activated
Reference documents
30,780 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- When to Use This Skill
- Core Principle
- Research Types
- The Research Process
- Continuous Discovery
- Common Mistakes to Avoid
- Quick Reference
- Resources
Files
SKILL.mdcore13,677 bytesSKILL.mdcore13,677 bytesSKILL.mdcore13,677 bytesexamples/interview-to-insights.mddoc10,565 bytesexamples/method-selection-scenarios.mddoc7,596 bytesreferences/analysis-synthesis.mddoc13,284 bytesreferences/continuous-discovery.mddoc9,191 bytesreferences/interviewing-guide.mddoc11,829 bytesreferences/research-methods-catalog.mddoc18,636 bytesreferences/usability-testing-guide.mddoc19,217 bytesreferences/workshop-methods.mddoc18,502 bytestemplates/findings-report-template.mddoc3,645 bytestemplates/interview-guide-template.mddoc2,918 bytestemplates/persona-template.mddoc7,104 bytestemplates/research-plan-template.mddoc3,341 bytestemplates/screener-template.mddoc4,477 bytestemplates/usability-test-plan-template.mddoc4,550 bytes
Read SKILL.md
# UX Research
Plan, conduct, and analyze user research that produces actionable insights for product design. This skill provides frameworks, methods, and practical guidance for every stage of the research process — from defining the right question to presenting findings that drive decisions.
## When to Use This Skill
Use this skill when:
- Planning a research study (choosing methods, defining scope, writing a plan)
- Writing interview scripts or discussion guides
- Creating usability test plans with tasks and success metrics
- Recruiting participants and writing screener surveys
- Analyzing qualitative data (affinity diagrams, thematic analysis)
- Synthesizing research into personas, journey maps, or opportunity maps
- Setting up continuous discovery practices (weekly interviews, OSTs)ux-strategy
When your agent uses it
Connect design decisions to business outcomes through competitive analysis, opportunity mapping, Jobs to Be Done, outcome-driven discovery, value proposition design, and UX metrics. Shape product direction with strategic frameworks grounded in evidence.
What it loads into context
Frontmatter
48 tokensAlways available to the agent
SKILL.md
4,917 tokensWhen the skill is activated
Reference documents
22,088 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core Framework
- Outcomes Over Outputs
- Opportunity Mapping
- Jobs to Be Done (JTBD)
- Competitive Analysis
- Validating Strategy
- UX Metrics
- Strategy Process (End-to-End)
- Ethical and Responsible Strategy
- Common Mistakes
- Reference Files
- Templates
- Examples
Files
SKILL.mdcore23,486 bytesSKILL.mdcore23,486 bytesexamples/competitive-analysis-walkthrough.mddoc10,822 bytesexamples/strategy-walkthrough.mddoc11,880 bytesreferences/competitive-analysis.mddoc9,446 bytesreferences/jobs-to-be-done.mddoc11,130 bytesreferences/metrics-and-measurement.mddoc9,804 bytesreferences/outcomes-and-opportunities.mddoc10,756 bytesreferences/value-proposition.mddoc11,257 bytestemplates/competitive-analysis-template.mddoc5,388 bytestemplates/competitive-brief-template.mddoc4,892 bytestemplates/opportunity-solution-tree-template.mddoc5,355 bytestemplates/strategy-brief-template.mddoc5,511 bytes
Read SKILL.md
# UX Strategy
You are an expert in UX strategy — the discipline that connects design decisions to business outcomes and customer value. Your recommendations are grounded in Teresa Torres's Continuous Discovery Habits (Opportunity Solution Trees, outcome-driven discovery), Jim Kalbach's Jobs to Be Done Playbook (job mapping, desired outcomes, switch analysis), Jaime Levy's UX Strategy (competitive analysis, value innovation, funnel design), Jeff Gothelf and Josh Seiden's Lean UX (hypothesis-driven design, outcomes over outputs), Victor Papanek's Design for the Real World (ethical responsibility, shared value, designing for underserved populations), and Google's HEART framework for UX metrics.
*UX strategy is the high-level plan to achieve business goals under conditions of uncertainty. It precedes wireframes, visual design, and development. Without it, teams build features no one needs. With it, every design decision traces back to a reason.*
---
## Core Framework
UX strategy sits at the intersection of four concerns:
| Concern | Question | Key Tool |
|---------|----------|----------|ux-writing
When your agent uses it
Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
4,632 tokensWhen the skill is activated
Reference documents
15,647 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- When to Use This Skill
- Core UX Writing Principles
- UX Text Patterns
- Formatting & Style Conventions
- Voice and Tone
- Editing Process
- Workflow
- Accessibility in UX Writing
- UX Text Benchmarks
- Common Mistakes to Avoid
- Quick Reference
- Style references
- Resources
Files
SKILL.mdcore20,045 bytesdocs/figma-integration.mddoc10,206 bytesexamples/real-world-improvements.mddoc7,455 bytesreferences/accessibility-guidelines.mddoc11,570 bytesreferences/content-usability-checklist.mddoc4,888 bytesreferences/patterns-detailed.mddoc10,190 bytesreferences/voice-chart-template.mddoc4,029 bytestemplates/empty-state-template.mddoc5,214 bytestemplates/error-message-template.mddoc3,219 bytestemplates/onboarding-flow-template.mddoc7,249 bytes
Read SKILL.md
# UX Writing
Write clear, concise, user-centered interface copy (UX text/microcopy) for digital products and experiences. This skill provides frameworks, patterns, and best practices for creating text that helps users accomplish their goals.
## When to Use This Skill
Use this skill when:
- Writing interface copy (buttons, labels, titles, messages, forms)
- Editing existing UX text for clarity and effectiveness
- Creating error messages, notifications, or success messages
- Designing conversational flows or onboarding experiences
- Establishing voice and tone for a product
- Auditing product content for consistency and usability
Skills included
- accessibility-audit
- design-critique
- design-elevation
- design-ops
- design-systems
- interaction-design
- journey-mapping
- ux-research
- ux-strategy
- ux-writing
Repository facts
- License
- MIT
- Created
- Mar 19, 2026
- Last pushed
- Sep 30, 2026
- Forks
- 9
- Open issues
- 0
- Project activity
- Active
Before you install
Instructions onlyAutomated signals, not a guarantee
Checked Nov 7, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 8 notes
skills/design-elevation/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/design-ops/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/design-ops/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/interaction-design/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/journey-mapping/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/ux-research/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/ux-research/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/ux-strategy/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- 39 network referencesin 9 files: ux-writing/references/accessibility-guidelines.md:370 .claude-plugin/marketplace.json:3 ux-writing/docs/figma-integration.md:50 and 6 more
- No hidden or obfuscated text
- 2 instruction override signalsin 1 file: interaction-design/references/microinteractions.md:157
- No executable scripts
- No access to secrets
- No requests to vote in Hot
Show all 41 signals by file
.claude-plugin/marketplace.json
- Network accessline 3
"owner": { "name": "Carlos Cuellar", "url": "https://github.com/cuellarfr" - Network accessline 4
"name": "Carlos Cuellar", "url": "https://github.com/cuellarfr" }, - Network accessline 5
"url": "https://github.com/cuellarfr" - Network accessline 15
"name": "Carlos Cuellar" }, "homepage": "https://cuellarfr.github.io/design-skills/", - Network accessline 16
}, "homepage": "https://cuellarfr.github.io/design-skills/", "repository": "https://github.com/cuellarfr/design-skills", - Network accessline 17
"homepage": "https://cuellarfr.github.io/design-skills/", - Network accessline 18
"repository": "https://github.com/cuellarfr/design-skills",
.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "Carlos Cuellar", "url": "https://github.com/cuellarfr" - Network accessline 6
"name": "Carlos Cuellar", "url": "https://github.com/cuellarfr" }, - Network accessline 7
"url": "https://github.com/cuellarfr" - Network accessline 8
}, "homepage": "https://cuellarfr.github.io/design-skills/", "repository": "https://github.com/cuellarfr/design-skills", - Network accessline 9
"homepage": "https://cuellarfr.github.io/design-skills/", - Network accessline 10
"repository": "https://github.com/cuellarfr/design-skills",
skills/accessibility-audit/templates/audit-report-template.md
skills/design-elevation/references/carbon-design-system.md
- Network accessline 5
Source: [carbondesignsystem.com](https://carbondesignsystem.com) and [@carbon/themes](https://github.com/carbon-design-system/carbon) - Network accessline 40
<link href="https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@300;400;500;600;700&family=IBM+Plex+Mono:wght@400;600&display=swap" rel="stylesheet">
skills/design-elevation/references/lightning-design-system.md
- Network accessline 5
Source: [lightningdesignsystem.com](https://www.lightningdesignsystem.com) and [@salesforce-ux/design-system](https://github.com/salesforce-ux/design-system)
skills/design-elevation/references/polaris-design-system.md
- Network accessline 5
Source: [polaris.shopify.com](https://polaris.shopify.com) and [@shopify/polaris](https://github.com/Shopify/polaris)
skills/design-elevation/references/spectrum-design-system.md
- Network accessline 5
Source: [spectrum.adobe.com](https://spectrum.adobe.com) and [@adobe/spectrum-tokens](https://github.com/adobe/spectrum-tokens), [@spectrum-css](https://github.com/adobe/spectrum-css) - Network accessline 41
<link href="https://fonts.googleapis.com/css2?family=Source+Sans+Pro:wght@300;400;600;700&display=swap" rel="stylesheet">
skills/interaction-design/references/microinteractions.md
- Instruction override signalline 157
| Onboarding walkthrough | "Tip of the day" (dismissible) | Nothing — user knows the product | | Default view with essential options | "Show advanced" toggle remembered | Advanced always visible (if user toggled it) | | Confirmation dialogs - Instruction override signalline 159
| Confirmation dialogs for destructive actions | "Don't ask again" checkbox | Skip confirmation, rely on Undo |
skills/ux-writing/docs/figma-integration.md
- Network accessline 50
claude mcp add --transport http figma https://mcp.figma.com/mcp - Network accessline 104
claude mcp add --transport http figma-desktop http://127.0.0.1:3845/mcp - Network accessline 143
Review the UX copy in this login screen: https://www.figma.com/file/abc123/Design?node-id=123-456 - Network accessline 144
https://www.figma.com/file/abc123/Design?node-id=123-456 - Network accessline 167
Review all UX copy in this onboarding flow: https://www.figma.com/file/abc123/Onboarding-Flow - Network accessline 168
https://www.figma.com/file/abc123/Onboarding-Flow - Network accessline 408
- **Figma MCP Documentation**: [developers.figma.com/docs/figma-mcp-server](https://developers.figma.com/docs/figma-mcp-server/)
skills/ux-writing/references/accessibility-guidelines.md
- Network accessline 370
### WCAG Guidelines - [WCAG 2.1 Quick Reference](https://www.w3.org/WAI/WCAG21/quickref/) - Network accessline 371
- [WCAG 2.1 Quick Reference](https://www.w3.org/WAI/WCAG21/quickref/) - Network accessline 372
- [Understanding WCAG Success Criteria](https://www.w3.org/WAI/WCAG21/Understanding/) - Network accessline 374
### Testing Tools - [WAVE Web Accessibility Evaluation Tool](https://wave.webaim.org/) - Network accessline 375
- [WAVE Web Accessibility Evaluation Tool](https://wave.webaim.org/) - Network accessline 376
- [Hemingway Editor](http://hemingwayapp.com/) - Network accessline 377
- [WebAIM Contrast Checker](https://webaim.org/resources/contrastchecker/) - Network accessline 379
### Plain Language - [PlainLanguage.gov](https://www.plainlanguage.gov/) - Network accessline 380
- [PlainLanguage.gov](https://www.plainlanguage.gov/) - Network accessline 381
- [Readable.com](https://readable.com/)
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
Signal confidence: 28 facts
- Network access in prose of documentationaccessibility-audit/templates/audit-report-template.md:197Low confidence
- Network access in prose of documentationaccessibility-audit/templates/audit-report-template.md:198Low confidence
- Network access in prose of documentationaccessibility-audit/templates/audit-report-template.md:199Low confidence
- Network access in prose of documentationdesign-elevation/references/carbon-design-system.md:5Low confidence
- Network access in code of documentationdesign-elevation/references/carbon-design-system.md:40Low confidence
- Network access in prose of documentationdesign-elevation/references/lightning-design-system.md:5Low confidence
- Network access in prose of documentationdesign-elevation/references/polaris-design-system.md:5Low confidence
- Network access in prose of documentationdesign-elevation/references/spectrum-design-system.md:5Low confidence
- Network access in code of documentationdesign-elevation/references/spectrum-design-system.md:41Low confidence
- Instruction override signal in prose of documentationinteraction-design/references/microinteractions.md:157Low confidence
- Instruction override signal in prose of documentationinteraction-design/references/microinteractions.md:159Low confidence
- Network access in code of documentationux-writing/docs/figma-integration.md:50Low confidence
- Network access in code of documentationux-writing/docs/figma-integration.md:104Low confidence
- Network access in code of documentationux-writing/docs/figma-integration.md:143Low confidence
- Network access in code of documentationux-writing/docs/figma-integration.md:144Low confidence
- Network access in code of documentationux-writing/docs/figma-integration.md:167Low confidence
- Network access in code of documentationux-writing/docs/figma-integration.md:168Low confidence
- Network access in prose of documentationux-writing/docs/figma-integration.md:408Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:370Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:371Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:372Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:374Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:375Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:376Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:377Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:379Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:380Low confidence
- Network access in prose of documentationux-writing/references/accessibility-guidelines.md:381Low confidence
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md skills/accessibility-audit/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/accessibility-audit/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/accessibility-audit/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/accessibility-audit/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/accessibility-audit/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.
