agentleFS
kwakseongjaekwakseongjae/oh-my-design/.agents/skills/omd-add-reference/SKILL.md

omd:add-reference

Skill588 starsChanged 34 days agoMITView on GitHub

Reference catalog authoring compatibility gate. Core v2 cutover가 끝나기 전에는 신규 legacy DESIGN.md 쓰기를 차단하고 안전한 재개 조건을 설명한다.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If research is still useful, save nothing to the catalog.

    line 35
  2. Very specific:

    Never work around this gate by restoring a legacy YAML marker, numbered 13/15/16 sections, placeholder sentinels, or a second authoritative …

    line 44

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

omd:add-reference — Core v2 catalog cutover gate

Status: CORE_V2_CATALOG_WRITE_BLOCKED.

Scope, narrowed by owner decision 2026-09-16. This gate blocks writes that create a new legacy reference or a new Core catalog package. It does not block refreshing evidence on an existing reference — verification_v2, .verification.md, tokens.components state values, ## Proof — because that produces no Core package and adds no migration debt; the file stays legacy and stays in the same queue. Creating a reference, adding a brand, restoring a legacy YAML marker, emitting retired section output, placeholder sentinels, or hand-editing generated counts and mirrors all remain refused. Full rationale and the two expiry conditions: .claude/skills/omd-add-reference/SKILL.md.

This repository still reads the 440 historical reference files through the legacy frontmatter adapter. That makes them valid migration inputs, but it does not authorize a new legacy writer. Do not create, update, backfill, or sync a web/references/<id>/DESIGN.md from this skill.

When invoked:

  1. Inspect only. Do not write a reference, token block, generated catalog, or public count.
  2. Explain that project/user-facing DESIGN.md is already single-write Core v2, while reference authoring is paused until the catalog has a graph-backed metadata/evidence package and Core projection compiler.
  3. If research is still useful, save nothing to the catalog. Return a concise proposed source list and the intended reference id in chat only.
  4. Resume writes only after all of these exist and pass together:
    • Core v2 reference metadata/evidence sidecar schema;
    • registry, quality, AST, token, and verification readers for that schema;
    • deterministic graph → portable DESIGN.md projection;
    • legacy dual-read and Core single-write tests;
    • migration report with dropped_segments=0 and unknown facts absent.

Never work around this gate by restoring a legacy YAML marker, numbered 13/15/16 sections, placeholder sentinels, or a second authoritative Markdown dialect.

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.