design-tokens
Skill32 starsChanged 49 days agoMITView on GitHub
Establish color, typography, spacing, radius and motion as named role-based tokens. Use before building any interface.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- miratcan/claude-skillstheir own version, first seen Nov 16, 2026
- fatihkan/baditheir own version, first seen Nov 16, 2026
- dmlguq456/heartingtheir own version, first seen Nov 10, 2026
- plugin87/ux-ui-agent-skillstheir own version, first seen Nov 10, 2026
- ainurdev/mystical-assistanttheir own version, first seen Nov 8, 2026
- gitbutlerapp/gitbutlertheir own version, first seen Nov 8, 2026
Used with
Projects with it also use design-flow, micro-interactions and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
julianoczkowskiSkilldesign-flow
Run the full design-to-build workflow as a guided sequence. Orchestrates all designer skills in order, from grilling through review. Use when user wants to go through the complete design process, start a project from scratch, run the full flow, or mentions "design flow" or "full workflow".
Also in 6 projects that use this
solinkzSkillmicro-interactions
Expert micro-interaction architect for mobile apps, web applications, and responsive websites. Use this skill when the user asks to add, build, fix, audit, or consult on micro-interactions, animations, transitions, motion design, gesture feedback, haptics, loading states, skeleton screens, pull-to-refresh, swipe actions, scroll animations, button states, form validation feedback, toast notifications, modals, dropdowns, toggles, progress indicators, shared element transitions, spring physics, easing curves, motion tokens, or any interaction that provides visual/haptic/auditory feedback to user actions. Triggers on: "micro-interaction", "animation", "transition", "motion", "easing", "spring", "gesture", "haptic", "feedback", "loading state", "skeleton", "shimmer", "pull to refresh", "swipe", "drag", "hover effect", "press state", "focus ring", "scroll animation", "parallax", "stagger", "orchestration", "reduced motion", "View Transitions", "layout animation", "shared element", "hero animation", "morphing", "Framer Motion", "GSAP", "Lottie", "Rive", "React Spring", "anime.js", or any request to make an interface "feel better", "feel alive", "feel snappy", "feel responsive", or "feel polished".
Also in 3 projects that use this
jpoindexterSkilldesign-system-audit
Audit code for design system violations - grid spacing, tokens, existing components
Also in 3 projects that use this
renfei-designSkilla11y-audit
Audit Figma designs for WCAG accessibility issues — color contrast, minimum font size, touch target sizing, and missing text alternatives. Use when asked to check accessibility, audit contrast ratios, find a11y issues, verify WCAG compliance, or review designs for accessibility problems. Scans nodes, analyzes offline, and annotates issues in Figma.
Also in 4 projects that use this
brianciouSkillux-writing
UX writing guidelines for reviewing and optimizing interface copy. Use when the user asks to review, improve, or rewrite UI text including button labels, error messages, onboarding flows, or any interface copy. Apply when auditing microcopy for web apps, mobile apps, or any digital product requiring clear, user-centered communication.
Also in 3 projects that use this
GitHubSkillaccessibility-audit
Audits actual components and routes against applicable WCAG 2.2 A/AA criteria using consumer-owned design-system evidence and repository tools. Use when asked for an accessibility audit, a11y check, keyboard or focus review, contrast check, or screen-reader verification.
Also in 3 projects that use this
Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
- gitbutlerapp/gitbutler★ 22ksame name
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- rommapp/argosy-launcher★ 737same name
- julianoczkowski/designer-skills★ 536same name
- glebis/claude-skills★ 414same name
- dylanfeltus/skills★ 179same name
- marcusgoll/Spec-Flow★ 94same name
- ilikescience/design-tokens-skill★ 15same name
- icons8/agent-skills★ 12same name
- dmlguq456/hearting★ 10same name
25 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- application-packSkill
- brief-to-tasksSkill
- design-briefSkill
- design-reviewSkill
- frontend-designSkill
- grill-meSkill
- heuristic-evaluationSkill
- information-architectureSkill
- persona-acid-testSkill
- pick-upSkill
- stuckSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
If starting from scratch, create CSS custom properties across these five categories:
- Distinctive: line 33
If a value looks correct in Figma but renders differently in the browser, run this audit before filing a bug.
“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are establishing the design system foundation. Tokens defined here are used by every component in /frontend-design. Get this right before building anything.
First, check: does a design system already exist for this project? Ask the user to confirm. If yes, document the existing tokens rather than inventing new ones. Pull from Figma or existing CSS files if accessible.
If starting from scratch, create CSS custom properties across these five categories:
Color
Brand colors (primary, secondary, accent), semantic colors (action, destructive, success, warning), neutral scale (background, surface, border, text), feedback colors (error, warning, success, info). Name every token by its purpose, not its value. Use --color-action not --color-blue. Use --color-text-primary not --color-gray-900.
Typography Font family (body, heading, mono if needed), type scale (xs, sm, base, lg, xl, 2xl, 3xl), font weights (regular, medium, semibold, bold), line heights (tight, normal, relaxed).
Spacing
A consistent scale, not arbitrary values. Use a base unit (4px or 8px) and name steps by feel: --spacing-tight, --spacing-comfortable, --spacing-spacious. At minimum: 4px, 8px, 12px, 16px, 24px, 32px, 48px, 64px.
Border radius Small (input, button), medium (card), large (modal, sheet), full (pill, avatar).
Motion A duration scale (fast, default, slow) and one easing curve. Justify the slow end against the slowest device your user is actually holding.
Output as a ready-to-paste CSS :root block. Include a brief comment above each category explaining the system logic. No inline documentation that pads length; every comment must earn its space.
Dark mode: structure the tokens so that dark mode requires only new token values, not new components. Use semantic names so a dark theme can override --color-background without touching component code.
Token audit (use this when Figma and the frontend do not match)
If a value looks correct in Figma but renders differently in the browser, run this audit before filing a bug. Paste your Figma token export and your CSS file and ask:
"I am going to paste two things: a Figma token export and a CSS file. Compare them. Tell me: (1) which tokens in the export are not referenced anywhere in the CSS, (2) which CSS values are hardcoded instead of using a token, and (3) whether there are any unit mismatches between the token values and the CSS values (for example, a px value in the token but a rem value in the CSS). List each issue with the specific token name and the line in the CSS where the problem appears."
The four most common causes of a mismatch: the token was never exported from Figma, the token was exported but the CSS references a hardcoded value instead, the units differ (px in Figma, rem in CSS), or the comparison is being made at different zoom levels. Confirm all four before concluding something is broken.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

