dx-init
Skill8 starsChanged 4 months agoMITView on GitHub
Scaffold the dx- SDLC state tree (context/) in this project and seed the baseline standards and review Policies.
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-lessonSkill
- dx-newSkill
- dx-planSkill
- dx-refactor-discoverSkill
- dx-referencesSkill
- dx-researchSkill
- dx-reviewSkill
- dx-review-triageSkill
- dx-roadmapSkill
- dx-standards-discoverSkill
- dx-standards-updateSkill
- dx-tddSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Create (only if absent) under context/:
- Distinctive: line 39
No block yet: append it. Block present: replace its contents in place, never add a second one.
- Very specific: line 43
Ensure the project's .gitignore lists .worktrees/ — where /dx-implement auto mode keeps its worktrees.
- Distinctive: line 53
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-init
Set up the context/ tree the dx- workflow reads and writes. Idempotent by contract: create what's missing, never touch what exists. Re-running is safe.
Scaffold
Create (only if absent) under context/:
foundation/ glossary.md, lessons.md, research/
standards/ global/, frontend/, backend/, testing/
efforts/ changes/ archive/
config/ review-policies/, templates/- Standards: decide first whether
context/standards/existed before this run.- Absent (fresh context): seed the three global standards by copying
${CLAUDE_SKILL_DIR}/assets/standards/global/*.mdintocontext/standards/global/. - Present: copy nothing — a project removes and replaces the shipped standards, and re-seeding resurrects what it deleted. List the shipped standards that aren't in
context/standards/global/and ask which, if any, to copy. Copy only the ones the user names; never overwrite an existing file.
- Absent (fresh context): seed the three global standards by copying
- Seed the review Policies and templates by copying
${CLAUDE_SKILL_DIR}/assets/config/intocontext/config/(review-policies/*.mdandtemplates/*.md), missing files only. They are user-owned from then on:/dx-reviewreads them, and a project may edit or add to them. standards/{frontend,backend,testing}/ship empty —dx-standards-discoverfills them per-project from the real codebase.foundation/glossary.mdandfoundation/lessons.mdget a one-line header each and nothing more (e.g.# Glossary — ubiquitous language for this project/# Lessons — accrued warnings and load-bearing decisions (append-only)). They stay empty;dx-domain-discoveranddx-lessonfill them.
Agent instructions file
Write to the project's root AGENTS.md when it exists and CLAUDE.md is absent or holds only a pointer to it (e.g. @AGENTS.md); otherwise write to CLAUDE.md, creating it if absent. Keep everything dx- owns inside one managed block, so later injections edit only that block and the rest of the file stays the user's:
<!-- dx:workflow:start -->
This project uses the dx- SDLC framework; workflow state lives under `context/`.
<!-- dx:workflow:end -->No block yet: append it. Block present: replace its contents in place, never add a second one.
.gitignore
Ensure the project's .gitignore lists .worktrees/ — where /dx-implement auto mode keeps its worktrees. Create the file if absent, else append the line if missing; never duplicate an existing entry.
Done when
The tree above exists, the review Policy and template files are in place, the global standards are seeded (fresh context) or the user was asked about additions (existing context), the agent instructions file carries the managed dx:workflow block, and .gitignore ignores .worktrees/. Print a short created/present status per artifact, listing each review Policy and template file and the .gitignore entry, then:
Next: /dx-new <idea> — create a change or effort and start the workflow.Stop. 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.

