design-os
Skill1 starsChanged 58 days agoApache-2.0View on GitHub
Use for frontend or UI design work, design critique, reference research, visual feedback, or preflight review. It provides judgment standards, optional Refero research guidance, technique guidance, feedback protocol, and delivery checks. It excludes private preferences, customer cases, copied third-party archives, and local state.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- jangtrinh/design-ostheir own version, first seen Oct 17, 2026
- agentik-os/claude-code-skillstheir own version, first seen Sep 17, 2026
- jaysu66/design-ostheir own version, first seen Jul 16, 2026
- shreyvaughn/claude-skillstheir own version, first seen Jun 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- jangtrinh/design-os★ 37same name
- agentik-os/claude-code-skills★ 1same name
- shreyvaughn/claude-skills★ 1same name
- jaysu66/design-os★ 0same 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.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
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 16
Read this Skill's README.md, then load only what the task needs:
- Distinctive: line 33
Verify the real page before delivery.
- Distinctive: line 35
Keep personal preferences, customer material, copyrighted reference assets, credentials, and machine-specific paths outside this shared …
“Common” is measured: kept by at least 6 in 10 of the 3 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-os — Design OS Community Core
This is the portable, shareable core of a design operating system. It helps an Agent make UI decisions from explicit standards, references, feedback, and verification instead of producing generic screens. It can use the user's own official Refero connection as an optional research source; no Refero dataset or private preference archive is bundled with the Skill.
Required routing
Read this Skill's README.md, then load only what the task needs:
| Situation | Read |
| Any UI implementation or change | 1-judgment/STANDARDS.md, 1-judgment/AI-TELLS.md, and the project's DESIGN.md |
| Before delivery | 1-judgment/PREFLIGHT.md |
| New project | 4-workflow/WORKFLOW.md and 4-workflow/DESIGN-TEMPLATE.md |
| Use Refero as a research source | 3-references/REFERO.md, then use the user's official connection |
| User says a UI feels wrong | 4-workflow/FEEDBACK-PROTOCOL.md |
| Choosing interaction or motion techniques | 2-techniques/RECIPE.md, then the relevant part of PLAYS.md |
Non-negotiables
- Establish a reference and a one-page
DESIGN.mdbefore implementing a new interface when the project has no design direction. - Translate vague visual feedback into observable issues and evidence; do not force the user to speak design jargon.
- Verify the real page before delivery. A screenshot or static mock is not proof that the interaction works.
- Keep personal preferences, customer material, copyrighted reference assets, credentials, and machine-specific paths outside this shared Skill. Do not turn third-party research services into a redistributed archive.
Optional references
The included workflow and techniques are portable guidance. Refero is an optional external source governed by its own terms. If a project maintains its own authorized reference library, keep it project-local and out of this Skill.
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.