agentleFS
Sign inStart free
ilhae-aiilhae-ai/claude-code-orchestrator/.claude/skills/update-design/SKILL.md

update-design

Skill18 starsChanged 10 months agoMITView on GitHub

Explicitly update DESIGN.md with decisions from the current conversation. Use when you want to force a design document update.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

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
  1. Distinctive:

    Update the appropriate section

    line 18
  2. Distinctive:

    Add entry to Changelog with today's date

    line 19
  3. Distinctive:

    When updating, add to the appropriate section:

    line 35
  4. Distinctive:

    Always add to Changelog:

    line 49
  5. Distinctive:

    Document content: English (technical), Korean OK for descriptions

    line 60
  6. Distinctive:

    If $ARGUMENTS provided, focus on recording that content.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

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-tracker skill. Use this when you want to force a design document update.

Workflow

  1. Read existing .claude/docs/DESIGN.md
  2. Extract decisions/information from the conversation
  3. Update the appropriate section
  4. Add entry to Changelog with today's date

Section Mapping

TopicSection
Goals, purposeOverview
Structure, componentsArchitecture
Design patternsImplementation Plan > Patterns
Library choicesImplementation Plan > Libraries
Decision rationaleImplementation Plan > Key Decisions
Future workTODO
Unresolved issuesOpen 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.

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.

Check your setup, free