You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/commands/wrap-up.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,11 +37,13 @@ If during your session:
37
37
38
38
...that is relevant, was not known initially, and should be persisted, add it to the appropriate `CLAUDE.md` (for shared context) or
39
39
`CLAUDE.local.md` (for private notes) file. If the information is relevant for a subdirectory only,
40
-
place or update it in the `CLAUDE.md` file within that subdirectory. If it is structured information (e.g. relationship between classes, variables, or knockout observables, store it in "memory" - a model context protocol server for storing a knowledge graph)
40
+
place or update it in the `CLAUDE.md` file within that subdirectory.
41
41
42
42
When specific information belongs to a particular subcomponent, ensure you place it in the CLAUDE file for that component.
43
43
For example:
44
44
* Information A belongs exclusively to writing html code with knockout bindings → put it in `templates/CLAUDE.md`
45
45
* Information B belongs exclusively to programming in typescript → put it in `src/CLAUDE.md`
46
+
* Information C belongs exclusively to testing -> ptu it in `tests/CLAUDE.md`
46
47
47
-
This ensures important knowledge is retained and available in future sessions.
48
+
This ensures important knowledge is retained and available in future sessions.
49
+
**Important**: Keept the information concise and compact. Provide a **summary** of the final architecture and encountered pitfalls.
0 commit comments