agentleFS
kwakseongjaekwakseongjae/oh-my-design/.claude/skills/omd-update/SKILL.md

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.

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
  1. Very specific:

    Update only the OmD installation the user already has.

    line 12
  2. Distinctive:

    Run from the intended project root unless the user explicitly requests the global installation.

    line 16
  3. Distinctive:

    Use the latest package as the executor:

    line 17
  4. Very specific:

    Never add --force. The update command detects installed channels, preserves the existing scope, refreshes managed files, and runs the …

    line 24
  5. Distinctive:

    If the command reports a protected local difference, stop.

    line 25
  6. Distinctive:

    Do not switch project ↔ global scope.

    line 35
  7. Distinctive:

    Do not install channels that were not already installed.

    line 36
  8. Distinctive:

    Do not enable proof policy, hooks, or Cursor Agent Skills that were previously absent.

    line 37
  9. Distinctive:

    Do not update deprecated MCP configuration.

    line 38
  10. Very specific:

    Do not use --force, delete drifted files, or replace symlinks automatically.

    line 39
  11. Very specific:

    Do not edit DESIGN.md or product files during an OmD update.

    line 40
  12. Very specific:

    If no installation exists, explain that this is a fresh install and use npx oh-my-design-cli@latest only after the user confirms …

    line 42

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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

  1. Run from the intended project root unless the user explicitly requests the global installation.
  2. Use the latest package as the executor:

    npx oh-my-design-cli@latest update

    For a global installation, append --global. For another project root, append --dir <path>.

  3. 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.
  4. 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.
  5. Report the before/after state, preserved scope and channels, and any skipped drift. Do not claim success if the exit code is non-zero.
  6. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.