omd:update
Skill588 starsChanged 35 days agoMITView on GitHub
Safely update an existing oh-my-design installation in place and verify it afterward. Use when the user asks to update, upgrade, refresh, reinstall, or check whether their OmD skills, agents, hooks, or reference catalog are current.
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
- omdSkill
- 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
- 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
12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Update only the OmD installation the user already has.
- Distinctive: line 16
Run from the intended project root unless the user explicitly requests the global installation.
- Distinctive: line 17
Use the latest package as the executor:
- Very specific: line 24
Never add --force. The update command detects installed channels, preserves the existing scope, refreshes managed files, and runs the …
- Distinctive: line 25
If the command reports a protected local difference, stop.
- Distinctive: line 35
Do not switch project ↔ global scope.
- Distinctive: line 36
Do not install channels that were not already installed.
- Distinctive: line 37
Do not enable proof policy, hooks, or Cursor Agent Skills that were previously absent.
- Distinctive: line 38
Do not update deprecated MCP configuration.
- Very specific: line 39
Do not use --force, delete drifted files, or replace symlinks automatically.
- Very specific: line 40
Do not edit DESIGN.md or product files during an OmD update.
- Very specific: line 42
If no installation exists, explain that this is a fresh install and use npx oh-my-design-cli@latest only after the user confirms …
≈ “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:installed-skill — managed by `omd install-skills`. Do not edit; rerun the command to refresh. -->Update oh-my-design
Update only the OmD installation the user already has. Preserve its project/global scope, installed channels, Cursor compatibility mode, DESIGN.md, references added by the user, and every file outside OmD ownership.
Workflow
- Run from the intended project root unless the user explicitly requests the global installation.
Use the latest package as the executor:
npx oh-my-design-cli@latest updateFor a global installation, append
--global. For another project root, append--dir <path>.- Never add
--force. The update command detects installed channels, preserves the existing scope, refreshes managed files, and runs the equivalent of a post-update doctor check. - If the command reports a protected local difference, stop. Show the exact scoped repair command or manual action it prints; do not overwrite the file on the user's behalf.
- Report the before/after state, preserved scope and channels, and any skipped drift. Do not claim success if the exit code is non-zero.
Tell the user to restart the coding agent, then run:
npx oh-my-design-cli@latest doctor --self-test
## Safety contract
- Do not switch project ↔ global scope.
- Do not install channels that were not already installed.
- Do not enable proof policy, hooks, or Cursor Agent Skills that were previously absent.
- Do not update deprecated MCP configuration.
- Do not use `--force`, delete drifted files, or replace symlinks automatically.
- Do not edit `DESIGN.md` or product files during an OmD update.
If no installation exists, explain that this is a fresh install and use `npx oh-my-design-cli@latest` only after the user confirms installation intent.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.

