prizmkit 1.1.41 → 1.1.46

package/bundled/skills/prizmkit-prizm-docs/assets/prizm-docs-format.md

@@ -3,7 +3,7 @@ PURPOSE: AI-only documentation framework for vibe coding projects
 AUDIENCE: AI agents (not humans)
 FORMAT: KEY: value pairs, ALL CAPS section headers, arrow pointers
 FILE_EXT: .prizm
-DOC_ROOT: .prizm-docs/
+DOC_ROOT: .prizmkit/prizm-docs/
 LICENSE: MIT
 
 ---
@@ -49,27 +49,27 @@ CORE_PRINCIPLES:
 
 LEVELS:
 - L0: Root index. ALWAYS loaded at session start. Max 4KB.
-  FILE: .prizm-docs/root.prizm
+  FILE: .prizmkit/prizm-docs/root.prizm
   CONTAINS: project meta, module index with pointers, build commands, tech stack, top rules
 
 - L1: Structural index. Loaded ON DEMAND when AI works in a module area. Max 4KB each.
-  FILE: .prizm-docs/<mirrored-path>.prizm (mirrors source directory structure)
+  FILE: .prizmkit/prizm-docs/<mirrored-path>.prizm (mirrors source directory structure)
   CONTAINS: module responsibility, subdirs with pointers, key files, dependency graph, critical rules summary (1-3 only)
   DOES NOT CONTAIN: interface signatures, data flow, TRAPS, DECISIONS (those belong in L2)
 
 - L2: Behavioral detail. Loaded when AI modifies files in that module OR needs deep understanding. Max 5KB each.
-  FILE: .prizm-docs/<mirrored-path>/<submodule>.prizm
+  FILE: .prizmkit/prizm-docs/<mirrored-path>/<submodule>.prizm
   CONTAINS: interface signatures, data flow, full rules, TRAPS, DECISIONS, domain-specific sections, rejected approaches
 
 - Changelog: Append-only change log. Loaded at L0. No size limit but keep last 50 entries.
-  FILE: .prizm-docs/changelog.prizm
+  FILE: .prizmkit/prizm-docs/changelog.prizm
 
 ## 2.2 Directory Layout
 
-STRUCTURE: Mirrors source tree under .prizm-docs/
+STRUCTURE: Mirrors source tree under .prizmkit/prizm-docs/
 
 EXAMPLE (Go project):
-  .prizm-docs/
+  .prizmkit/prizm-docs/
     root.prizm                            # L0
     changelog.prizm                       # L0
     internal/
@@ -90,7 +90,7 @@ EXAMPLE (Go project):
         sso.prizm                         # L2 for internal/service/sso/
 
 EXAMPLE (JS/TS project):
-  .prizm-docs/
+  .prizmkit/prizm-docs/
     root.prizm                            # L0
     changelog.prizm                       # L0
     src/
@@ -102,7 +102,7 @@ EXAMPLE (JS/TS project):
         dashboard.prizm                   # L2 for src/components/dashboard/
 
 EXAMPLE (Python project):
-  .prizm-docs/
+  .prizmkit/prizm-docs/
     root.prizm                            # L0
     changelog.prizm                       # L0
     app/
@@ -116,8 +116,8 @@ EXAMPLE (Python project):
 
 ## 2.3 Git Configuration
 
-COMMIT: .prizm-docs/ MUST be committed to git alongside source code
-RATIONALE: .prizm-docs/ is shared project knowledge that all team members (human and AI) benefit from.
+COMMIT: .prizmkit/prizm-docs/ MUST be committed to git alongside source code
+RATIONALE: .prizmkit/prizm-docs/ is shared project knowledge that all team members (human and AI) benefit from.
 
 ---
 
@@ -145,7 +145,7 @@ TEMPLATE:
   - infra: <infrastructure: databases, queues, caches, etc.>
 
   MODULE_INDEX:
-  - <source-path>: <file-count> files. <one-line description>. -> .prizm-docs/<mirrored-path>.prizm
+  - <source-path>: <file-count> files. <one-line description>. -> .prizmkit/prizm-docs/<mirrored-path>.prizm
   (Multi-level entries allowed for efficient navigation. No hard depth limit — constrained by L0 4KB.
    If navigating from L0 to a target module requires 3+ hops, add intermediate entries here.)
 
@@ -162,7 +162,7 @@ TEMPLATE:
 
   CROSS_CUTTING:
   - <concern-name>: <one-line description>. Modules: <affected-module-list>.
-  (Optional: -> .prizm-docs/cross-cutting/<name>.prizm for detailed cross-cutting doc.
+  (Optional: -> .prizmkit/prizm-docs/cross-cutting/<name>.prizm for detailed cross-cutting doc.
    Only record concerns spanning 2+ modules. Single-module patterns go in that module's RULES.)
 
   DECISIONS:
@@ -184,10 +184,10 @@ When MODULE_INDEX would exceed 15 entries, replace it with MODULE_GROUPS to stay
 
   MODULE_GROUPS:
     <domain-name>:
-      - <module>: <file-count> files. <one-line description>. -> .prizm-docs/<module>.prizm
-      - <module>: <file-count> files. <one-line description>. -> .prizm-docs/<module>.prizm
+      - <module>: <file-count> files. <one-line description>. -> .prizmkit/prizm-docs/<module>.prizm
+      - <module>: <file-count> files. <one-line description>. -> .prizmkit/prizm-docs/<module>.prizm
     <domain-name>:
-      - <module>: <file-count> files. <one-line description>. -> .prizm-docs/<module>.prizm
+      - <module>: <file-count> files. <one-line description>. -> .prizmkit/prizm-docs/<module>.prizm
 
 CONSTRAINTS for MODULE_GROUPS:
 - Exactly ONE of MODULE_INDEX or MODULE_GROUPS must be present in root.prizm (not both)
@@ -202,9 +202,9 @@ CONSTRAINTS for MODULE_GROUPS:
 Entries may include keyword tags for AI intent matching:
 
   MODULE_INDEX:
-    - auth [login, session, jwt, oauth]: 12 files. Authentication and authorization. -> .prizm-docs/auth.prizm
-    - payments [stripe, billing, subscription]: 8 files. Payment processing. -> .prizm-docs/payments.prizm
-    - users: 6 files. User management. -> .prizm-docs/users.prizm
+    - auth [login, session, jwt, oauth]: 12 files. Authentication and authorization. -> .prizmkit/prizm-docs/auth.prizm
+    - payments [stripe, billing, subscription]: 8 files. Payment processing. -> .prizmkit/prizm-docs/payments.prizm
+    - users: 6 files. User management. -> .prizmkit/prizm-docs/users.prizm
 
 Tags are optional, enclosed in square brackets after the module name. They contain lowercase keywords that describe the module's domain concepts. AI matches user requirement descriptions against tags to identify relevant modules before loading L1. Tags are auto-generated during Init from module source content (function names, imports, domain terms) and refined during Rebuild.
 
@@ -217,7 +217,7 @@ TEMPLATE:
   RESPONSIBILITY: <one-line>
 
   SUBDIRS:
-  - <name>/: <one-line description>. -> .prizm-docs/<child-path>.prizm
+  - <name>/: <one-line description>. -> .prizmkit/prizm-docs/<child-path>.prizm
 
   KEY_FILES:
   - <filename>: <role/purpose>
@@ -321,7 +321,7 @@ TEMPLATE:
 
 VERBS: add, update, fix, remove, refactor, rename, deprecate
 RETENTION: Keep last 50 entries. Archive older entries to changelog-archive.prizm if needed.
-TEMPORAL_INFO: Git commit history is the authoritative source for when changes happened. No dates in changelog entries — git log on .prizm-docs/changelog.prizm provides the timeline.
+TEMPORAL_INFO: Git commit history is the authoritative source for when changes happened. No dates in changelog entries — git log on .prizmkit/prizm-docs/changelog.prizm provides the timeline.
 
 EXAMPLE:
   CHANGELOG:
@@ -349,28 +349,28 @@ TIMESTAMPS: No date/time fields in .prizm files. Git is the authoritative source
 
 ## 5.1 Mapping Algorithm
 
-RULE: Mirror the source directory tree under .prizm-docs/
-RULE: L1 file for directory D = .prizm-docs/<D>.prizm
-RULE: L2 file for subdirectory D/S = .prizm-docs/<D>/<S>.prizm
-RULE: Root index = .prizm-docs/root.prizm (always)
-RULE: Changelog = .prizm-docs/changelog.prizm (always)
+RULE: Mirror the source directory tree under .prizmkit/prizm-docs/
+RULE: L1 file for directory D = .prizmkit/prizm-docs/<D>.prizm
+RULE: L2 file for subdirectory D/S = .prizmkit/prizm-docs/<D>/<S>.prizm
+RULE: Root index = .prizmkit/prizm-docs/root.prizm (always)
+RULE: Changelog = .prizmkit/prizm-docs/changelog.prizm (always)
 
 ## 5.2 Examples
 
 SOURCE_PATH                   L1_PRIZM_FILE                            L2_PRIZM_FILES
-internal/logic/               .prizm-docs/internal/logic.prizm         .prizm-docs/internal/logic/*.prizm
-internal/logic/session/       (described in L1 logic.prizm SUBDIRS)    .prizm-docs/internal/logic/session.prizm
-internal/repo/store/          (described in L1 repo.prizm SUBDIRS)     .prizm-docs/internal/repo/store.prizm
-src/components/               .prizm-docs/src/components.prizm         .prizm-docs/src/components/*.prizm
-src/components/auth/          (described in L1 components.prizm)       .prizm-docs/src/components/auth.prizm
-app/services/                 .prizm-docs/app/services.prizm           .prizm-docs/app/services/*.prizm
+internal/logic/               .prizmkit/prizm-docs/internal/logic.prizm         .prizmkit/prizm-docs/internal/logic/*.prizm
+internal/logic/session/       (described in L1 logic.prizm SUBDIRS)    .prizmkit/prizm-docs/internal/logic/session.prizm
+internal/repo/store/          (described in L1 repo.prizm SUBDIRS)     .prizmkit/prizm-docs/internal/repo/store.prizm
+src/components/               .prizmkit/prizm-docs/src/components.prizm         .prizmkit/prizm-docs/src/components/*.prizm
+src/components/auth/          (described in L1 components.prizm)       .prizmkit/prizm-docs/src/components/auth.prizm
+app/services/                 .prizmkit/prizm-docs/app/services.prizm           .prizmkit/prizm-docs/app/services/*.prizm
 
 ## 5.3 Discovery Rule
 
 FOR any source file at path P:
-  1. Walk up directory tree to find the first ancestor D where .prizm-docs/<D>.prizm exists
+  1. Walk up directory tree to find the first ancestor D where .prizmkit/prizm-docs/<D>.prizm exists
   2. That file is the L1 doc for this source file
-  3. If P is inside a subdirectory S of D, check if .prizm-docs/<D>/<S>.prizm exists for L2
+  3. If P is inside a subdirectory S of D, check if .prizmkit/prizm-docs/<D>/<S>.prizm exists for L2
   4. If no .prizm doc found, the module is undocumented (may need prizmkit-prizm-docs Update operation)
 
 ---
@@ -380,7 +380,7 @@ FOR any source file at path P:
 ## 6.1 When to Load
 
 ON_SESSION_START:
-  ALWAYS: Read .prizm-docs/root.prizm (L0) if it exists
+  ALWAYS: Read .prizmkit/prizm-docs/root.prizm (L0) if it exists
   PURPOSE: Get the project map, understand architecture, know where to look
 
 ON_TASK_RECEIVED:
@@ -450,7 +450,7 @@ DETAILED_STEPS: → ${SKILL_DIR}/references/op-update.md
 
 ## 7.3 Changelog Update
 
-ALWAYS append to .prizm-docs/changelog.prizm after any doc update.
+ALWAYS append to .prizmkit/prizm-docs/changelog.prizm after any doc update.
 FORMAT: - <module-path> | <verb>: <one-line description>
 VERBS: add, update, fix, remove, refactor, rename, deprecate
 
@@ -481,10 +481,10 @@ NEVER: TRAPS entries without severity prefix ([CRITICAL], [HIGH], or [LOW])
 ## 9.1 Algorithm
 
 OPERATION: Init (invoked via prizmkit-prizm-docs skill)
-PRECONDITION: No .prizm-docs/ directory exists (or user confirms overwrite)
+PRECONDITION: No .prizmkit/prizm-docs/ directory exists (or user confirms overwrite)
 
 INPUT: Project root directory
-OUTPUT: .prizm-docs/ with root.prizm, changelog.prizm, and L1 docs for discovered modules
+OUTPUT: .prizmkit/prizm-docs/ with root.prizm, changelog.prizm, and L1 docs for discovered modules
 
 SUMMARY: Detect project type → discover modules (MODULE_DISCOVERY_CRITERIA) → create mirrored directory structure → generate root.prizm (L0) → generate L1 docs → skip L2 (lazy) → create changelog → configure hook → validate → report.
 
@@ -505,7 +505,7 @@ A directory does NOT qualify if ALL of the following are true:
 
 HIERARCHY RULE: if directory X lives inside top-level module M, X is a sub-module of M — NOT a separate top-level module.
 
-EXCLUDE: .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizm-docs/, dev-pipeline/
+EXCLUDE: .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizmkit/prizm-docs/, dev-pipeline/
 
 ## 9.2 Post-Init Behavior
 
@@ -513,13 +513,13 @@ After initialization, L2 docs are created incrementally:
 
 ON_MODIFY trigger:
 - First time AI modifies a file in sub-module S within module M:
-  IF .prizm-docs/<M>/<S>.prizm does not exist:
+  IF .prizmkit/prizm-docs/<M>/<S>.prizm does not exist:
     AI reads the source files in S, generates L2 doc, then proceeds with modification
 - This ensures L2 docs have real depth, written when AI has actual context
 
 ON_DEEP_READ trigger:
 - When AI needs to deeply understand a module but not modify it (e.g., code review, architecture analysis, dependency tracing, explaining complex logic):
-  IF .prizm-docs/<M>/<S>.prizm does not exist:
+  IF .prizmkit/prizm-docs/<M>/<S>.prizm does not exist:
     AI reads the source files in S, generates L2 doc for future reference
 - This ensures L2 docs are available for read-heavy analysis tasks, not just modifications
 - RATIONALE: Some tasks require deep understanding without editing (reviewing PRs, answering architecture questions, tracing bugs). Generating L2 during these tasks captures valuable context.
@@ -534,12 +534,12 @@ The Prizm skill is defined at: ${SKILL_DIR}/SKILL.md
 
 OPERATIONS (all invoked via the prizmkit-prizm-docs skill):
 
-  Init       - Bootstrap .prizm-docs/ for a new project. → ${SKILL_DIR}/references/op-init.md
+  Init       - Bootstrap .prizmkit/prizm-docs/ for a new project. → ${SKILL_DIR}/references/op-init.md
   Update     - Sync docs with code changes. → ${SKILL_DIR}/references/op-update.md
   Status     - Check freshness of all docs. → ${SKILL_DIR}/references/op-status.md
   Rebuild    - Regenerate docs for a specific module. → ${SKILL_DIR}/references/op-rebuild.md
   Validate   - Check format compliance and consistency. → ${SKILL_DIR}/references/op-validate.md
-  Migrate    - Convert existing docs to .prizm-docs/ format. Steps inline in SKILL.md.
+  Migrate    - Convert existing docs to .prizmkit/prizm-docs/ format. Steps inline in SKILL.md.
 
 ---
 
@@ -566,7 +566,7 @@ JSON:
         "hooks": [
           {
             "type": "command",
-            "command": "echo 'PRIZMKIT_MAINTENANCE_REQUIRED: Before committing, you MUST run /prizmkit-retrospective. It maintains .prizm-docs/ architecture index — structural sync (KEY_FILES, INTERFACES, DEPENDENCIES) + TRAPS/RULES/DECISIONS injection. After retrospective completes, proceed with /prizmkit-committer for the actual git commit.'"
+            "command": "echo 'PRIZMKIT_MAINTENANCE_REQUIRED: Before committing, you MUST run /prizmkit-retrospective. It maintains .prizmkit/prizm-docs/ architecture index — structural sync (KEY_FILES, INTERFACES, DEPENDENCIES) + TRAPS/RULES/DECISIONS injection. After retrospective completes, proceed with /prizmkit-committer for the actual git commit.'"
           }
         ]
       }
@@ -594,7 +594,7 @@ For other AI coding assistants:
 - Continue: Use .continue/config.json customInstructions
 - Generic: Add the auto-update protocol text to whatever system prompt or rules file the tool supports
 
-The core requirement is: before any commit operation, AI must update affected .prizm-docs/ files.
+The core requirement is: before any commit operation, AI must update affected .prizmkit/prizm-docs/ files.
 
 ---
 

package/bundled/skills/prizmkit-prizm-docs/references/op-init.md

@@ -1,8 +1,8 @@
 # Operation: Init — Detailed Steps
 
-Bootstrap .prizm-docs/ for the current project.
+Bootstrap .prizmkit/prizm-docs/ for the current project.
 
-PRECONDITION: No .prizm-docs/ directory exists, or user confirms overwrite.
+PRECONDITION: No .prizmkit/prizm-docs/ directory exists, or user confirms overwrite.
 
 STEPS:
 1. Detect project type by scanning for build system files (go.mod, package.json, requirements.txt, Cargo.toml, pom.xml, *.csproj). Identify primary language, framework, build command, test command, and entry points.
@@ -10,16 +10,16 @@ STEPS:
    - A directory qualifies as a module if it contains source files forming a logical unit, contains entry/config/interface files, contains qualifying sub-modules, or is referenced by multiple modules as a dependency.
    - TOP-LEVEL modules: directories directly under project root (or under src/ for src-based layouts) that qualify.
    - SUB-MODULES: directories INSIDE a top-level module that qualify. Listed in the parent L1 doc's SUBDIRS section.
-   - HIERARCHY RULE: directory X inside top-level module M maps to .prizm-docs/<M>/<X>.prizm, never to .prizm-docs/<X>.prizm.
-   - Exclude .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizm-docs/, dev-pipeline/. If total module count > 30, ask user for include/exclude patterns.
-3. Create .prizm-docs/ directory structure mirroring the source tree exactly. For each top-level module M that has sub-modules, create the subdirectory .prizm-docs/<M>/.
+   - HIERARCHY RULE: directory X inside top-level module M maps to .prizmkit/prizm-docs/<M>/<X>.prizm, never to .prizmkit/prizm-docs/<X>.prizm.
+   - Exclude .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizmkit/prizm-docs/, dev-pipeline/. If total module count > 30, ask user for include/exclude patterns.
+3. Create .prizmkit/prizm-docs/ directory structure mirroring the source tree exactly. For each top-level module M that has sub-modules, create the subdirectory .prizmkit/prizm-docs/<M>/.
 4. Generate root.prizm (L0) with PROJECT, LANG, FRAMEWORK, BUILD, TEST, ENTRY, MODULE_INDEX with multi-level entries as needed for efficient navigation (constrained by 4KB limit), RULES extracted from CODEBUDDY.md/CLAUDE.md/README/linter configs, PATTERNS, and CROSS_CUTTING (cross-module concerns spanning 2+ modules). Set PRIZM_VERSION: 4. Max 4KB. No UPDATED timestamp — git tracks modification times.
    - If `.prizmkit/plans/project-brief.md` exists: add `PROJECT_BRIEF: .prizmkit/plans/project-brief.md` to root.prizm (generated by prizmkit-init). If not present, skip — prizmkit-init Phase 7 will add it later.
    - If module count > 15: use MODULE_GROUPS format instead of MODULE_INDEX — group modules by functional domain (3-8 domains, inferred from directory structure and module responsibilities). See prizm-docs-format.md for MODULE_GROUPS format.
    - For each module entry, auto-generate 3-6 keyword tags by scanning the module's key source files for: exported function/class names, imported library names, domain-specific terms in file/directory names. Add tags in square brackets after the module name (e.g., `- auth [login, session, jwt]: ...`). Tags are optional but recommended for projects with 10+ modules.
 5. Generate L1 .prizm files (structural index only) for ALL modules, each at its correct mirrored path:
-   - Top-level module M → write .prizm-docs/<M>.prizm (include SUBDIRS section with pointers to sub-module docs)
-   - Sub-module S inside M → write .prizm-docs/<M>/<S>.prizm
+   - Top-level module M → write .prizmkit/prizm-docs/<M>.prizm (include SUBDIRS section with pointers to sub-module docs)
+   - Sub-module S inside M → write .prizmkit/prizm-docs/<M>/<S>.prizm
    Each L1 includes MODULE (full relative path), FILES count, RESPONSIBILITY, SUBDIRS with pointers, KEY_FILES (5-10 most important), DEPENDENCIES (imports, imported-by, external), RULES (1-3 most critical only). L1 does NOT include INTERFACES, DATA_FLOW, TRAPS, or DECISIONS (those are L2, generated lazily). Max 4KB each.
 6. Skip L2 docs during init — L2 is created lazily on first file modification or when AI needs deep understanding (ON_DEEP_READ trigger). L2 contains behavioral detail: INTERFACES, DATA_FLOW, TRAPS, DECISIONS, full RULES, domain-specific sections.
 7. Create changelog.prizm with initial entry: `- root | add: initialized prizm documentation framework`
@@ -35,12 +35,12 @@ After initialization, L2 docs are created incrementally:
 
 ON_MODIFY trigger:
 - First time AI modifies a file in sub-module S within module M:
-  IF .prizm-docs/<M>/<S>.prizm does not exist:
+  IF .prizmkit/prizm-docs/<M>/<S>.prizm does not exist:
     AI reads the source files in S, generates L2 doc, then proceeds with modification
 - This ensures L2 docs have real depth, written when AI has actual context
 
 ON_DEEP_READ trigger:
 - When AI needs to deeply understand a module but not modify it (e.g., code review, architecture analysis, dependency tracing, explaining complex logic):
-  IF .prizm-docs/<M>/<S>.prizm does not exist:
+  IF .prizmkit/prizm-docs/<M>/<S>.prizm does not exist:
     AI reads the source files in S, generates L2 doc for future reference
 - This ensures L2 docs are available for read-heavy analysis tasks, not just modifications

package/bundled/skills/prizmkit-prizm-docs/references/op-rebuild.md

@@ -2,7 +2,7 @@
 
 Regenerate docs for a specific module from scratch. Requires a module path argument.
 
-PRECONDITION: .prizm-docs/ exists. Module path is valid.
+PRECONDITION: .prizmkit/prizm-docs/ exists. Module path is valid.
 
 STEPS:
 1. Delete existing L1 and all L2 docs for the specified module.

package/bundled/skills/prizmkit-prizm-docs/references/op-status.md

@@ -2,10 +2,10 @@
 
 Check freshness of all .prizm docs.
 
-PRECONDITION: .prizm-docs/ exists with root.prizm.
+PRECONDITION: .prizmkit/prizm-docs/ exists with root.prizm.
 
 STEPS:
-1. Get last git modification time of root.prizm via `git log -1 --format="%ai" -- .prizm-docs/root.prizm`.
+1. Get last git modification time of root.prizm via `git log -1 --format="%ai" -- .prizmkit/prizm-docs/root.prizm`.
 2. Count commits since that time via `git log --since="<timestamp>" --oneline | wc -l`.
 3. For each L1/L2 doc, compare git modification time of the .prizm file (`git log -1 --format="%ai" -- <prizm-file>`) against latest git modification of source files in that module (`git log -1 --format="%ai" -- <module-path>/`).
 4. Classify each doc as: FRESH (prizm file updated after latest source change), STALE (source changed more recently than prizm file), MISSING (module exists but no .prizm doc).

package/bundled/skills/prizmkit-prizm-docs/references/op-update.md

@@ -1,8 +1,8 @@
 # Operation: Update — Detailed Steps
 
-Update .prizm-docs/ to reflect recent code changes.
+Update .prizmkit/prizm-docs/ to reflect recent code changes.
 
-PRECONDITION: .prizm-docs/ exists with root.prizm.
+PRECONDITION: .prizmkit/prizm-docs/ exists with root.prizm.
 
 STEPS:
 1. Get changed files via `git diff --cached --name-status`. If nothing staged, use `git diff --name-status`. If no git changes at all, do full rescan comparing code against existing docs — this includes checking for modules that have source files but no L2 doc.
@@ -14,6 +14,6 @@ STEPS:
 6a. **L2 gap check** (runs during full rescan mode only — when no git changes detected): For each existing module in MODULE_INDEX, check if L2 doc exists. If L2 is missing and the module has source files with meaningful logic (not trivial config/wrapper) → create L2 with sections: MODULE, FILES, RESPONSIBILITY, INTERFACES, DATA_FLOW, KEY_FILES, DEPENDENCIES, RULES, TRAPS, DECISIONS, CHANGELOG. This ensures Update fills documentation gaps left by previous sessions.
 7. Append entries to changelog.prizm using format: `- <module-path> | <verb>: <description>`
 8. Enforce size limits: L0 > 4KB -> consolidate. L1 > 4KB -> trim KEY_FILES descriptions, ensure RULES <= 3 entries. L2 > 5KB -> split or archive.
-9. Stage updated .prizm files via `git add .prizm-docs/`
+9. Stage updated .prizm files via `git add .prizmkit/prizm-docs/`
 
 OUTPUT: List of updated/created/skipped docs with reasons.

package/bundled/skills/prizmkit-prizm-docs/references/op-validate.md

@@ -2,7 +2,7 @@
 
 Check format compliance and consistency of all .prizm docs.
 
-PRECONDITION: .prizm-docs/ exists.
+PRECONDITION: .prizmkit/prizm-docs/ exists.
 
 STEPS:
 1. FORMAT CHECK: Verify all .prizm files use KEY: value format. Flag any prose paragraphs, code blocks (```), markdown headers (##), emoji, ASCII art, or horizontal rules. Flag TRAPS entries missing severity prefix ([CRITICAL], [HIGH], or [LOW]). Note: [REVIEW] preceding severity (e.g., `[REVIEW][HIGH]`) is a valid temporary staleness marker, not a format violation.

package/bundled/skills/prizmkit-retrospective/SKILL.md

@@ -1,18 +1,18 @@
 ---
 name: "prizmkit-retrospective"
-description: "Incremental .prizm-docs/ maintainer. Performs two jobs: (1) structural sync — update .prizm-docs/ KEY_FILES/INTERFACES/DEPENDENCIES, (2) architecture knowledge — inject TRAPS/RULES/DECISIONS into .prizm-docs/. All project knowledge lives in .prizm-docs/ . Run after code review passes and before committing. Trigger on: 'retrospective', 'retro', 'update docs', 'sync docs', 'wrap up', 'done with feature', 'feature complete'. (project)"
+description: "Incremental .prizmkit/prizm-docs/ maintainer. Performs two jobs: (1) structural sync — update .prizmkit/prizm-docs/ KEY_FILES/INTERFACES/DEPENDENCIES, (2) architecture knowledge — inject TRAPS/RULES/DECISIONS into .prizmkit/prizm-docs/. All project knowledge lives in .prizmkit/prizm-docs/ . Run after code review passes and before committing. Trigger on: 'retrospective', 'retro', 'update docs', 'sync docs', 'wrap up', 'done with feature', 'feature complete'. (project)"
 ---
 
 # PrizmKit Retrospective
 
 | Store | Location | Content | Purpose |
 |-------|----------|---------|---------|
-| **Architecture Index** | `.prizm-docs/` | MODULE, FILES, INTERFACES, DEPENDENCIES, TRAPS, RULES, DECISIONS | AI quickly locates code structure, interfaces, known pitfalls, and key design decisions |
+| **Architecture Index** | `.prizmkit/prizm-docs/` | MODULE, FILES, INTERFACES, DEPENDENCIES, TRAPS, RULES, DECISIONS | AI quickly locates code structure, interfaces, known pitfalls, and key design decisions |
 
 **This skill handles both structural sync and knowledge injection in one pass:**
 
-1. **Structural Sync** — reflect what changed in code → `.prizm-docs/` (KEY_FILES, INTERFACES, DEPENDENCIES, file counts)
-2. **Architecture Knowledge** — inject TRAPS, RULES, and DECISIONS → `.prizm-docs/`
+1. **Structural Sync** — reflect what changed in code → `.prizmkit/prizm-docs/` (KEY_FILES, INTERFACES, DEPENDENCIES, file counts)
+2. **Architecture Knowledge** — inject TRAPS, RULES, and DECISIONS → `.prizmkit/prizm-docs/`
 
 For initial doc setup, validation, or migration, use `/prizmkit-prizm-docs` instead.
 
@@ -38,7 +38,7 @@ For initial doc setup, validation, or migration, use `/prizmkit-prizm-docs` inst
 ---
 
 ### Job 1: Structural Sync (always runs)
-Synchronize `.prizm-docs/` structure with actual codebase changes from this session.
+Synchronize `.prizmkit/prizm-docs/` structure with actual codebase changes from this session.
 → Read `${SKILL_DIR}/references/structural-sync-steps.md` for the detailed procedure.
 
 **Key outputs**: Updated L1 file counts, L2 INTERFACES/DATA_FLOW, changelog entries, stale TRAPS cleanup.
@@ -72,20 +72,20 @@ Inject newly discovered project knowledge (TRAPS, RULES, DECISIONS) into archite
 
 ## Final: Changelog + Stage
 
-**3a.** Append to `.prizm-docs/changelog.prizm`:
+**3a.** Append to `.prizmkit/prizm-docs/changelog.prizm`:
 - Format: `<module-path> | <verb>: <one-line description>`
 - Verbs: add, update, fix, remove, refactor, rename, deprecate
 - One entry per meaningful change, not one per file
 
 **3b.** Stage all doc changes:
 ```bash
-git add .prizm-docs/
+git add .prizmkit/prizm-docs/
 ```
 
 **HANDOFF:** `/prizmkit-committer`
 
 ## Output
 
-- `.prizm-docs/*.prizm` — Structurally synced + TRAPS/RULES/DECISIONS enriched
-- `.prizm-docs/changelog.prizm` — Appended entries
-- All `.prizm-docs/` changes staged via `git add`
+- `.prizmkit/prizm-docs/*.prizm` — Structurally synced + TRAPS/RULES/DECISIONS enriched
+- `.prizmkit/prizm-docs/changelog.prizm` — Appended entries
+- All `.prizmkit/prizm-docs/` changes staged via `git add`

package/bundled/skills/prizmkit-retrospective/references/knowledge-injection-steps.md

@@ -6,7 +6,7 @@
 - `review-report.md` in the artifact directory — read the findings and fix instructions. If this file exists, use it as a source for pre-categorized decisions and findings.
 - `plan.md` in the artifact directory — read planned vs actual
 - Any companion documents in the artifact directory (e.g., `refactor-analysis.md`, `fix-report.md`) — read what was discovered
-- The relevant `.prizm-docs/` L1/L2 docs for affected modules
+- The relevant `.prizmkit/prizm-docs/` L1/L2 docs for affected modules
 
 **2b.** Extract knowledge from what was **observed in code**, not invented:
 
@@ -38,9 +38,9 @@ When writing TRAPS:
 - Only record decisions that a future AI session would benefit from knowing
 - Do NOT record obvious implementation details that can be derived by reading the code
 
-**QUALITY GATE**: Every item must answer: "If a new AI session reads only `.prizm-docs/` and this entry, does it gain actionable understanding?" If not, discard. Do not record trivially observable code patterns — the AI can read the code directly.
+**QUALITY GATE**: Every item must answer: "If a new AI session reads only `.prizmkit/prizm-docs/` and this entry, does it gain actionable understanding?" If not, discard. Do not record trivially observable code patterns — the AI can read the code directly.
 
-**2c.** Inject into the correct `.prizm-docs/` file:
+**2c.** Inject into the correct `.prizmkit/prizm-docs/` file:
 - Module-level TRAPS/RULES/DECISIONS → the affected **L2** `.prizm` file. If the target L2 does not exist, create it first using the L2 GENERATION TEMPLATE before injecting knowledge. (TRAPS/DECISIONS/RULES belong in L2, not L1.)
 - Project-level RULES/PATTERNS → `root.prizm` (respect the current format — MODULE_INDEX or MODULE_GROUPS — do not convert between them during injection)
 - Cross-module concerns spanning 2+ modules → `root.prizm` CROSS_CUTTING section

package/bundled/skills/prizmkit-retrospective/references/structural-sync-steps.md

@@ -5,7 +5,7 @@
 git diff HEAD --name-status
 ```
 
-**1b.** Read `.prizm-docs/root.prizm` to get MODULE_INDEX (or MODULE_GROUPS). Map each changed file to its module.
+**1b.** Read `.prizmkit/prizm-docs/root.prizm` to get MODULE_INDEX (or MODULE_GROUPS). Map each changed file to its module.
 
 **1c.** Classify changes:
 - `A` (added) → add to KEY_FILES, check for new INTERFACES

package/bundled/skills/recovery-workflow/SKILL.md

@@ -27,11 +27,11 @@ User says:
 Pipeline commands (for reference — Phase 1.3 will present these as a selectable option):
 
 ```bash
-./dev-pipeline/run-recovery.sh                    # Auto-detect and recover
-./dev-pipeline/run-recovery.sh detect              # Detection report only
-./dev-pipeline/run-recovery.sh run --dry-run       # Generate prompt, don't execute
-./dev-pipeline/run-recovery.sh run --yes           # Skip confirmation
-./dev-pipeline/run-recovery.sh run --model <model> # Override AI model
+./.prizmkit/dev-pipeline/run-recovery.sh                    # Auto-detect and recover
+./.prizmkit/dev-pipeline/run-recovery.sh detect              # Detection report only
+./.prizmkit/dev-pipeline/run-recovery.sh run --dry-run       # Generate prompt, don't execute
+./.prizmkit/dev-pipeline/run-recovery.sh run --yes           # Skip confirmation
+./.prizmkit/dev-pipeline/run-recovery.sh run --model <model> # Override AI model
 ```
 
 ### When to use pipeline vs interactive recovery
@@ -141,19 +141,19 @@ Before showing the recovery report, run a comprehensive diagnosis:
 2. **Scan all pipelines for failed/in-progress tasks**:
    ```bash
    # Feature pipeline
-   python3 dev-pipeline/scripts/update-feature-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-feature-status.py \
      --feature-list .prizmkit/plans/feature-list.json \
      --state-dir .prizmkit/state/features \
      --action status 2>/dev/null
 
    # Bugfix pipeline
-   python3 dev-pipeline/scripts/update-bug-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-bug-status.py \
      --bug-list .prizmkit/plans/bug-fix-list.json \
      --state-dir .prizmkit/state/bugfix \
      --action status 2>/dev/null
 
    # Refactor pipeline
-   python3 dev-pipeline/scripts/update-refactor-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-refactor-status.py \
      --refactor-list .prizmkit/plans/refactor-list.json \
      --state-dir .prizmkit/state/refactor \
      --action status 2>/dev/null
@@ -259,7 +259,7 @@ AskUserQuestion:
   header: "Recovery"
   options:
     - label: "Run recovery script (Recommended)"
-      description: "Execute ./dev-pipeline/run-recovery.sh — autonomously completes ALL remaining phases (review, commit, merge, etc.) via a dedicated AI session with explicit phase instructions"
+      description: "Execute ./.prizmkit/dev-pipeline/run-recovery.sh — autonomously completes ALL remaining phases (review, commit, merge, etc.) via a dedicated AI session with explicit phase instructions"
     - label: "Copy command and run manually"
       description: "I'll give you the exact shell command to paste into your terminal — you run it yourself outside this session"
     - label: "Resume interactively in this session"
@@ -270,7 +270,7 @@ AskUserQuestion:
 
 **If "Run recovery script"** → Execute the pipeline recovery:
 ```bash
-./dev-pipeline/run-recovery.sh
+./.prizmkit/dev-pipeline/run-recovery.sh
 ```
 The script handles everything: detection, confirmation, prompt generation, session spawn, and post-session validation. **End this skill after launching the script** — do not proceed to Phase 2.
 
@@ -278,12 +278,12 @@ The script handles everything: detection, confirmation, prompt generation, sessi
 ```
 To recover, run this command in your project root:
 
-  ./dev-pipeline/run-recovery.sh
+  ./.prizmkit/dev-pipeline/run-recovery.sh
 
 Or with options:
-  ./dev-pipeline/run-recovery.sh run --dry-run    # Preview the recovery prompt first
-  ./dev-pipeline/run-recovery.sh run --yes         # Skip confirmation
-  ./dev-pipeline/run-recovery.sh run --model <model>  # Specify AI model
+  ./.prizmkit/dev-pipeline/run-recovery.sh run --dry-run    # Preview the recovery prompt first
+  ./.prizmkit/dev-pipeline/run-recovery.sh run --yes         # Skip confirmation
+  ./.prizmkit/dev-pipeline/run-recovery.sh run --model <model>  # Specify AI model
 ```
 **End this skill** — do not proceed to Phase 2. The user will run the command themselves.
 
@@ -312,7 +312,7 @@ End this skill.
    - If `context-snapshot.md` exists in the artifact directory → read it first. It provides a snapshot of completed tasks, key decisions, and remaining work from the interrupted session.
    - If `session-summary.md` exists → read it for a lightweight summary of the previous session.
    - Then read remaining artifacts: spec.md, plan.md, review-report.md, code diffs, bug descriptions, etc.
-3. **Read relevant `.prizm-docs/`** — load project context (L0 root, relevant L1/L2 for affected modules).
+3. **Read relevant `.prizmkit/prizm-docs/`** — load project context (L0 root, relevant L1/L2 for affected modules).
 
 This step replaces the context that was lost when the AI session was interrupted.
 

package/bundled/skills/recovery-workflow/scripts/detect-recovery-state.py

@@ -354,7 +354,6 @@ def detect_code_changes(project_root, main_branch="main"):
     # Note: .prizmkit/plans/*.json paths are caught by IGNORED_PREFIXES below
     IGNORED_PREFIXES = (
         ".prizmkit/",
-        ".prizm-docs/",
         ".claude/",
         ".codebuddy/",
     )