prizmkit 1.0.0 → 1.0.2

package/bundled/templates/codebuddy-md-template.md

@@ -0,0 +1,35 @@
+## PrizmKit Documentation Framework
+
+This project uses PrizmKit with the Prizm documentation system for AI-optimized progressive context loading.
+
+### Progressive Loading Protocol
+- ON SESSION START: Always read `.prizm-docs/root.prizm` first (L0 — project map)
+- ON TASK: Read L1 (`.prizm-docs/<module>.prizm`) for relevant modules referenced in MODULE_INDEX
+- ON FILE EDIT: Read L2 (`.prizm-docs/<module>/<submodule>.prizm`) before modifying files. Pay attention to TRAPS and DECISIONS.
+- NEVER load all .prizm docs at once. Load only what is needed for the current task.
+
+### Auto-Update Protocol
+- BEFORE EVERY COMMIT: Update affected `.prizm-docs/` files
+- The UserPromptSubmit hook will remind you automatically
+- Use `prizmkit-committer` skill for the complete commit workflow
+
+### Doc Format Rules
+- All `.prizm` files use KEY: value format, not prose
+- Size limits: L0 = 4KB, L1 = 3KB, L2 = 5KB
+- Arrow notation (->) indicates load pointers to other .prizm docs
+- DECISIONS and CHANGELOG are append-only (never delete entries)
+
+### Creating New L2 Docs
+- When you first modify files in a sub-module that has no L2 doc:
+  1. Read the source files in that sub-module
+  2. Generate a new L2 `.prizm` file following Prizm specification
+  3. Add a pointer in the parent L1 doc's SUBDIRS section
+
+### Fast Path for Simple Changes
+Not every change needs the full spec -> plan -> tasks workflow. Use fast path for:
+- Bug fixes with clear root cause, config tweaks, typo fixes, simple refactors
+- Documentation-only changes, test additions for existing code
+- Directly use `prizmkit.implement` with inline task description, then `prizmkit.commit`
+
+Use the full workflow (specify -> plan -> tasks -> analyze -> implement) for:
+- New features, multi-file coordinated changes, architectural decisions, data model or API changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {
@@ -13,6 +13,7 @@
   ],
   "scripts": {
     "bundle": "node ../scripts/bundle.js",
+    "prepack": "npm run bundle",
     "dev": "node bin/create-prizmkit.js install . --dry-run",
     "test": "node bin/create-prizmkit.js uninstall . --dry-run"
   },

package/src/scaffold.js

@@ -339,7 +339,7 @@ async function installSettings(platform, projectRoot, options, dryRun) {
             hooks: [
               {
                 type: 'prompt',
-                prompt: 'If this message mentions committing, pushing, or finishing a task, remind about updating .prizm-docs/ first. Suggest using the prizmkit-committer skill.',
+                prompt: 'You are a commit-intent detector for PrizmKit. Analyze the user prompt and determine if the user intends to COMMIT, PUSH, FINISH, SHIP, MERGE, or create a PULL REQUEST.\n\nUser prompt: $ARGUMENTS\n\nIF commit intent detected, respond with:\n{"ok": true, "reason": "PRIZMKIT_DOC_UPDATE_REQUIRED: Before committing, you MUST update .prizm-docs/ per Prizm auto-update protocol. Steps: 1) Run git diff --cached --name-status. 2) Map changed files to modules via root.prizm MODULE_INDEX. 3) Read and update affected .prizm files (only changed sections). 4) Append to changelog.prizm. 5) Stage .prizm files with git add .prizm-docs/. 6) Then proceed with commit using prizmkit-committer workflow. RULES: Never rewrite entire .prizm files. Never add prose. Only update affected sections."}\n\nIF no commit intent, respond with:\n{"ok": true}\n\nRespond with JSON only. No explanation.',
               },
             ],
           },