Review an existing CLAUDE.md, identify gaps, and refine it through targeted questions. Then ask broader project questions to capture learnings in MEMORY.md. Use after /cmd-generator or whenever the CLAUDE.md feels incomplete. Triggers: "clarify", "確認", "深掘り", "CLAUDE.md確認", "もっと詳しく", "refine CLAUDE.md".
Refine a project's CLAUDE.md by identifying gaps, then capture broader project knowledge in MEMORY.md.
Search for the project's CLAUDE.md in this order:
./CLAUDE.md (current working directory)CLAUDE.md/cmd-generator first and stop.Read the file fully before proceeding.
Analyze the CLAUDE.md for weak areas. Check each section:
| Section | Look for |
|---|---|
| Commands | Missing key commands (dev, build, test, lint, deploy), undocumented flags/options |
| Architecture | Important directories not explained, missing layers (API, DB, middleware) |
| Conventions | Missing naming patterns, import order, error handling, logging conventions |
| Do NOT | Common pitfalls not yet listed, footguns specific to the stack |
| Testing | Missing test patterns, fixture setup, mocking approaches, coverage expectations |
| Key Decisions | Undocumented architectural choices that affect daily coding |
Also scan the actual codebase (package.json, directory structure, config files) to find things the CLAUDE.md should mention but doesn't.
Use AskUserQuestion with up to 4 questions about the weakest areas found in step 2.
Focus on gaps that would most improve Claude's effectiveness in this project.
Apply the answers to the appropriate sections of CLAUDE.md. Show the user a summary of what was added or changed.
Then re-evaluate: are there still significant gaps? If so, proceed to Round 2. If CLAUDE.md is now solid, skip directly to Phase 2.
Use AskUserQuestion with up to 4 more questions, now informed by the Round 1 answers.
Good candidates for Round 2:
Update CLAUDE.md with the answers and show what changed.
Ask up to 4 questions about topics NOT covered by CLAUDE.md:
Skip any topic already well-documented in CLAUDE.md or MEMORY.md.
Classify each answer and write to the appropriate file:
| Classification | Destination |
|---|---|
| Project-specific conventions, architecture, commands | Project CLAUDE.md |
| Project-specific workflow, gotchas, team conventions | Project MEMORY.md |
| Personal preferences, general tools/habits | ~/.claude/MEMORY.md |
Before creating any MEMORY.md file, ask the user for approval.
Present what was updated:
## Changes Made
- CLAUDE.md: added X, updated Y
- MEMORY.md (project): created with Z
- ~/.claude/MEMORY.md: appended W
AskUserQuestion tool for all questions (not free-text), with concrete options when possible