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

omd:migrate

Skill588 starsChanged 35 days agoMITView on GitHub

Legacy deep-reference writer safety gate. Use for old brand migration requests only to prevent retired section/frontmatter writes until the Core v2 catalog migration pipeline is authoritative.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not mutate web/references/<id>/DESIGN.md, its frontmatter, numbered sections, verification footer, or mirrors.

    line 41
  2. Very specific:

    Do not adopt or overwrite its staged result.

    line 47

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

Expiry. This gate is a waiting state, not a policy. It lifts when the catalog adoption path lands — the T2-2 writer gate. Status, updated 2026-09-16 (the earlier "today: 없다" note was written 2026-09-02 and went stale):

  • graph-backed Core v2 writer exists — met. --adoption-target reference-catalog shipped with a four-canary isolated adopt → rollback → readopt rehearsal (2026-09-08, .omd/execution/2026-09-08/sprint90/core/).
  • every catalog reader accepts its package — not met. The web readers still parse legacy frontmatter and numbered sections (extract-tokens.ts, generate-css.ts, font-registry.ts, logos.ts).

Scope, narrowed by owner decision 2026-09-16. The second condition governs Core v2 packages, so it cannot govern a write that produces none. Two different operations were being blocked by one rule:

OperationProduces a Core package?Status
Create a new legacy reference, or a new Core catalog packageyes / adds migration debtstill refused
Refresh evidence on an existing reference — verification_v2, .verification.md, tokens.components state values, ## Proofno; the file stays legacy and stays in the same migration queueallowed

An evidence refresh does not create another legacy file — it restores what an earlier pass discarded from a file already queued for migration. It therefore falls outside this gate's stated purpose.

Still refused, with no one-off exception and no plausible fallback: creating a new reference, adding a brand, restoring a legacy YAML marker, emitting 13/15/16-section output, placeholder sentinels, a second authoritative Markdown dialect, or mutating generated counts and mirrors by hand.

omd:migrate — catalog write safety gate

CORE_V2_CATALOG_WRITE_BLOCKED

Do not mutate web/references/<id>/DESIGN.md, its frontmatter, numbered sections, verification footer, or mirrors. Those files remain readable during the migration window, but creating more legacy bytes would violate the Core v2 dual-read/single-write contract.

For a provider-free assessment, use the Core migration auditor in check mode. Do not adopt or overwrite its staged result. A migration candidate keeps the source DESIGN.md canonical until a graph-backed catalog writer, migrated consumers, evidence binding, and dropped_segments=0 acceptance ship together.

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.