@roulabs/mx 1.2.0 → 1.2.1

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/templates/CLAUDE.md +2 -4
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@roulabs/mx",
3
- "version": "1.2.0",
3
+ "version": "1.2.1",
4
4
  "description": "mx — run several features in parallel across shared repos using git worktrees",
5
5
  "type": "module",
6
6
  "bin": {
package/templates/CLAUDE.md CHANGED
@@ -115,7 +115,7 @@ Example entry:
115
115
 
116
116
  Primary path:
117
117
 
118
- 1. Read `<runtime>/context/INDEX.json` — every entry's metadata in one Read.
118
+ 1. **Read `<runtime>/context/INDEX.json` on every task** — trivial or not, small or large. Skimming a metadata index is cheap; the cost of missing a relevant entry is high. This is a hard rule, not a heuristic.
119
119
  2. Open files at `<runtime>/context/<path>.md` for entries whose metadata matches the current task.
120
120
 
121
121
  When INDEX descriptions don't surface what you need — and often they won't — fall back to anything that works:
@@ -123,12 +123,10 @@ When INDEX descriptions don't surface what you need — and often they won't —
123
123
  - **Grep `<runtime>/context/`** for keywords. Frequently the term you need lives in a body, not in any description.
124
124
  - **`ls` the folder recursively** to spot entries on disk that aren't indexed (orphans), and read them directly when relevant.
125
125
  - **Follow `related` chains** outward from a known-relevant entry to find the rest of a cluster.
126
- - **Read everything** if the registry is small (< ~30 entries) and you're starting unfamiliar work — cheaper than guessing.
126
+ - **Read everything** when in doubt — better than guessing.
127
127
 
128
128
  INDEX is the *primary* discovery surface, not the only one. Use whatever gets you to the right entry fastest — direct grep, full-content scan, recursive read, following links, your judgment.
129
129
 
130
- A 30-second skim of INDEX is free; do it before any non-trivial task. Skip only for typo-fix-level work.
131
-
132
130
  ### Maintain INDEX.json as you go
133
131
 
134
132
  When you add, rename, remove, or restructure an entry, update INDEX in the same change. Drift means orphan files (invisible to future sessions) or stale entries (false positives). After editing INDEX, sanity-check it parses as valid JSON.