Designer Skills Collection
A design skills pack for agents: research, UX strategy, design systems, UI, interaction, prototyping and visual critique
Install
/plugin marketplace add Owl-Listener/designer-skills
/plugin install ux-strategy@designer-skillsChange the plugin name after install to the collection you want; you can install several.
This is third-party code. Review the repository files before installing.
What it does
The plugin gathers design skills and commands across nine practice areas: research, design systems, UX strategy, UI, interaction, prototyping and testing, design ops, the designer toolkit and visual critique. Skills are knowledge units such as creating a persona or defining tokens, and commands are ready workflows that chain them in one pass, for example a full user discovery cycle or a screen critique. One marketplace also pulls in four more collections from sibling repositories: AI product design, UX program management, leadership and inclusive design. A navigator command routes you from a task description to where to start.
Who it is for. For designers and product teams who run interface work through an agent.
Good fit when
- You start a new product with research and personas
- You build a design system with tokens and components
- You need a structured screen critique or UX audit
Not a fit when
- You need one concrete component, not a design methodology
- The task is unrelated to design or product
Example request
Run a research cycle for a new app and build initial personasLimitations
The skills provide methodology and structure, not finished mockups, and do not connect to external design tools. Four of the five collections live in separate repositories and are pulled in through the marketplace.
How to disable. Remove the installed collection plugins via /plugin, or delete the skill folders from your agent's skills directory.
Security check
- The skills are methodology and references
README in short
The README describes a pack of 273 skills and 76 commands across 33 plugins in five collections. Installation is three steps in Claude Code with no terminal: add the marketplace, open Discover, tick what you want. It explains the difference between skills as knowledge and commands as workflows, and offers a start-here navigator to pick an entry point. Each plugin is also a Gemini CLI extension. MIT licensed.
SKILL.md
--- name: design-token description: 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 Token You are an expert in design token architecture and systematic design foundations. ## What You Do You help define, organize, and document design tokens — the atomic values that drive visual consistency. You understand token taxonomies, naming hierarchies, and cross-platform mapping.
FAQ
Can I install only the design skills?
Yes, on the Discover tab you tick the collections you want and install as few or as many as needed.
How does a skill differ from a command?
A skill is topic knowledge; a command is a workflow that chains several skills into one pass.
Related
Official Claude Code plugin from the Next.js repo: adopting Cache Components and Partial Prefetching, and verifying changes on a running dev server
Official shadcn/ui skill and MCP server: the agent searches registries, adds components via the CLI and follows the library's rules
A frontend design skill with 23 commands, live browser iteration and 61 detector rules for common AI-generated UI tells
Vercel Agent Skills
Agent Skills
Vercel's skills: React and Next.js performance, UI guideline audits, React Native, component composition and deploys