Reflection Self-Question Checklist (quickly go through after completing a task)
- Did this time havepitfalls/detours? What was the root cause?
- Was there anycounterintuitive behavior(unexpected behavior of frameworks, APIs, or tools)?
- Was there anyarchitecture decisionorproject conventionworth recording?
- Will this informationstill be used next time? Will other developers benefit?
All no → skip, do not memorize.
Storage Location
| Category | Location | Commit to git | Content |
|---|---|---|---|
| Team-shared | Project .claude/memory/MEMORY.md |
Yes | Deployment lessons, business rules, architecture decisions, environment key points, pitfall records |
| Sensitive private | ~/.claude/projects/<project>/memory/MEMORY.md |
No | Passwords, keys, tokens, personal paths |
Writing Process
- Read the target file, check whether relevant memories already exist
- Existing → Edit and update; none → append a new entry; contradictory → correct the old memory
- Group by semantics (
##headings), not by time - Keep the total number of lines within 150; merge and streamline when exceeded
Writing Principles
- Conclusion-oriented: write "Docker --env-file does not remove quotes", not a process narrative
- Actionable: write "use sed for precise replacement, do not overwrite the entire .env"
- With context: write "Prisma P1012 → check whether DATABASE_URL has quotes"
- No duplication: do not repeatedly record what already exists in CLAUDE.md / skill
- Sensitive separation: passwords and keys go only into private memory; in shared memory, use "already configured" instead of specific values