cc-dev-template 0.1.91 → 0.1.92

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cc-dev-template",
3
- "version": "0.1.91",
3
+ "version": "0.1.92",
4
4
  "description": "Structured AI-assisted development framework for Claude Code",
5
5
  "bin": {
6
6
  "cc-dev-template": "./bin/install.js"
@@ -14,11 +14,25 @@ This requires full conversation context. Handle it yourself rather than delegati
14
14
 
15
15
  ## Steps
16
16
 
17
- **1. Commit your work**
17
+ **1. Apply session learnings**
18
18
 
19
- Write clear commit messages that explain what was accomplished. This IS your record of completed work.
19
+ Review the session for anything that passes the "had I known this ahead of time" test — things that, known upfront, would have prevented mistakes or saved real time.
20
+
21
+ If anything qualifies, read `references/apply-learnings.md` and follow its hierarchy to put the fix in the right place.
22
+
23
+ If nothing qualifies (most sessions), skip this step entirely.
24
+
25
+ **2. Prune memory**
26
+
27
+ Read your MEMORY.md file. Check every entry against `references/memory-rules.md`.
28
+
29
+ - Entries that are project-specific tribal knowledge (not personal) — relocate using the hierarchy from step 1
30
+ - Entries that are stale, obvious, or discoverable from code — delete
31
+ - Entries that duplicate CLAUDE.md or rules files — delete
32
+
33
+ If MEMORY.md exceeds 200 lines, stop and deeply reflect. Something is wrong — you're storing things that don't belong.
20
34
 
21
- **2. Update `docs/CURRENT_WORK.md`**
35
+ **3. Update `docs/CURRENT_WORK.md`**
22
36
 
23
37
  This file is forward-looking. Review it holistically and ensure it contains ONLY:
24
38
 
@@ -35,23 +49,9 @@ This file is forward-looking. Review it holistically and ensure it contains ONLY
35
49
 
36
50
  The file should be scannable in 30 seconds. If it takes longer, it's too long.
37
51
 
38
- **3. Apply session learnings**
52
+ **4. Commit everything**
39
53
 
40
- Review the session for anything that passes the "had I known this ahead of time" test — things that, known upfront, would have prevented mistakes or saved real time.
41
-
42
- If anything qualifies, read `references/apply-learnings.md` and follow its hierarchy to put the fix in the right place.
43
-
44
- If nothing qualifies (most sessions), skip this step entirely.
45
-
46
- **4. Prune memory**
47
-
48
- Read your MEMORY.md file. Check every entry against `references/memory-rules.md`.
49
-
50
- - Entries that are project-specific tribal knowledge (not personal) — relocate using the hierarchy from step 3
51
- - Entries that are stale, obvious, or discoverable from code — delete
52
- - Entries that duplicate CLAUDE.md or rules files — delete
53
-
54
- If MEMORY.md exceeds 200 lines, stop and deeply reflect. Something is wrong — you're storing things that don't belong.
54
+ Commit all session work plus any changes from steps 1-3 (rules, CLAUDE.md updates, memory relocations, CURRENT_WORK.md). Write clear commit messages that explain what was accomplished.
55
55
 
56
56
  **5. Push**
57
57