ux-skills

In the author's own words, from each skill's SKILL.md.

• accessibility

  Review UX design intent and available implementation evidence for accessibility barriers, inclusive interaction, WCAG or Section 508 requirements, keyboard and focus behavior, semantics, dynamic announcements, content, motion, zoom/reflow, and recovery. Use when a designer asks for an accessibility review or needs accessibility behavior defined before engineering handoff.

  skills/accessibility/SKILL.md on GitHub (opens in a new tab)

• blindspots

  Find important users, contexts, constraints, dependencies, consequences, and conditions that a design discussion has not considered at all. Use when a designer asks "what am I missing?", wants edge perspectives beyond UI states, or needs a pre-review scan for overlooked experience risks.

  skills/blindspots/SKILL.md on GitHub (opens in a new tab)

• challenge

  Interrogate a UX idea, requirement, flow, feature, or design direction before execution. Use when a designer asks to be challenged, wants assumptions exposed, wants a red-team review of the premise, or needs hard questions that test whether the proposed work should exist at all.

  skills/challenge/SKILL.md on GitHub (opens in a new tab)

• clear

  Rewrite UX, product, research, handoff, ticket, or engineering-facing content so it reads like a capable human practitioner wrote it. Use when generated or existing content is bloated, robotic, unclear, over-structured, audience-blind, or sounds like AI while preserving meaning, evidence strength, and uncertainty.

  skills/clear/SKILL.md on GitHub (opens in a new tab)

• content

  Review and improve product UX content including labels, instructions, errors, empty states, confirmations, terminology, and content timing. Use when a designer asks whether UI copy is clear, consistent, accessible, actionable, appropriately human, or aligned with the product's established language.

  skills/content/SKILL.md on GitHub (opens in a new tab)

• critique

  Review and compare UX designs, flows, prototypes, specifications, or implementations against user goals, evidence, interaction behavior, accessibility, design-system fit, content, and engineering intent. Use when a designer asks for critique, comparison, tough feedback, review before approval, or wants to check whether implementation preserved the intended experience.

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

• decision

  Recover or preserve consequential UX and architecture rationale. Use when a designer asks why something was designed a certain way, whether a choice deserves an ADR/design decision record, or wants to capture context, evidence, alternatives, rationale, consequences, and status without documenting trivial changes.

  skills/decision/SKILL.md on GitHub (opens in a new tab)

• frame

  Turn a feature request, stakeholder request, idea, complaint, or vague design assignment into a clear UX problem frame with user outcome, evidence, constraints, assumptions, unknowns, and success signals. Use before solutioning when the real problem or reason for the work is unclear.

  skills/frame/SKILL.md on GitHub (opens in a new tab)

• handoff

  Prepare UX work for engineering by preserving user intent, behavior, states, design-system usage, accessibility requirements, dependencies, acceptance behavior, and unresolved questions. Use when a designer says "get this ready for engineering", needs a handoff, behavioral contract, implementation-ready ticket content, or wants to stop engineering from guessing.

  skills/handoff/SKILL.md on GitHub (opens in a new tab)

• pr

  Create a high-quality pull request description for UX-related implementation that explains why the change exists, what behavior changed, design-system usage, states, accessibility, testing, risks, and what reviewers should inspect. Use when design or design-engineering work is ready to become a PR.

  skills/pr/SKILL.md on GitHub (opens in a new tab)

• ripple

  Trace what else a UX, flow, component, content, or design-system change could affect. Use when a designer asks "if we change this, what else moves?", "what else could this affect?", or wants to understand downstream UX impact before committing to a change.

  skills/ripple/SKILL.md on GitHub (opens in a new tab)

• setup-ux

  Set up or refresh UX Skills for a new or existing project by capturing product intent, learning users and evidence, the design system, engineering environment, accessibility expectations, terminology, and consequential decisions. Use only when the user explicitly asks to set up, initialize, connect, learn, or refresh UX Skills/project context; do not activate during ordinary UX work.

  skills/setup-ux/SKILL.md on GitHub (opens in a new tab)

• state-sweep

  Find missing interface and service states such as loading, empty, partial, permission, timeout, stale data, validation, failure, interruption, and recovery. Use when a designer asks what states or edge cases are missing from a screen, component, journey, or feature.

  skills/state-sweep/SKILL.md on GitHub (opens in a new tab)

• system-fit

  Decide whether a UX need should reuse, compose, extend, or create a design-system component or pattern. Use when a designer asks whether something needs a new component, how a design fits the current system, or what design-system contribution a feature should make.

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

• user-grounding

  Ground UX work in actual users and evidence when who the design is for, their goals or context, or the strength of user knowledge is materially uncertain. Use when a designer asks who this is for, whether personas are useful, what research is needed, what existing research says, or when a decision depends on unsupported assumptions about users. Do not activate merely because a UX task involves us…

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

No skill matches that filter.

Similar skills

• awesome-design-skillsby bergside List of 67 awesome DESIGN.md and SKILL.md design skill files for agentic tools like Claude Design, Google Stitch, Codex, Cursor, and other… 3.2k stars
• paperclipby paperclipai The open-source app everyone uses to manage agents at work 103k stars · 30 skills
• claude-code-best-practiceby shanraisshan from vibe coding to agentic engineering - practice makes claude perfect 67.6k stars · 9 skills
• agentsby wshobson Multi-harness agentic plugin marketplace for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Google Antigravity, and Pi 40.9k stars · 30 skills
• distillyby titanwings Distilly — Distill how they think into reusable Skills for any Agent or Bot. Formerly Colleague Skill（原同事 Skill）. 25.7k stars · 1 skill
• MemOSby MemTensor Self-evolving memory OS for LLM & AI Agents: ultra-persistent memory, hybrid-retrieval, and cross-task skill reuse, with 35.24% token savin… 11.9k stars · 7 skills