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

omd:batch-launch

Skill588 starsChanged 34 days agoMITView on GitHub

Reference batch writer compatibility gate during the DESIGN.md Core v2 catalog cutover.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not add references, mutate counts, start authoring workers, or create promo claims from an unshipped batch.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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, tracked in docs/OMD_PLAN_2026-09-02.md §0 "카탈로그 채택 경로" (today: 없다 — the migrated bodies sit in docs/design-md-weight/migrated/ and web/references/ is still legacy). Until a graph-backed Core v2 writer exists and every catalog reader accepts its package, this skill refuses catalog writes — all of them, with no one-off exception and no plausible fallback.

omd:batch-launch — Core v2 catalog cutover gate

Status: CORE_V2_CATALOG_WRITE_BLOCKED.

Do not add references, mutate counts, start authoring workers, or create promo claims from an unshipped batch. The prior workflow emitted legacy frontmatter and numbered sections, so it is disabled until omd:add-reference has a graph-backed Core v2 writer and all catalog readers accept its package.

Candidate research may be returned in chat without repository writes. Never bypass this gate with legacy YAML, placeholder sentinels, or a mixed-format batch.

Write path: DESIGN.md v3 (2026-10-14)

The catalog is DESIGN.md v3 (spec/design-md-v3.md): every web/references/<id>/ holds a Google-frontmatter DESIGN.md and a reference.json sidecar. Any write this gate permits (an evidence refresh on an existing reference) goes through one path: read readReferenceSource(dir).markdown (the legacy-shaped source), edit it, and write it with scripts/design-md-v3/writer.mjs writeReference(dir, text), which converts, checks spec §10 conformance with 0 Google lint errors, and writes the file, the sidecar and the design-md/ mirror. web/scripts/assemble-reference.mjs emits v3 the same way. The OmD 0.1 text-patching tools (apply-state-values, apply-measured-palette, apply-primary-tasks, migrate-frontmatters, retire-template-motion) refuse v3 files until they are ported. Creating a new reference stays refused until the owner lifts this gate.

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.