update-design
Skill18 starsChanged 9 months agoMITView on GitHub
Explicitly update DESIGN.md with decisions from the current conversation. Use when you want to force a design document update.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 18
Update the appropriate section
- Distinctive: line 19
Add entry to Changelog with today's date
- Distinctive: line 35
When updating, add to the appropriate section:
- Distinctive: line 49
Always add to Changelog:
- Distinctive: line 60
Document content: English (technical), Korean OK for descriptions
- Distinctive: line 63
If $ARGUMENTS provided, focus on recording that content.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Update Design Document
Record/update project design and implementation decisions in .claude/docs/DESIGN.md based on conversation content.
Note: This skill explicitly invokes the same workflow as the
design-trackerskill. Use this when you want to force a design document update.
Workflow
- Read existing
.claude/docs/DESIGN.md - Extract decisions/information from the conversation
- Update the appropriate section
- Add entry to Changelog with today's date
Section Mapping
| Topic | Section |
| Goals, purpose | Overview |
| Structure, components | Architecture |
| Design patterns | Implementation Plan > Patterns |
| Library choices | Implementation Plan > Libraries |
| Decision rationale | Implementation Plan > Key Decisions |
| Future work | TODO |
| Unresolved issues | Open Questions |
Update Format
When updating, add to the appropriate section:
### Key Decisions
#### {Decision Title} ({Date})
**Context**: {Why this decision was needed}
**Decision**: {What was decided}
**Rationale**: {Why this option was chosen}Changelog Entry
Always add to Changelog:
## Changelog
### {Date}
- {Brief description of what was recorded}Language
- Document content: English (technical), Korean OK for descriptions
- User communication: Korean
If $ARGUMENTS provided, focus on recording that content.
Other versions3 projects use a version of this.
Word for word · 1
- ilhae-ai/claude-code-orchestrator★ 18100% same
Edited · 0
None found.
Wrote their own version · 2
- EthanReedLabs/sulde★ 99same name
- pumpkit-io/sdlc★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- checkpointingSkill
- codex-systemSkill
- design-trackerSkill
- gemini-systemSkill
- initSkill
- planSkill
- research-libSkill
- simplifySkill
- startprojectSkill
- tddSkill
- update-lib-docsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.