update-design

update-design is a skill for Claude Code, Codex from cliffren/swf. It costs 20 tokens per session (490 once invoked), scanned A, original, MIT.

A documentation update process that compares recent decisions, experiments, and code changes with a project’s design document. An ADR is a written record of an architectural decision.

In plain words
What is it for?
Use it after creating an ADR or completing a relevant experiment or code change, to identify and update affected sections of docs/design.md.
Why use it?
It keeps the design document aligned with decisions that have already been recorded, so it does not describe an outdated system.

Skill for Claude CodeCodex

Part of the swf plugin — 16 skills, 1 agent shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/cliffren/swf/update-design
Any agent
npx skills add cliffren/swf --skill update-design
Clone the repo
git clone --depth 1 https://github.com/cliffren/swf

Made for: Claude Code, Codex.

Or install swf, the plugin that ships this one along with the rest of its 16 skills, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for update-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/cliffren/swf/update-design.svg)](https://agentmods.dev/skills/cliffren/swf/update-design)
Your own site
<a href="https://agentmods.dev/skills/cliffren/swf/update-design"><img src="https://agentmods.dev/badge/skills/cliffren/swf/update-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 490 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00490
Opus 5 $0.00010 $0.00245
Sonnet 5 $0.00004 $0.00098
Haiku 4.5 $0.00002 $0.00049

Measured 3d ago against content hash 3e852296a00b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/update-design/SKILL.md · 59 lines

What it actually says

Update Design Document

Review recent changes and update docs/design.md to keep it current.

Prerequisite

Every design.md change MUST be backed by an ADR. If no recent ADR exists:

  • Ask: "没有找到未同步的 ADR。要先用 /swf:adr 记录决策吗?"
  • Do NOT proceed to modify design.md without an ADR as justification
  • No exceptions

Workflow

  1. Gather what changed:

    • Read all ADRs in docs/adr/ — identify any not yet reflected in design.md
    • Read current docs/design.md
  2. Identify deltas:

    • List specific sections of design.md that need updating
    • For each delta, note the source (which ADR, experiment, or commit)
  3. Present changes to user:

    ## design.md 需要更新的部分
    
    1. **Section: 数据存储层**
       原因:ADR-003 决定使用 sparse matrix
       变更:将 dense array 描述改为 sparse matrix,更新相关 API
    
    2. **Section: 性能估算**
       原因:实验 exp-002 显示内存占用低于预期
       变更:更新内存估算数据
    
    确认更新吗?
    
  4. Apply changes after user confirms:

    • Edit docs/design.md with the identified changes
    • Preserve the document's overall structure and style
    • Add a changelog entry at the bottom if one exists
  5. Commit:

    • git add docs/design.md
    • Commit with message: docs: update design.md (based on ADR-NNN, exp-NNN)

Rules

  • NEVER modify design.md without user confirmation
  • NEVER delete existing content without explicit approval — prefer updating or annotating
  • If there are no changes needed, say so: "design.md 已是最新,无需更新"
  • This is the ONLY approved way to modify design.md (per CLAUDE.md conventions)
  • Every change must trace back to an ADR or experiment record — no ad-hoc edits
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 59 lines · 20 tokens per session scan A 3e852296a00b

Subscribe to this mod's changes

update-design is a skill published in the GitHub repository cliffren/swf (5 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 490 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens