prizmkit 1.1.42 → 1.1.47

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

@@ -1,6 +1,6 @@
 ---
 name: "prizmkit-init"
-description: "Project takeover and bootstrap. Scans any project, generates Prizm docs and project brief. Use this skill whenever a user opens a new project for the first time, says 'initialize', 'set up PrizmKit', 'take over this project', 'bootstrap', 'scan this codebase', 'init', or when .prizm-docs/ doesn't exist yet. Also use when PrizmKit was just installed via npx but not yet initialized. (project)"
+description: "Project takeover and bootstrap. Scans any project, generates Prizm docs and project brief. Use this skill whenever a user opens a new project for the first time, says 'initialize', 'set up PrizmKit', 'take over this project', 'bootstrap', 'scan this codebase', 'init', or when .prizmkit/prizm-docs/ doesn't exist yet. Also use when PrizmKit was just installed via npx but not yet initialized. (project)"
 ---
 
 # PrizmKit Init
@@ -11,7 +11,7 @@ Project takeover and bootstrap skill. Scans any project (brownfield or greenfiel
 - Taking over a new project (brownfield or greenfield)
 - User says "initialize PrizmKit", "set up PrizmKit", "take over this project"
 - First time using PrizmKit on a project
-- After `npx prizmkit install` when project has no `.prizm-docs/`
+- After `npx prizmkit install` when project has no `.prizmkit/prizm-docs/`
 
 ### When NOT to Use
 - All artifacts exist and are up to date → use `/prizmkit-prizm-docs` (Update) instead if you only want to resync docs
@@ -38,14 +38,14 @@ Scan all init artifacts and display their status:
 
 | Artifact | Path | Check |
 |----------|------|-------|
-| Prizm docs | `.prizm-docs/` | Directory exists + `root.prizm` present |
+| Prizm docs | `.prizmkit/prizm-docs/` | Directory exists + `root.prizm` present |
 | Runtime config | `.prizmkit/config.json` | File exists |
 | Project brief | `.prizmkit/plans/project-brief.md` | File exists |
 
 Display status table to user:
 ```
 Init Status Check:
-  [exists]  .prizm-docs/          (N files)
+  [exists]  .prizmkit/prizm-docs/          (N files)
   [exists]  .prizmkit/config.json
   [missing] .prizmkit/plans/project-brief.md
 ```
@@ -59,7 +59,7 @@ Init Status Check:
 Each subsequent phase checks its artifact's action before executing:
 - `action == skip` → output "Skipped (exists)" and move on
 - `action == generate | regenerate` → run normally
-- **Special case for `.prizm-docs/`**:
+- **Special case for `.prizmkit/prizm-docs/`**:
   - `skip` = **Update** mode: preserve existing L1/L2 docs, re-scan tech stack, merge changes, check for missing docs (see `${SKILL_DIR}/references/update-supplement.md`)
   - `regenerate` = **Reinitialize**: overwrite everything
 
@@ -70,8 +70,8 @@ BROWNFIELD WORKFLOW (existing project):
 2. Map directory structure using a TWO-TIER model — flat structures lose the nesting relationships that AI needs to navigate the codebase:
    - TOP-LEVEL modules: directories directly under project root that contain source files or sub-directories with source files (e.g. `src/`, `internal/`, `lib/`)
    - SUB-MODULES: directories INSIDE a top-level module (e.g. `src/routes/`, `src/models/`)
-   - A sub-module maps to `.prizm-docs/<M>/<S>.prizm`, never to `.prizm-docs/<S>.prizm` — flattening would create ambiguous paths when two modules have identically-named sub-modules
-   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.claude/`, `.codebuddy/`, `.prizmkit/`, `.prizm-docs/`, `dev-pipeline/`
+   - A sub-module maps to `.prizmkit/prizm-docs/<M>/<S>.prizm`, never to `.prizmkit/prizm-docs/<S>.prizm` — flattening would create ambiguous paths when two modules have identically-named sub-modules
+   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.claude/`, `.codebuddy/`, `.prizmkit/`
    - **Scan command** — run this to get a 2-level directory tree (excludes noise directories):
      ```bash
      find . -maxdepth 2 -type d \
@@ -79,8 +79,7 @@ BROWNFIELD WORKFLOW (existing project):
        -not -path '*/dist/*' -not -path '*/build/*' \
        -not -path '*/__pycache__/*' -not -path '*/vendor/*' \
        -not -path '*/.claude/*' -not -path '*/.codebuddy/*' \
-       -not -path '*/.prizmkit/*' -not -path '*/.prizm-docs/*' \
-       -not -path '*/dev-pipeline/*' -not -path '*/target/*' \
+       -not -path '*/.prizmkit/*' -not -path '*/target/*' \
        | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
      ```
 3. Identify entry points by language convention
@@ -151,10 +150,10 @@ Detect database and deployment signals, then ask 1-2 brief questions. This phase
 
 **Phase 5: Prizm Documentation Generation**
 Invoke prizmkit-prizm-docs (Init operation), passing the two-tier module structure from Phase 4:
-  - Create `.prizm-docs/` directory structure mirroring the source tree (sub-module dirs become subdirectories under `.prizm-docs/<top-level>/`)
+  - Create `.prizmkit/prizm-docs/` directory structure mirroring the source tree (sub-module dirs become subdirectories under `.prizmkit/prizm-docs/<top-level>/`)
   - Generate `root.prizm` (L0) with project meta and MODULE_INDEX listing only top-level modules. If module count > 15, use MODULE_GROUPS format instead (group by functional domain).
   - For each module entry in MODULE_INDEX/MODULE_GROUPS, include keyword tags extracted from the module's source files — scan for: exported symbols, imported packages, domain terms in file/directory names. Format: `- module-name [tag1, tag2, tag3]: ...`. Tags help AI match user intent to relevant modules.
-  - Generate L1 docs for top-level modules at `.prizm-docs/<M>.prizm` and for sub-modules at `.prizm-docs/<M>/<S>.prizm`
+  - Generate L1 docs for top-level modules at `.prizmkit/prizm-docs/<M>.prizm` and for sub-modules at `.prizmkit/prizm-docs/<M>/<S>.prizm`
   - Create `changelog.prizm`
   - Skip L2 (lazy generation) — L2 is generated on first file modification, saving tokens upfront
 
@@ -231,7 +230,7 @@ GREENFIELD WORKFLOW (new project):
   - Record answers in `config.json` `tech_stack` with `"_auto_detected": false` (user-provided, not auto-detected)
   - If user is unsure, skip tech_stack — it can be populated later on re-init after code exists
 - Phase 4.5: Run Infrastructure Quick Scan — in greenfield mode, no auto-detection is possible, so only ask the 2 brief questions (database need and deployment target). If user is unsure, skip — these can be configured later via `app-planner` or `/prizmkit-deploy`.
-- Phase 5: Create minimal `.prizm-docs/` with just `root.prizm` skeleton (populate TECH_STACK from user answers if provided)
+- Phase 5: Create minimal `.prizmkit/prizm-docs/` with just `root.prizm` skeleton (populate TECH_STACK from user answers if provided)
 - Phase 7: Generate project brief (greenfield flow — ask user about project goals, see Phase 7 above)
 - Phases 6, 8: Same as brownfield (Phase 8 Report recommends `/prizmkit-plan` for first feature)
 
@@ -243,7 +242,7 @@ $ /prizmkit-init
 
 Platform detected: Claude Code
 Init Status Check:
-  [missing] .prizm-docs/
+  [missing] .prizmkit/prizm-docs/
   [missing] .prizmkit/config.json
   [missing] .prizmkit/plans/project-brief.md
 → All missing, generating everything.
@@ -266,10 +265,10 @@ Infrastructure Quick Scan:
   → Written to CLAUDE.md ### Infrastructure
 
 Modules discovered:
-  src/routes/     → .prizm-docs/routes.prizm (12 files)
-  src/models/     → .prizm-docs/models.prizm (8 files)
-  src/services/   → .prizm-docs/services.prizm (15 files)
-  src/middleware/  → .prizm-docs/middleware.prizm (5 files)
+  src/routes/     → .prizmkit/prizm-docs/routes.prizm (12 files)
+  src/models/     → .prizmkit/prizm-docs/models.prizm (8 files)
+  src/services/   → .prizmkit/prizm-docs/services.prizm (15 files)
+  src/middleware/  → .prizmkit/prizm-docs/middleware.prizm (5 files)
 
 Project brief: inferred from codebase → confirmed by user
   → .prizmkit/plans/project-brief.md
@@ -288,7 +287,7 @@ UPDATE SUPPLEMENT (runs after tech stack merge in Update mode):
 $ /prizmkit-init
 
 Init Status Check:
-  [exists]  .prizm-docs/          (12 files)
+  [exists]  .prizmkit/prizm-docs/          (12 files)
   [exists]  .prizmkit/config.json
   [missing] .prizmkit/plans/project-brief.md
 

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

@@ -36,7 +36,7 @@ A universal spec + plan generator. Takes a natural-language description of ANY d
    - If `artifact_dir` is provided → use it directly
    - If not provided → scan `.prizmkit/specs/` for existing `###-*` directories, find highest numeric prefix, next = highest + 1 (zero-padded to 3 digits; start at `001` if empty). Create `.prizmkit/specs/###-task-slug/`
    - Auto-generate 2-10 word task slug from description
-3. Load project context: read `.prizm-docs/root.prizm` and relevant L1/L2 docs
+3. Load project context: read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 docs
 4. Generate `spec.md` from template (`${SKILL_DIR}/assets/spec-template.md`):
    - Fill sections based on the task description — all sections are optional, include only what is relevant
    - `[NEEDS CLARIFICATION]` markers for all ambiguous items
@@ -56,7 +56,7 @@ A universal spec + plan generator. Takes a natural-language description of ANY d
 **Steps:**
 
 1. Read `spec.md` from the artifact directory
-2. Load project context if not already loaded in Phase 0: read `.prizm-docs/root.prizm` and relevant L1/L2 docs
+2. Load project context if not already loaded in Phase 0: read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 docs
 3. Resolve any remaining `[NEEDS CLARIFICATION]` by proposing solutions
 4. Generate `plan.md` from template (`${SKILL_DIR}/assets/plan-template.md`):
    - Change approach (how the changes integrate with existing system)
@@ -67,7 +67,7 @@ A universal spec + plan generator. Takes a natural-language description of ANY d
    - Risk assessment
    - Behavior preservation strategy (if the task modifies existing behavior — include what must remain unchanged and how to verify)
 5. Cross-check: every goal in spec.md maps to plan components — unmapped goals = coverage gaps
-6. Check alignment with `.prizm-docs/root.prizm` RULES section
+6. Check alignment with `.prizmkit/prizm-docs/root.prizm` RULES section
 
 ### Phase 2: Task Generation (plan.md → Tasks section)
 

package/bundled/skills/prizmkit-plan/references/verification-checklist.md

@@ -40,8 +40,8 @@ Run this checklist after generating the Tasks section in plan.md. Fix any issues
 
 ## Rules Alignment
 
-- [ ] No spec or plan element conflicts with `.prizm-docs/root.prizm` RULES MUST/NEVER directives
-- [ ] Tech stack choices in plan.md match `.prizm-docs/root.prizm` TECH_STACK (if defined)
+- [ ] No spec or plan element conflicts with `.prizmkit/prizm-docs/root.prizm` RULES MUST/NEVER directives
+- [ ] Tech stack choices in plan.md match `.prizmkit/prizm-docs/root.prizm` TECH_STACK (if defined)
 
 ## Database Design (skip if no Data Model section)
 

package/bundled/skills/prizmkit-prizm-docs/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "prizmkit-prizm-docs"
-description: "Project documentation specification and standard for AI-optimized progressive context loading. Defines the .prizm-docs/ 3-level hierarchy (L0/L1/L2), format rules, size limits, and loading protocol. Use this skill to: bootstrap docs for new projects (init), check doc freshness (status), regenerate stale modules (rebuild), validate format compliance (validate), or migrate existing docs (migrate). For incremental doc updates after code changes, use /prizmkit-retrospective instead — it is the sole writer of .prizm-docs/ during development. Trigger on: 'initialize docs', 'check doc status', 'rebuild docs', 'validate docs', 'migrate docs', 'docs are stale', 'prizm docs'. (project)"
+description: "Project documentation specification and standard for AI-optimized progressive context loading. Defines the .prizmkit/prizm-docs/ 3-level hierarchy (L0/L1/L2), format rules, size limits, and loading protocol. Use this skill to: bootstrap docs for new projects (init), check doc freshness (status), regenerate stale modules (rebuild), validate format compliance (validate), or migrate existing docs (migrate). For incremental doc updates after code changes, use /prizmkit-retrospective instead — it is the sole writer of .prizmkit/prizm-docs/ during development. Trigger on: 'initialize docs', 'check doc status', 'rebuild docs', 'validate docs', 'migrate docs', 'docs are stale', 'prizm docs'. (project)"
 ---
 
 # Prizm Docs - AI Documentation Framework
@@ -30,53 +30,53 @@ This skill handles 6 operations. When invoked, determine the user's intent and e
 |--------|----------------------|--------------------------|
 | **Role** | Documentation SPECIFICATION + BOOTSTRAP | Incremental WRITER during development |
 | **When** | Project setup, health checks, migrations | After feature completion, before commit |
-| **Writes** | Initial .prizm-docs/ structure (init, rebuild, migrate) | Incremental updates to existing .prizm-docs/ |
+| **Writes** | Initial .prizmkit/prizm-docs/ structure (init, rebuild, migrate) | Incremental updates to existing .prizmkit/prizm-docs/ |
 | **Reads** | Source code structure (for init/rebuild) | git diff + code changes (for sync) |
-| **Knowledge** | Defines format rules, size limits, loading protocol | Extracts TRAPS/RULES/DECISIONS into `.prizm-docs/` |
+| **Knowledge** | Defines format rules, size limits, loading protocol | Extracts TRAPS/RULES/DECISIONS into `.prizmkit/prizm-docs/` |
 
 **Key principle**: `/prizmkit-prizm-docs` defines WHAT the docs should look like and bootstraps them. `/prizmkit-retrospective` is the SOLE WRITER that keeps docs in sync with code during ongoing development.
 
 ## Operation: Init
 
-Bootstrap .prizm-docs/ for the current project.
-PRECONDITION: No .prizm-docs/ directory exists, or user confirms overwrite.
+Bootstrap .prizmkit/prizm-docs/ for the current project.
+PRECONDITION: No .prizmkit/prizm-docs/ directory exists, or user confirms overwrite.
 → Read `${SKILL_DIR}/references/op-init.md` for detailed steps.
 
 ## Operation: Update
 
-Update .prizm-docs/ to reflect recent code changes.
-PRECONDITION: .prizm-docs/ exists with root.prizm.
+Update .prizmkit/prizm-docs/ to reflect recent code changes.
+PRECONDITION: .prizmkit/prizm-docs/ exists with root.prizm.
 → Read `${SKILL_DIR}/references/op-update.md` for detailed steps.
 
 ## Operation: Status
 
 Check freshness of all .prizm docs.
-PRECONDITION: .prizm-docs/ exists with root.prizm.
+PRECONDITION: .prizmkit/prizm-docs/ exists with root.prizm.
 → Read `${SKILL_DIR}/references/op-status.md` for detailed steps.
 
 ## Operation: Rebuild
 
 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.
 → Read `${SKILL_DIR}/references/op-rebuild.md` for detailed steps.
 
 ## Operation: Validate
 
 Check format compliance and consistency of all .prizm docs.
-PRECONDITION: .prizm-docs/ exists.
+PRECONDITION: .prizmkit/prizm-docs/ exists.
 → Read `${SKILL_DIR}/references/op-validate.md` for detailed steps.
 
 ## Operation: Migrate
 
-Convert existing documentation to .prizm-docs/ format.
-PRECONDITION: Existing docs/ or docs/AI_CONTEXT/ directory. No .prizm-docs/ (or user confirms overwrite).
+Convert existing documentation to .prizmkit/prizm-docs/ format.
+PRECONDITION: Existing docs/ or docs/AI_CONTEXT/ directory. No .prizmkit/prizm-docs/ (or user confirms overwrite).
 
 STEPS:
 1. DISCOVER existing docs: Scan docs/, docs/AI_CONTEXT/, README.md, ARCHITECTURE.md, and any structured documentation files.
 2. EXTRACT information from existing docs: project metadata, module descriptions, architecture patterns, rules, decisions, dependencies.
 3. MAP existing doc content to Prizm levels: project-wide info -> L0 root.prizm, module-level info -> L1 docs (MODULE, FILES, RESPONSIBILITY, KEY_FILES, DEPENDENCIES), detailed module info -> L2 docs (INTERFACES, DATA_FLOW, TRAPS, DECISIONS, domain-specific sections).
 4. CONVERT prose content to KEY: value format. Strip markdown formatting, tables, diagrams. Condense explanatory text into single-line values.
-5. GENERATE .prizm-docs/ structure following standard init procedure but seeded with extracted information instead of scanning source code alone.
+5. GENERATE .prizmkit/prizm-docs/ structure following standard init procedure but seeded with extracted information instead of scanning source code alone.
 6. VALIDATE migrated docs against Prizm format rules and size limits.
 7. REPORT migration summary: files processed, content mapped, information that could not be automatically converted (requires manual review).
 
@@ -99,7 +99,7 @@ For detailed protocol specifications, see prizm-docs-format.md:
 
 **Init output (Node.js project):**
 ```
-Generated .prizm-docs/:
+Generated .prizmkit/prizm-docs/:
   root.prizm (L0) — 3 modules in MODULE_INDEX
   routes.prizm (L1) — 12 files, 4 interfaces
   models.prizm (L1) — 8 files, 3 interfaces
@@ -110,8 +110,8 @@ Generated .prizm-docs/:
 **Update after adding new API endpoint:**
 ```
 Changed: src/routes/avatar.ts (A), src/models/user.ts (M)
-Updated: .prizm-docs/routes.prizm — added avatar.ts to KEY_FILES, new POST /api/avatar interface
-Updated: .prizm-docs/models.prizm — updated User interface with avatar_url field
-Skipped: .prizm-docs/services.prizm — no changes in services module
+Updated: .prizmkit/prizm-docs/routes.prizm — added avatar.ts to KEY_FILES, new POST /api/avatar interface
+Updated: .prizmkit/prizm-docs/models.prizm — updated User interface with avatar_url field
+Skipped: .prizmkit/prizm-docs/services.prizm — no changes in services module
 Appended: changelog.prizm — "routes | add: avatar upload endpoint"
 ```

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.