design-system
Skill1 starsChanged 58 days agoMITView on GitHub
The project's UI design system (rules, tokens, component recipes in design-system/). Use BEFORE creating or changing any UI - HTML, CSS, JSX/TSX, Vue/Svelte templates, Tailwind classes, landing pages, emails, charts. Also use to build or rebuild the design system from a reference website URL.
193 other projects use a version of this.
Adopted by
Most recently taken up by
- Rugved1652/skillstheir own version, first seen Nov 16, 2026
- mannobeats/hyper-tastetheir own version, first seen Nov 16, 2026
- irank786/Claude-skillstheir own version, first seen Nov 16, 2026
- david33137/claude-skillstheir own version, first seen Nov 16, 2026
- AndresArreguy/ecc-pi-porttheir own version, first seen Nov 16, 2026
- Vujavujavuja/Stillmotion-onbrandtheir own version, first seen Nov 16, 2026
Used with
Projects with it also use setup-engine, team-level and 10 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.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 13 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 12 projects that use this
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 11 projects that use this
- +2 more from CoralGame
- +6 more from lilangMax
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- nextlevelbuilder/ui-ux-pro-max-skill★ 150ksame name
- getsentry/sentry★ 46ksame name
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- ethereum/ethereum-org-website★ 6ksame name
- langwatch/langwatch★ 5ksame name
- joye61/pic-smaller★ 2.9ksame name
- daveebbelaar/bama★ 1.7ksame name
- reatom/reatom★ 1.4ksame name
- microsoft/power-platform-skills★ 1.2ksame name
183 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 repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- extract-designSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 176 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
If the request is a URL, go to B.
- Very specific: line 19
Read design-system/DESIGN.md before writing markup or styles.
- Distinctive: line 27
Before you finish, run the check and fix every hit:
- Distinctive: line 31
Check the page at 375 px and 1440 px wide.
- Very specific: line 35
Ask before overwriting an existing design-system/.
- Very specific: line 38
Extract: - run the extract-design skill on the URL.
- Very specific: line 43
Fonts: - if the source font is commercial, pick the closest Google Font that has every subset the project needs (for this repo: vietnamese).
- Distinctive: line 54
Do / Don't, Gaps).
“Common” is measured: kept by at least 6 in 10 of the 176 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
Design system
Files (source of truth, in this order):
design-system/DESIGN.md- rules and design language. Read it fully first.design-system/tokens.css- every allowed color, font, size, space, radius, shadow, gradient, motion value.design-system/components.css- base styles and component recipes built only from tokens.
Request: $ARGUMENTS
If the request is a URL, go to B. Build. Otherwise go to A. Apply.
A. Apply (every UI change)
- Read
design-system/DESIGN.mdbefore writing markup or styles. - Load
tokens.cssthencomponents.cssin the page or app entry. Use the recipes (.btn,.tag,.card,.stat, ...) before writing new CSS. - Style only with
var(--token). No raw hex/rgb, font names, font sizes, radii, shadows or durations outsidetokens.css. Layout-only values (grid tracks, widths of one element) are fine. - A need the tokens do not cover: use the closest token, then report the gap
in your reply and append it to the "Gaps" list in
DESIGN.md. Never invent a token silently. - Before you finish, run the check and fix every hit:
grep -nE '#[0-9a-fA-F]{3,8}\b|rgba?\(' <changed files other than design-system/*> - Check the page at 375 px and 1440 px wide. Check keyboard focus is visible.
B. Build from a reference URL
Ask before overwriting an existing design-system/. Tell the user: we borrow
the design language only - never logos, brand names, copy or images.
- Extract - run the
extract-designskill on the URL. Output goes to.design-extract/<host>/. - Verify live - open the URL in a browser tool at 1440 x 900. Read computed
styles for:
body,h1-h4, main text sizes, primary and secondary buttons (and their inner elements), cards, tags, containers, section padding. Live computed values beat extractor numbers. - Fonts - if the source font is commercial, pick the closest Google Font
that has every subset the project needs (for this repo:
vietnamese). Record the substitution inDESIGN.md. - Write the three files:
tokens.css: primitives first (raw palette), then semantic tokens that point at primitives. Semantic names describe the role (--text-muted,--surface-card), not the color.components.css: reset, base typography, then one recipe per component seen on the source.DESIGN.md: keep the existing section order (Source, Principles, Color, Typography, Space and layout, Surfaces, Components, Motion, Accessibility, Do / Don't, Gaps).
- Prove it - build a small sample section with the recipes and screenshot it next to the source. Report what matches and what does not.
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.

