dx-standards-update
Skill8 starsChanged 4 months agoMITView on GitHub
Create, edit, or promote a standard in context/standards/ — from the conversation, a graduated lesson, or another project.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- dx-archiveSkill
- dx-brainstormSkill
- dx-diagnoseSkill
- dx-distillSkill
- dx-domain-discoverSkill
- dx-domainSkill
- dx-frameSkill
- dx-implementSkill
- dx-initSkill
- dx-lessonSkill
- dx-newSkill
- dx-planSkill
- dx-refactor-discoverSkill
- dx-referencesSkill
- dx-researchSkill
- dx-reviewSkill
- dx-review-triageSkill
- dx-roadmapSkill
- dx-standards-discoverSkill
- dx-tddSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 21
Use it for the standards-vs-lessons distinction, the standard entry shape, and the promotion criteria — confirm this rule is *recurring and …
- Distinctive: line 40
Stop. Do not chain into another skill.
≈ “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.
Files
dx-standards-update
Land a rule in the right context/standards/<layer>/<topic>.md. Standards are the rulebook — prescriptive, project-wide, stable, and edited in place (a catalog, not an append-only log). Read foundation/glossary.md for naming (a one-line habit — no section).
Guard. context/standards/ must exist. If it is missing, tell the user to run /dx-init first.
1 — Get the rule (three entry points)
- From the conversation (no argument) — the user said "make this a standard." Lift the rule from what was just discussed; if it is fuzzy, ask one clarifying question, no more.
- From a graduated lesson — a
foundation/lessons.mdentry that has stopped being "this one time" and become "how we do it here." Read it and carry its rule forward. - From
--from=PATH— read the named file (e.g. a graduated lesson, or another project'scontext/standards/…) and take the rule from it.
2 — Load the contract (invoke dx-references with knowledge-layer)
Use it for the standards-vs-lessons distinction, the standard entry shape, and the promotion criteria — confirm this rule is recurring and generalized, not a one-off (a one-off stays a lesson).
3 — Place it: layer × topic
Pick the file by layer (global / frontend / backend / testing) × topic (the existing filename it belongs in, e.g. coding-style.md, error-handling.md). Prefer an existing file; create a new <topic>.md only when nothing fits.
4 — Edit in place
Append the rule or refine an existing entry — a ## <heading> plus one to a few prescriptive lines ("do this"), matching the shape and tone of the neighbours. No preamble, no rationale essays. If you are promoting a lesson, add a one-line note to that foundation/lessons.md entry that it graduated (leave the entry — lessons are append-only).
Done when
The rule lives in one context/standards/ file, prescriptive and concise; any promoted lesson is marked graduated. Then print what changed and stop:
Standard updated: context/standards/<layer>/<topic>.md — <one-line what changed>
Next: /dx-plan <change-id> — the checklist will now match this standardStop. Do not chain into another skill.
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
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.

