omd
Skill588 starsChanged 35 days agoMITView on GitHub
Compatibility router for older `omd` invocations. Route existing UI work to omd:apply, autonomous greenfield work to omd:autopilot, and DESIGN.md-only setup or migration to omd:init. Use it only when the legacy skill name is invoked; it reads Core v2 or legacy context without writing DESIGN.md itself.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vins-anity/ohmydifftheir own version, first seen Aug 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- vins-anity/ohmydiff★ 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.
In this repository89 other files it gives its agents.
- AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- web/CLAUDE.mdCLAUDE.md
- ego-browserSkill
- google-analyticsSkill
- omd:add-referenceSkill
- omd:batch-launchSkill
- omd-component-harvestSkill
- omd:designSkill
- omd-lab-01-designmd-impactSkill
- omd:migrateSkill
- omd-token-backfillSkill
- claude-designSkill
- hangulSkill
- omd:add-referenceSkill
- omd:aphroditeSkill
- omd:applySkill
- omd:asset-fetchSkill
- omd:autopilotSkill
- omd:batch-launchSkill
- omd:cjk-type-shaderSkill
- omd:codex-imageSkill
- omd-component-harvestSkill
- omd:designer-reviewSkill
- omd:experiment-gallerySkill
- omd:feelSkill
- omd:final-qaSkill
- omd:harnessSkill
- omd:humanizeSkill
- omd:initSkill
- omd:issueSkill
- omd:kr-writerSkill
- omd-lab-01-designmd-impactSkill
- omd-lab-02-design-harnessSkill
- omd:landingSkill
- omd:learnSkill
- omd:locale-adapterSkill
- omd:mediaSkill
- omd:migrateSkill
- omd:orchestratorSkill
- omd:reference-captureSkill
- omd:release-hygieneSkill
- omd:rememberSkill
- omd:restraintSkill
- omd:setupSkill
- omd:shader-heroSkill
- omd:showcaseSkill
- omdSkill
- omd:slop-auditSkill
- omd:syncSkill
- omd:tasteSkill
- omd-token-backfillSkill
- omd:updateSkill
- claude-designSkill
- hangulSkill
- omd-3d-heroSkill
- omd-aphroditeSkill
- omd-applySkill
- omd-asset-fetchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
If the package is absent, stale, invalid, or hash-mismatched, use root DESIGN.md independently for the rules it actually expresses.
- Very specific: line 53
If the user explicitly requests guided checkpoints, transfer to omd:harness.
- Very specific: line 56
Use the runtime's skill dispatch when available.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
OmD compatibility router
ROUTER_ONLY_NO_DESIGN_MD_WRITES
This skill preserves old omd entrypoints while the active workflows live in
omd:apply, omd:autopilot, and omd:init. It classifies the available design
context, transfers the original request to one canonical workflow, and then
stops. Do not duplicate a target workflow here.
Authority classification
Inspect these files without mutating them:
- A valid adopted Core v2 package has a hash-bound
.omd/system/manifest.jsonwithformat: design-md-core,format_version: 2.0.0,profile: portable-core, andauthority.canonical: system-graph. Only after the target workflow validates the manifest, graph, projection, and exact bidirectional hashes is.omd/system/graph.jsoncanonical. RootDESIGN.mdremains its complete, vendor-neutral portable projection. profile: migration-candidateis non-authoritative. Keep the sourceDESIGN.mdnamed by its authority record canonical while the candidate is reviewed. Never use the candidate as a Bound System.- If the package is absent, stale, invalid, or hash-mismatched, use root
DESIGN.mdindependently for the rules it actually expresses. It does not require sidecars, an OmD install, or this skill to be useful. Do not claim graph authority or a conformance level that has not been validated. - A legacy or unmarked root
DESIGN.mdremains a read-only compatibility input. If rootDESIGN.mdis absent,.stitch/DESIGN.mdmay be used only as the same read-only fallback. Apply declared rules, omit unknown values at the smallest boundary, and never silently rewrite or upgrade either file.
A stale binding invalidates graph authority, not the readable Markdown. Never promote reference observations, placeholders, or generic defaults into project facts.
Route once
- Existing UI, component, styling, motion, microcopy, design review, or other
bounded product work -> transfer the unchanged request and authority
classification to
omd:apply. - Broad from-scratch product work, a new surface with delegated decisions, or
autonomous design-system-plus-implementation work -> transfer to
omd:autopilot. - DESIGN.md bootstrap, design-system-only creation, explicit migration,
refactor, or refresh without product implementation -> transfer to
omd:init. - If the user explicitly requests guided checkpoints, transfer to
omd:harness; do not convert that request into Autopilot.
Use the runtime's skill dispatch when available. Otherwise locate the selected
skill in the active channel, read its SKILL.md completely, and follow it. Pass
through the user's original brief, preferences, and known authority facts so the
user is not asked to repeat them.
Write boundary
This compatibility shim may inspect and route only. It must not create, edit,
copy, move, rename, delete, or project DESIGN.md; it must not edit
.omd/system; and it must not run a writer or migration command itself. The
selected canonical workflow owns every write, checkpoint, migration proof, and
validation step.
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.

