prizmkit 1.0.20 → 1.0.21

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.20",
-  "bundledAt": "2026-03-15T16:09:11.089Z",
-  "bundledFrom": "4f7e6fe"
+  "frameworkVersion": "1.0.21",
+  "bundledAt": "2026-03-15T16:24:08.378Z",
+  "bundledFrom": "db1bf04"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.20",
+  "version": "1.0.21",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

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

@@ -34,16 +34,20 @@ BROWNFIELD WORKFLOW (existing project):
 
 **Step 1: Project Scanning**
 1. Detect tech stack from build files (`package.json`, `requirements.txt`, `go.mod`, `pom.xml`, `Cargo.toml`, etc.)
-2. Map directory structure — identify source directories, test directories, config files
+2. Map directory structure using a TWO-TIER model — do NOT flatten:
+   - TOP-LEVEL modules: directories directly under project root that contain source files or sub-directories with source files (e.g. `dev-pipeline/`, `src/`, `internal/`)
+   - SUB-MODULES: directories INSIDE a top-level module (e.g. `dev-pipeline/scripts/`, `dev-pipeline/lib/`)
+   - A sub-module is NEVER treated as a top-level module, even if it has many files
+   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `.claude/`, `.codebuddy/`, `.prizmkit/`, `.prizm-docs/`
 3. Identify entry points by language convention
 4. Catalog dependencies (external packages)
 5. Count source files per directory
 
 **Step 2: Prizm Documentation Generation**
-2a. Invoke prizmkit-prizm-docs `prizmkit.doc.init` algorithm:
-  - Create `.prizm-docs/` directory structure
-  - Generate `root.prizm` (L0) with project meta and module index
-  - Generate L1 docs for all discovered modules
+2a. Invoke prizmkit-prizm-docs `prizmkit.doc.init` algorithm, passing the two-tier module structure from Step 1:
+  - Create `.prizm-docs/` directory structure mirroring the source tree (sub-module dirs become subdirectories under `.prizm-docs/<top-level>/`)
+  - Generate `root.prizm` (L0) with project meta and MODULE_INDEX listing ONLY top-level modules
+  - Generate L1 docs for top-level modules at `.prizm-docs/<M>.prizm` and for sub-modules at `.prizm-docs/<M>/<S>.prizm`
   - Create `changelog.prizm`
   - Skip L2 (lazy generation)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.0.20",
+  "version": "1.0.21",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {