最適化過程の確認

プロンプトを与えると、先に作成したルールがLoaded .claude/rules/claude/config-maintenance.mdとして読み込み、分析を始めてくれる。

> Minimize startup context by refactoring @.claude/CLAUDE.md with excellent extractions of path-specific rules, commands, skills, and/or subagents. 
  ⎿  Read .claude/CLAUDE.md (77 lines)
  ⎿  Loaded .claude/rules/claude/config-maintenance.md

⏺ I'll analyze your current CLAUDE.md and restructure it following the configuration maintenance principles. Let me fir
st explore what's already in your .claude directory.

しばらくすると、最適化戦略としてslash commandやskillsの抽出を計画してくれる。

⏺ ★ Insight ─────────────────────────────────────
  Context Optimization Strategy:
  1. CLAUDE.md should contain only the role identity and pointers to skills/commands
  2. /go command - Triggered explicitly by user saying "go", handles the plan.md workflow
  3. tdd skill - Auto-triggers when writing tests or implementing features, contains methodology
  4. commit skill - Auto-triggers when committing, contains commit discipline
  5. Path-specific rule - You already have code-quality.md with paths filter - this is good!
  ─────────────────────────────────────────────────

そのまま進むと、skillやcommandを切り出した旨を報告してくれる。

コード品質に関するルールも切り出してくれている。パス限定ルールとしてよくあるプログラミング言語の拡張子に反応するようだが、自分の使う言語に反応しない場合は手直しするか、Skillに移すとよいだろう。

⏺ ★ Insight ─────────────────────────────────────
  What Changed:
  - Before: 77 lines loaded at every startup (3,450 bytes)
  - After: 10 lines loaded at startup (~300 bytes) — 91% reduction

  Context Loading Strategy:
  | Component                                         | When Loaded              | Content                                            |
  |---------------------------------------------------|--------------------------|----------------------------------------------------|
  | CLAUDE.md                                         | Always                   | Role identity + skill/command discovery (10 lines) |
  | rules/code-quality.md                             | When touching code files | Quality standards (15 lines, path-filtered)        |
  | skills/tdd/                                       | Auto, when writing tests | Full TDD methodology (description only at startup) |
  | skills/commit/                                    | Auto, when committing    | Commit discipline (description only at startup)    |
  | commands/go.md                                    | User-invoked /go         | Plan.md workflow (never loaded until used)         |
  | ───────────────────────────────────────────────── |                          |                                                    |

最終的に得られたCLAUDE.mdは以下の通りだ。CLAUDE.mdは10行と主張しているが、実質9行である。

# Role

Senior software engineer following Kent Beck's Test-Driven Development (TDD) and Tidy First principles.

## Quick Reference

- Use `/go` command to advance through plan.md tests (Red → Green → Refactor cycle)
- `tdd` skill auto-triggers for test writing, implementation, and refactoring guidance
- `commit` skill auto-triggers for commit discipline and change separation

試しにPythonでFizzBuzzを実装させたところ、適切にTDDスキルを使ってくれた。

> implement FizzBuzz in Python 

⏺ Skill(tdd)

⏺ I'll implement FizzBuzz using TDD principles - starting with a failing test, making it pass, then refactoring. Let me
 set up a todo list to track our Red → Green → Refactor cycles.