/learnings
Reflects on the current session and captures important, reusable knowledge for future sessions.
Usage
/learnings
Parameters
None.
What It Does
1. Session Review
Reviews the full conversation history and identifies learnings that meet all of these criteria:
- Project-specific — not general knowledge from official docs
- Caused real friction — required debugging or multiple attempts
- Actionable — provides a concrete rule, command, or pattern
- Reusable — likely to come up again
- Not already documented — not covered by existing project docs
If nothing qualifies, it reports “No new learnings” and stops.
2. Classify
Each learning is classified into one of two categories:
| Category | Destination | Criteria |
|---|---|---|
| A | CLAUDE.md | Universal, concise (1-2 lines), rule-like |
| B | docs/coding/ | Detailed, niche, too long for CLAUDE.md |
3. Persist
- Category A: Added to the relevant section of
CLAUDE.md(respects a ~200 line cap) - Category B: Added to an existing or new file in
docs/coding/, with a reference added toCLAUDE.md
4. Summary
Reports which files were modified and what was added.
Rules
- Less is more — one high-quality learning beats five marginal ones
- No duplication of existing documentation
- No session-specific context (ticket numbers, temporary state)
- No generic TYPO3/PHP/Docker knowledge