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

omd:design

Skill588 starsChanged 35 days agoMITView on GitHub

Legacy survey-based DESIGN.md writer redirect. Use for old omd:design requests only to route them to the Core v2 Autopilot or init workflow; this compatibility skill never writes DESIGN.md itself.

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 decode an old survey result into DESIGN.md, copy a catalog reference into the project root, or hand-author a partial replacement.

    line 19

≈ “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:design — Core v2 compatibility redirect

CORE_V2_LEGACY_WRITER_BLOCKED

This legacy survey flow cannot author a new project design system. It mapped preferences into the retired frontmatter/numbered-section format and could not produce the evidence-bound Core v2 package.

For a new project or autonomous build, route the original request to omd:autopilot. For design-system-only work, route it to the current omd:init workflow. Preserve the user's original brief and preferences; do not ask them to repeat information already present in the conversation.

Do not decode an old survey result into DESIGN.md, copy a catalog reference into the project root, or hand-author a partial replacement. New output must use the clean-top, seven-anchor standalone Core v2 projection. Only an explicitly adopted profile: portable-core manifest with exact graph/projection hashes may make the System Graph canonical; a migration candidate remains non-authoritative.

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.