prizmkit 1.1.1 → 1.1.4

package/bundled/rules/prizm/prizm-documentation.md

@@ -18,19 +18,20 @@ WHEN TO UPDATE .prizm-docs/:
 - Before modifying any source file, read `.prizm-docs/root.prizm` if it exists to understand project structure.
 
 FORMAT RULES (enforced by pre-commit hook — violations block commit):
-- ALL CAPS section headers: MODULE:, FILES:, RESPONSIBILITY:, UPDATED:, etc.
+- ALL CAPS section headers: MODULE:, FILES:, RESPONSIBILITY:, etc.
 - KEY: value pairs and dash-prefixed lists only
 - PROHIBITED: prose paragraphs, markdown headers (##/###), code blocks (```), emoji, ASCII art
+- No UPDATED timestamps — git is the authoritative source for temporal information
 - This format is designed for AI token efficiency, not human readability. Do not add human-friendly formatting.
 
 SIZE LIMITS (hard — pre-commit hook blocks commits exceeding these):
 - L0 root.prizm: 4KB max
-- L1 module.prizm: 3KB max
+- L1 module.prizm: 4KB max
 - L2 detail.prizm: 5KB max
 
 SIZE OVERFLOW HANDLING:
-- L0 approaching 4KB: consolidate MODULE_INDEX, keep only top-5 RULES, remove PATTERNS detail
-- L1 approaching 3KB: move implementation details to L2, keep only INTERFACES signatures
+- L0 approaching 4KB: if MODULE_INDEX has > 15 entries, convert to MODULE_GROUPS format (group by domain). Otherwise consolidate descriptions, keep only top-5 RULES, remove PATTERNS detail.
+- L1 approaching 4KB: trim KEY_FILES descriptions, ensure RULES <= 3 entries, move detail to L2
 - L2 approaching 5KB: archive CHANGELOG entries older than 90 days to changelog-archive.prizm
 - NEVER exceed hard limits — pre-commit hook will block the commit
 
@@ -40,26 +41,24 @@ L0 root.prizm:
 - PRIZM_VERSION
 - PROJECT
 - LANG
-- MODULE_INDEX (with -> pointers to L1 files)
+- MODULE_INDEX or MODULE_GROUPS (with -> pointers to L1 files)
 - RULES (top-level project rules)
-- UPDATED
 
-L1 module.prizm:
+L1 module.prizm (structural index only):
 - MODULE
 - FILES
 - RESPONSIBILITY
-- INTERFACES (public/exported only)
 - DEPENDENCIES
-- UPDATED
+- L1 does NOT contain: INTERFACES, DATA_FLOW, TRAPS, DECISIONS (those belong in L2)
 
 L2 detail.prizm:
 - MODULE
 - FILES
 - KEY_FILES
 - DEPENDENCIES
-- TRAPS
+- INTERFACES
+- TRAPS (with severity prefix: [CRITICAL], [HIGH], or [LOW])
 - CHANGELOG
-- UPDATED
 
 L2 GENERATION TEMPLATE (use when AI first touches a sub-module with no L2 doc):
 
@@ -71,10 +70,11 @@ KEY_FILES:
 DEPENDENCIES:
 - uses: <lib>: <why>
 - imports: <module>: <what>
+INTERFACES:
+- <exported function/class>: <signature and purpose>
 TRAPS:
-- <gotcha, race condition, or non-obvious coupling>
+- [LOW] <gotcha, race condition, or non-obvious coupling> | FIX: <approach>
 CHANGELOG:
-- <YYYY-MM-DD> | add: initial L2 documentation
-UPDATED: <YYYY-MM-DD>
+- root | add: initial L2 documentation
 
-TRAPS is critical — always record gotchas, race conditions, non-obvious behavior, and surprising coupling between modules.
+TRAPS is critical — always record gotchas, race conditions, non-obvious behavior, and surprising coupling between modules. Every TRAP must have a severity prefix ([CRITICAL], [HIGH], or [LOW]).

package/bundled/rules/prizm/prizm-progressive-loading.md

@@ -4,7 +4,8 @@ description: "PrizmKit progressive context loading protocol"
 
 This project uses PrizmKit's progressive loading protocol:
 - ON SESSION START: Read `.prizm-docs/root.prizm` (L0 — project map)
-- ON TASK: Read L1 (`.prizm-docs/<module>.prizm`) for relevant modules
+- ON RESUME (feature/bugfix directory has session-summary.md): Read session-summary.md first for prior context, then load only L1/L2 for modules mentioned in it
+- ON TASK: Read L1 (`.prizm-docs/<module>.prizm`) for relevant modules. If MODULE_INDEX entries have keyword tags (e.g., `[login, jwt, oauth]`), match user's task description against tags to prioritize which modules' L1 to load first. If root.prizm uses MODULE_GROUPS, identify the relevant domain first, then load L1 only for modules in that domain.
 - ON FILE EDIT: Read L2 (`.prizm-docs/<module>/<submodule>.prizm`) before modifying
 - NEVER load all .prizm docs at once
 - Arrow notation (->) in .prizm files indicates load pointers

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.1",
+  "version": "1.1.4",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",
@@ -72,7 +72,7 @@
       "hasScripts": false
     },
     "feature-workflow": {
-      "description": "One-stop entry point for feature development. Orchestrates app-planner → dev-pipeline-launcher → background execution. Handles multi-feature batch development from a single request.",
+      "description": "One-stop entry point for feature development. Orchestrates feature-planner → feature-pipeline-launcher → background execution. Handles multi-feature batch development from a single request.",
       "tier": "companion",
       "category": "orchestration-skill",
       "subcategory": "workflows",
@@ -80,8 +80,8 @@
       "hasScripts": false
     },
     "refactor-workflow": {
-      "description": "End-to-end refactor workflow: analyze → plan → implement → review → commit. Behavior-preserving.",
-      "tier": "1",
+      "description": "One-stop entry point for code refactoring. Orchestrates refactor-planner → refactor-pipeline-launcher → execution.",
+      "tier": "companion",
       "category": "orchestration-skill",
       "subcategory": "workflows",
       "hasAssets": false,
@@ -96,6 +96,14 @@
       "hasScripts": false
     },
     "app-planner": {
+      "description": "Plan a new application from scratch — vision, tech stack, feature decomposition, and validated feature-list.json.",
+      "tier": "companion",
+      "category": "orchestration-skill",
+      "subcategory": "pipelines",
+      "hasAssets": true,
+      "hasScripts": true
+    },
+    "feature-planner": {
       "description": "Interactive planning for new apps and incremental features; outputs validated feature-list.json for dev-pipeline.",
       "tier": "companion",
       "category": "orchestration-skill",
@@ -103,7 +111,7 @@
       "hasAssets": true,
       "hasScripts": true
     },
-    "dev-pipeline-launcher": {
+    "feature-pipeline-launcher": {
       "description": "Launch and manage the dev-pipeline from within an AI CLI session. Start pipeline in background, monitor logs, check status, stop pipeline.",
       "tier": "companion",
       "category": "orchestration-skill",
@@ -119,6 +127,22 @@
       "hasAssets": false,
       "hasScripts": false
     },
+    "refactor-planner": {
+      "description": "Interactive refactoring planner. Analyzes code structure and produces validated refactor-list.json for dev-pipeline execution.",
+      "tier": "companion",
+      "category": "orchestration-skill",
+      "subcategory": "pipelines",
+      "hasAssets": true,
+      "hasScripts": true
+    },
+    "refactor-pipeline-launcher": {
+      "description": "Launch and manage the refactor pipeline from within an AI CLI session.",
+      "tier": "companion",
+      "category": "orchestration-skill",
+      "subcategory": "pipelines",
+      "hasAssets": false,
+      "hasScripts": false
+    },
     "bug-fix-workflow": {
       "description": "Interactive single-bug fix in current session. Guides triage → reproduce → fix → review → commit without background pipeline.",
       "tier": "companion",
@@ -153,9 +177,12 @@
         "feature-workflow",
         "refactor-workflow",
         "app-planner",
+        "feature-planner",
         "bug-planner",
-        "dev-pipeline-launcher",
+        "feature-pipeline-launcher",
         "bugfix-pipeline-launcher",
+        "refactor-planner",
+        "refactor-pipeline-launcher",
         "bug-fix-workflow",
         "recovery-workflow"
       ]