prizmkit 1.0.99 → 1.0.100

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.99",
-  "bundledAt": "2026-03-23T13:30:18.410Z",
-  "bundledFrom": "df41166"
+  "frameworkVersion": "1.0.100",
+  "bundledAt": "2026-03-23T15:20:23.258Z",
+  "bundledFrom": "e0c5380"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.99",
+  "version": "1.0.100",
   "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

@@ -43,10 +43,10 @@ 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 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. `dev-pipeline/`, `src/`, `internal/`)
-   - SUB-MODULES: directories INSIDE a top-level module (e.g. `dev-pipeline/scripts/`, `dev-pipeline/lib/`)
+   - 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__/`, `.claude/`, `.codebuddy/`, `.prizmkit/`, `.prizm-docs/`
+   - Exclude: `.git/`, `node_modules/`, `vendor/`, `build/`, `dist/`, `__pycache__/`, `target/`, `bin/`, `.claude/`, `.codebuddy/`, `.prizmkit/`, `.prizm-docs/`, `dev-pipeline/`
 3. Identify entry points by language convention
 4. Catalog dependencies (external packages)
 5. Count source files per directory

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

@@ -48,7 +48,7 @@ STEPS:
    - TOP-LEVEL modules: directories directly under project root (or under src/ for src-based layouts) that contain 3+ source files OR contain sub-directories with 3+ source files. These go into MODULE_INDEX.
    - SUB-MODULES: directories INSIDE a top-level module that contain 3+ source files. Listed in the parent L1 doc's SUBDIRS section only.
    - HIERARCHY RULE: directory X inside top-level module M maps to .prizm-docs/<M>/<X>.prizm, never to .prizm-docs/<X>.prizm.
-   - Exclude vendor/, node_modules/, .git/, build/, dist/, __pycache__/, target/, bin/. If top-level module count > 30, ask user for include/exclude patterns.
+   - Exclude .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizm-docs/, dev-pipeline/. If top-level 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>/.
 4. Generate root.prizm (L0) with PROJECT, LANG, FRAMEWORK, BUILD, TEST, ENTRY, MODULE_INDEX listing only top-level modules with arrow pointers to .prizm-docs/<M>.prizm (sub-modules stay out of MODULE_INDEX to keep L0 compact and within the 4KB limit), RULES extracted from CODEBUDDY.md/CLAUDE.md/README/linter configs, and PATTERNS. Set PRIZM_VERSION: 2, UPDATED: today's date. Max 4KB.
 5. Generate L1 .prizm files for ALL modules (top-level and sub-modules), each at its correct mirrored path:

package/bundled/skills/prizmkit-prizm-docs/assets/PRIZM-SPEC.md

@@ -479,19 +479,19 @@ STEPS:
    a. IDENTIFY TOP-LEVEL modules: directories directly under project root (or directly under src/ for src-based layouts) that either:
       - Contain 3+ source files of the primary language, OR
       - Contain sub-directories that each have 3+ source files
-      RESULT: top_modules = [dev-pipeline, src, internal, app, ...]
+      RESULT: top_modules = [src, internal, app, lib, ...]
 
    b. IDENTIFY SUB-MODULES: for each top-level module M, find directories INSIDE M that contain 3+ source files
       RESULT: sub_modules[M] = [scripts, lib, templates, ...]  (relative names, not full paths)
 
    c. HIERARCHY RULE: if directory X lives inside top-level module M, X is a sub-module of M — NOT a separate top-level module.
-      WRONG: dev-pipeline/scripts/ treated as top-level module -> .prizm-docs/scripts.prizm
-      CORRECT: dev-pipeline/scripts/ is a sub-module of dev-pipeline -> .prizm-docs/dev-pipeline/scripts.prizm
+      WRONG: src/routes/ treated as top-level module -> .prizm-docs/routes.prizm
+      CORRECT: src/routes/ is a sub-module of src -> .prizm-docs/src/routes.prizm
 
    d. MODULE_INDEX in root.prizm lists ONLY top-level modules from step 2a.
       Sub-modules appear in their parent's L1 doc SUBDIRS section, not in MODULE_INDEX.
 
-   - EXCLUDE: vendor/, node_modules/, .git/, build/, dist/, __pycache__/, target/, bin/
+   - EXCLUDE: .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizm-docs/, dev-pipeline/
    IF top-level module count > 30: ASK user for include/exclude patterns
 
 3. CREATE_DIRECTORY_STRUCTURE:
@@ -499,10 +499,10 @@ STEPS:
    For each top-level module M that has sub-modules: create .prizm-docs/<M>/ directory
    RULE: .prizm-docs/ directory tree must mirror the source directory tree exactly
    EXAMPLE:
-     source: dev-pipeline/scripts/  -> prizm: .prizm-docs/dev-pipeline/scripts.prizm
-     source: dev-pipeline/lib/      -> prizm: .prizm-docs/dev-pipeline/lib.prizm
-     source: dev-pipeline/          -> prizm: .prizm-docs/dev-pipeline.prizm
-   NEVER create .prizm-docs/scripts.prizm for a directory that lives at dev-pipeline/scripts/
+     source: src/routes/     -> prizm: .prizm-docs/src/routes.prizm
+     source: src/models/     -> prizm: .prizm-docs/src/models.prizm
+     source: src/            -> prizm: .prizm-docs/src.prizm
+   NEVER create .prizm-docs/routes.prizm for a directory that lives at src/routes/
 
 4. GENERATE_ROOT (L0):
    Fill: PROJECT, LANG, FRAMEWORK, BUILD, TEST, ENTRY from step 1

package/package.json

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