kwakseongjae/oh-my-design / .claude/skills/omd-migrate
omd:migrate
VerifiedLegacy 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.
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-catalogshipped 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:
| Operation | Produces a Core package? | Status |
|---|---|---|
| Create a new legacy reference, or a new Core catalog package | yes / adds migration debt | still refused |
Refresh evidence on an existing reference — verification_v2, .verification.md, tokens.components state values, ## Proof | no; the file stays legacy and stays in the same migration queue | allowed |
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |