ui-ux-design-system
Skill17 starsChanged 8 months agoMITView on GitHub
Premium neutral-first UI/UX design system and frontend workflow for product interfaces. Use when designing or reviewing pages, components, dashboards, settings screens, editors, forms, tables, modals, drawers, or interaction patterns that should feel calm, premium, responsive, system-driven, and production-ready. Also use when making design decisions about hierarchy, tokens, spacing, dark/light parity, component states, and cross-page consistency.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jac2206/agentic-skillstheir own version, first seen Nov 15, 2026
- FutureAtoms/claude-skills-backuptheir own version, first seen Mar 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- jac2206/agentic-skills★ 4same name
- FutureAtoms/claude-skills-backup★ 1same name
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 repository4 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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
Use this skill to design or review product UI with a calm, premium, system-first approach.
- Distinctive: line 48
Read references/design-system-skills.md when you need the full system:
- Distinctive: line 60
Prefer existing product patterns when working in an established codebase.
- Distinctive: line 61
Do not introduce decorative styles that break the system just to make one screen “special.”
- Distinctive: line 62
Avoid colorful or noisy dashboards unless explicitly requested.
- Distinctive: line 63
Keep output production-ready, not concept art.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UI UX Design System
Overview
Use this skill to design or review product UI with a calm, premium, system-first approach. It is intended for application UI and real workflow surfaces, not decorative concept art.
Workflow
- Define the screen purpose, user goal, and single primary action.
- Choose the page structure before styling:
- top bar or context row
- intro or summary
- main working area
- supporting panels
- secondary details
- Apply the design rules from references/design-system-skills.md.
- Implement with reusable components, semantic tokens, responsive layout, and real states.
- Final-check the screen:
- hierarchy is obvious
- accents are restrained
- cards feel like one family
- empty, loading, and error states exist
- mobile layout still works
Defaults
- Neutral-first surfaces
- Premium SaaS product tone
- Dark-first with light-mode parity
- One clear primary action
- Reusable components over one-off div soup
- Semantic colors only for status
Use This Skill To
- design internal product pages, dashboards, builders, settings, editors, tables, modals, and drawers
- review UI hierarchy, spacing, tokens, states, and responsiveness
- refactor noisy or inconsistent UI toward one coherent system
- decide when to use cards, tabs, chips, alerts, tables, and side panels
References
Read references/design-system-skills.md when you need the full system:
- design philosophy
- tokens
- spacing, radius, shadows, typography
- desktop, tablet, and mobile layout rules
- component rules
- AI product patterns
- accessibility and responsiveness
Constraints
- Prefer existing product patterns when working in an established codebase.
- Do not introduce decorative styles that break the system just to make one screen “special.”
- Avoid colorful or noisy dashboards unless explicitly requested.
- Keep output production-ready, not concept art.
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.

