@leing2021/super-pi 0.18.0 → 0.18.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.
package/README.md CHANGED
@@ -267,7 +267,14 @@ No rules are loaded when you brainstorm, check status, or do non-code tasks. Zer
267
267
 
268
268
  #### Customizing rules for your project
269
269
 
270
- Rules are plain Markdown files in the `rules/` directory. Edit them freely:
270
+ Two rule sources exist, with project-level taking priority:
271
+
272
+ | Source | Location | Survives `pi update`? |
273
+ |--------|----------|----------------------|
274
+ | **Project-level** | `{your-project-root}/rules/` | ✅ Yes |
275
+ | Package-level | Inside `node_modules/@leing2021/super-pi/rules/` | ❌ No |
276
+
277
+ To customize, create a `rules/` directory in your project root. `10-rules` checks it first — if a file exists there, it overrides the package default for that topic.
271
278
 
272
279
  **Add a language** — create a new directory with the 5 standard topics:
273
280
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@leing2021/super-pi",
3
- "version": "0.18.0",
3
+ "version": "0.18.1",
4
4
  "private": false,
5
5
  "type": "module",
6
6
  "description": "Pi-native Compound Engineering package for iterative development workflows",
@@ -1,11 +1,16 @@
1
1
  ---
2
2
  name: 10-rules
3
- description: "Progressively load project coding rules on demand. Auto-triggered by plan, work, and review skills."
3
+ description: "Progressively load project coding rules on demand. Auto-triggered by plan, work, and review skills, or run manually with /skill:10-rules."
4
4
  ---
5
5
 
6
6
  # Rules
7
7
 
8
- Project rules live under `rules/` in the super-pi package root (resolved as the skill directory's `../../rules/`).
8
+ Rules are loaded from two locations with clear priority:
9
+
10
+ 1. **Project-level** `{repo-root}/rules/` — if it exists, takes priority. Users maintain this themselves; survives `pi update`.
11
+ 2. **Package-level** `rules/` in the super-pi package — built-in defaults, used when no project-level override exists.
12
+
13
+ Detection: check `{repo-root}/rules/` first. If a file exists at the project level for the topic being loaded, use it. Otherwise fall back to the package-level copy.
9
14
 
10
15
  ## Core rule
11
16