AI Skills
Claude Code skills for product design
Six skills I wrote and use in my own work. Each one gives Claude Code a method for one part of the job: research, UX, visual craft, design systems, motion and Figma. They are free and MIT licensed.
$ npx skills add Gustavosilveira23/claude-design-skills --all -g
How the skills connect
Each skill knows when to pass the work on.
01 Evidence
02 Experience
03 Interface
04 Motion
In Figma
Evidence · /ux-research
/ux-research: What should we build, and what is the evidence?
Starts every study from the decision it has to inform, writes interview scripts, turns findings into atomic evidence and evidence into design specs.
Hands off to: /ux-designer
Read the guideExperience · /ux-designer
/ux-designer: How should this experience work?
Asks who the user is before building, designs the flow instead of a single screen and audits interfaces with a five-part scorecard.
Hands off to: /design-system, /ui-designer, /ux-research
Read the guideInterface · /design-system
/design-system: Is every screen using the same tokens?
Tokens, components, audits and Figma sync for projects built on shadcn/ui, Tailwind and Next.js.
Hands off to: /ui-designer, /ux-designer
SKILL.md on GitHubInterface · /ui-designer
/ui-designer: Does the screen hold up once rendered?
Reads your project's tokens before it styles, works in brand or product mode and checks the rendered screen itself.
Hands off to: /design-system, /ux-designer
Read the guideMotion · /creative-coding
/creative-coding: Should this move, and how?
Scroll animation, canvas and WebGL. Climbs from CSS to shaders only when the scene needs it, and respects reduced motion.
Hands off to: /design-system, /ui-designer, /ux-designer
SKILL.md on GitHubIn Figma · /figma-craft
/figma-craft: Will the Figma file keep its auto layout?
Writes to Figma through the MCP without breaking auto layout: frame tree first, sizing by role, checks by property instead of screenshot.
Hands off to: /ui-designer, /design-system, /ux-designer
SKILL.md on GitHub