agentleFS
kwakseongjaekwakseongjae/oh-my-design/.agents/skills/omd-lab-01-designmd-impact/SKILL.md

omd-lab-01-designmd-impact

Skill588 starsChanged 35 days agoMITView on GitHub

Archived DESIGN.md impact experiment compatibility gate. Use when an old Lab #01 run is requested, but do not generate new legacy 9/12-section documents; direct new experiments to the Core v2 benchmark track.

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:

    Do not create, update, or normalize a DESIGN.md through those playbooks.

    line 13
  2. Very specific:

    Use the same sealed prompt/model/effort/budget and keep full-harness comparisons separate.

    line 17

≈ “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 Lab #01 — archived writer gate

CORE_V2_LEGACY_EXPERIMENT_BLOCKED

The historical Lab #01 playbooks authored retired 9/12-section DESIGN.md files. They remain evidence about an earlier format, not a valid template for new runs. Do not create, update, or normalize a DESIGN.md through those playbooks.

For a new format-impact experiment, preregister arms against DESIGN.md Core v2: model-only, standalone Portable Core, and an adopted Bound System where relevant. Use the same sealed prompt/model/effort/budget and keep full-harness comparisons separate. A new visible document must have a clean top and the exact seven Core anchors, keep unknowns absent, and be useful without OmD or sidecars. Only an adopted profile: portable-core manifest may make its graph canonical.

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.