prizmkit 1.0.149 → 1.0.150

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.149",
-  "bundledAt": "2026-03-31T17:50:05.806Z",
-  "bundledFrom": "9c1abf7"
+  "frameworkVersion": "1.0.150",
+  "bundledAt": "2026-03-31T17:59:38.986Z",
+  "bundledFrom": "51bf160"
 }

package/bundled/adapters/claude/command-adapter.js

@@ -11,7 +11,7 @@
 
 import { parseFrontmatter, buildMarkdown } from '../shared/frontmatter.js';
 import { COMMANDS_DIR } from './paths.js';
-import { existsSync, mkdirSync, cpSync } from 'node:fs';
+import { existsSync, mkdirSync, cpSync, readdirSync } from 'node:fs';
 import { readFile, writeFile } from 'node:fs/promises';
 import path from 'path';
 
@@ -100,12 +100,13 @@ export function convertSkillToCommand(skillContent, skillName) {
  */
 export async function installCommand(corePath, targetRoot) {
   const skillName = path.basename(corePath);
-  const hasAssets = existsSync(path.join(corePath, 'assets'));
-  const hasScripts = existsSync(path.join(corePath, 'scripts'));
-  const hasRules = existsSync(path.join(corePath, 'rules'));
-  const hasReferences = existsSync(path.join(corePath, 'references'));
 
-  if (hasAssets || hasScripts || hasRules || hasReferences) {
+  // Discover all subdirectories in the skill
+  const subdirs = existsSync(corePath)
+    ? readdirSync(corePath, { withFileTypes: true }).filter(e => e.isDirectory()).map(e => e.name)
+    : [];
+
+  if (subdirs.length > 0) {
     // Use directory structure for commands with resources
     const targetDir = path.join(targetRoot, COMMANDS_DIR, skillName);
     mkdirSync(targetDir, { recursive: true });
@@ -118,12 +119,9 @@ export async function installCommand(corePath, targetRoot) {
       await writeFile(path.join(targetDir, `${skillName}.md`), converted);
     }
 
-    // Copy assets and scripts
-    for (const subdir of ['scripts', 'assets', 'rules', 'references']) {
-      const srcSubdir = path.join(corePath, subdir);
-      if (existsSync(srcSubdir)) {
-        cpSync(srcSubdir, path.join(targetDir, subdir), { recursive: true });
-      }
+    // Copy all subdirectories
+    for (const subdir of subdirs) {
+      cpSync(path.join(corePath, subdir), path.join(targetDir, subdir), { recursive: true });
     }
   } else {
     // Single file command

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.149",
+  "version": "1.0.150",
   "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/app-planner/SKILL.md

@@ -58,23 +58,21 @@ Do NOT use this skill when the user only wants to run the pipeline (`dev-pipelin
 
 ## Resource Loading Rules (Mandatory)
 
-`SKILL_DIR` definition:
-- `SKILL_DIR` is the absolute path of this skill directory.
 1. **Choose scenario reference before planning**:
-   - New app → read `references/new-app-planning.md`
-   - Existing app incremental features → read `references/incremental-feature-planning.md`
+   - New app → read `${SKILL_DIR}/references/new-app-planning.md`
+   - Existing app incremental features → read `${SKILL_DIR}/references/incremental-feature-planning.md`
 
 2. **Use shared quality examples as needed**:
-   - read `assets/planning-guide.md` for decomposition and acceptance criteria patterns
+   - read `${SKILL_DIR}/assets/planning-guide.md` for decomposition and acceptance criteria patterns
 
 3. **Load on-demand references when triggered**:
-   - Validation errors or interrupted session → read `references/error-recovery.md`
-   - Architecture decisions emerged → read `references/architecture-decisions.md`
-   - Browser interaction fields needed → read `references/browser-interaction.md`
+   - Validation errors or interrupted session → read `${SKILL_DIR}/references/error-recovery.md`
+   - Architecture decisions emerged → read `${SKILL_DIR}/references/architecture-decisions.md`
+   - Browser interaction fields needed → read `${SKILL_DIR}/references/browser-interaction.md`
 
 4. **Brainstorm deep-dive** — If the user chooses to continue discussing or exploring ideas before finalizing features (e.g., during Intent Confirmation the user selects "just explore ideas", or at any point says "let's discuss more" / "I want to think through this"):
-   → read `references/brainstorm-guide.md` and follow its four-phase structured ideation process (Assess Clarity → Understand → Explore Approaches → Capture Design)
-   → During Phase C (Explore Approaches), also read `references/red-team-checklist.md` for adversarial critique of each approach
+   → read `${SKILL_DIR}/references/brainstorm-guide.md` and follow its four-phase structured ideation process (Assess Clarity → Understand → Explore Approaches → Capture Design)
+   → During Phase C (Explore Approaches), also read `${SKILL_DIR}/references/red-team-checklist.md` for adversarial critique of each approach
    → When brainstorm Phase D produces a "Capture Design" summary, use it as the Vision Summary (fulfilling CP-AP-2) and proceed to Phase 2 (constraints and tech assumptions)
 
 5. **Frontend / UI design check** — Evaluate during Phase 2 (constraints and tech assumptions), after tech stack is confirmed. If the project has a frontend framework:
@@ -82,17 +80,17 @@ Do NOT use this skill when the user only wants to run the pipeline (`dev-pipelin
    → Also search the active CLI's project instruction file (`CLAUDE.md` / `CODEBUDDY.md`) for keywords: "UI", "UX", "design system", "style guide", "theme", "typography", "color palette"
    → If unified design guidance is found → use it as constraint for feature descriptions
    → If NO unified design guidance found → ask user: "项目中未找到统一的 UI/UX 设计规范。是否需要在特性规划前先建立一套 UI/UX 设计方向？(No unified UI/UX design system found. Would you like to establish one before feature planning?)"
-   → If yes → read `references/frontend-design-guide.md` and conduct a design direction session. Capture the result in the project instruction file (with user consent).
+   → If yes → read `${SKILL_DIR}/references/frontend-design-guide.md` and conduct a design direction session. Capture the result in the project instruction file (with user consent).
    → If no → proceed without; individual features may still define their own UI approach.
 
 6. **Project conventions check** — After Intent Confirmation (CP-AP-0), before brainstorm or Phase 1 vision work. This runs regardless of session goal (produce or explore):
    → Read `.prizmkit/project-conventions.json` if it exists
    → If the file exists but cannot be parsed as valid JSON → warn user ("conventions file is corrupted, will re-ask all questions"), treat all conventions as unanswered
-   → Cross-reference with `references/project-conventions.md` for the full question list
+   → Cross-reference with `${SKILL_DIR}/references/project-conventions.md` for the full question list
    → For any convention with a `null` or missing value → batch all unanswered questions into a single prompt to the user
    → Save answers to `.prizmkit/project-conventions.json` (create `.prizmkit/` directory if needed — this is an allowed writable output)
    → If all conventions are already answered → skip silently, do not re-ask
-   → Use convention answers as context when writing feature descriptions and proposing features (see `references/project-conventions.md` §How Conventions Are Used)
+   → Use convention answers as context when writing feature descriptions and proposing features (see `${SKILL_DIR}/references/project-conventions.md` §How Conventions Are Used)
 
 7. **Always validate output via script**:
    - run:
@@ -134,7 +132,7 @@ Classify user intent first:
 Use when user starts from idea/blank slate or asks for initial end-to-end plan.
 
 Actions:
-1. Load `references/new-app-planning.md`
+1. Load `${SKILL_DIR}/references/new-app-planning.md`
 2. Run interactive planning phases
 3. Generate initial `feature-list.json`
 
@@ -142,7 +140,7 @@ Actions:
 Use when user already has app/code/plan and asks to add or adjust features.
 
 Actions:
-1. Load `references/incremental-feature-planning.md`
+1. Load `${SKILL_DIR}/references/incremental-feature-planning.md`
 2. Read existing `feature-list.json` first (if missing, ask whether to start new plan)
 3. Append features with next sequential `F-NNN` IDs
 4. Preserve style/language/detail consistency with existing plan
@@ -159,7 +157,7 @@ After scenario routing, immediately confirm the user's deliverable intent:
    - **"Produce feature-list.json"** → Continue to Core Workflow. Set session goal = `produce`.
    - **"Just explore ideas"** → Enter **Exploration Mode**:
      - Run project conventions check first (CP-AP-1) — same as produce mode
-     - Load `references/brainstorm-guide.md` and follow its structured ideation process (Phases A-D)
+     - Load `${SKILL_DIR}/references/brainstorm-guide.md` and follow its structured ideation process (Phases A-D)
      - Brainstorm Phase D output serves as the Vision Summary (CP-AP-2)
      - Continue with Phase 2 (constraints — including frontend design check CP-AP-3 if applicable), then Phases 3-5 normally
      - At Phase 5 completion, re-ask: "Ideas are taking shape. Ready to generate `feature-list.json` now?"
@@ -206,11 +204,11 @@ Note: Checkpoint numbers (CP-AP-N) are sequential identifiers for the gate, NOT
 | **CP-AP-6** | `feature-list.json` Generated | Schema validates, all required keys present | 6-7 |
 | **CP-AP-7** | Final Validation Pass | Python script returns `"valid": true` with zero errors | 8 |
 
-**Resume Detection**: If existing artifacts are found, read `references/error-recovery.md` §Resume Support for checkpoint-based resumption.
+**Resume Detection**: If existing artifacts are found, read `${SKILL_DIR}/references/error-recovery.md` §Resume Support for checkpoint-based resumption.
 
 ## Architecture Decision Capture
 
-After Phase 5, if framework-shaping architecture decisions emerged during planning (tech stack, communication patterns, data model strategies — not individual feature details), read `references/architecture-decisions.md` and follow the capture flow. Most sessions will NOT produce architecture decisions — only capture when genuinely impactful.
+After Phase 5, if framework-shaping architecture decisions emerged during planning (tech stack, communication patterns, data model strategies — not individual feature details), read `${SKILL_DIR}/references/architecture-decisions.md` and follow the capture flow. Most sessions will NOT produce architecture decisions — only capture when genuinely impactful.
 
 ## Fast Path — Incremental Shortcuts
 
@@ -270,7 +268,7 @@ A feature is **exempt** when ANY of these are true:
 
 ### Default Behavior (Phase 4.2)
 
-1. **Auto-generate** `browser_interaction` for ALL qualifying features. Read `references/browser-interaction.md` for the object format and field rules.
+1. **Auto-generate** `browser_interaction` for ALL qualifying features. Read `${SKILL_DIR}/references/browser-interaction.md` for the object format and field rules.
 2. **Present a summary** to the user showing which features received `browser_interaction`:
    > "以下 N 个前端特性已自动添加 browser_interaction 用于 Playwright 自动验证：F-002, F-004, F-007。如需移除某个特性的浏览器验证，请告知。"
 3. **User can opt-OUT** specific features — remove the field for declined features.
@@ -371,7 +369,7 @@ When launcher is available, do not prioritize raw scripts.
 
 ## Error Recovery & Resume
 
-If validation fails or a session is interrupted → read `references/error-recovery.md` for the full error type table, decision tree, retry logic, and checkpoint-based resume support.
+If validation fails or a session is interrupted → read `${SKILL_DIR}/references/error-recovery.md` for the full error type table, decision tree, retry logic, and checkpoint-based resume support.
 
 Key behaviors:
 - Warnings only → proceed with user approval

package/bundled/skills/recovery-workflow/evals/evals.json

@@ -0,0 +1,30 @@
+{
+  "skill_name": "recovery-workflow",
+  "notes": "These test cases require pipeline state setup. Each has a setup_script that creates the necessary mock state before the skill is invoked. Due to the interactive nature and state-dependency of this skill, automated evaluation is limited — qualitative review is primary.",
+  "evals": [
+    {
+      "id": 1,
+      "name": "scenario-a-mid-implementation",
+      "prompt": "F-003 的 session 超时了，工作区里已经写了大部分代码了，帮我恢复一下",
+      "expected_output": "Should detect existing spec.md, plan.md with partial task completion, code changes in worktree. Should recommend 'Smart Resume' (continue_implementation). Should present clear recovery report showing what was found and what remains.",
+      "setup_description": "Create feature-list.json with F-003, .prizmkit/specs/003-*/spec.md and plan.md (3/5 tasks checked), some source files modified, pipeline state showing 'failed'.",
+      "files": []
+    },
+    {
+      "id": 2,
+      "name": "scenario-b-plan-only",
+      "prompt": "我看到 F-001 有 spec 和 plan 但是还没开始写代码，帮我从 plan 开始执行",
+      "expected_output": "Should detect spec.md and plan.md exist but no code changes. Should recommend 'Start Implementation'. Should read existing plan and begin implementing from task 1.",
+      "setup_description": "Create feature-list.json with F-001, .prizmkit/specs/001-*/spec.md and plan.md (0/4 tasks checked), no code changes, pipeline state showing 'failed' at early phase.",
+      "files": []
+    },
+    {
+      "id": 3,
+      "name": "scenario-a-nearly-complete",
+      "prompt": "recover F-005. Token limit exceeded but I think the code is mostly done, tests should be passing",
+      "expected_output": "Should detect all plan tasks completed, code changes present, tests passing. Should recommend 'Review & Commit Only'. Should proceed to code review and commit without re-implementing.",
+      "setup_description": "Create feature-list.json with F-005, full spec.md and plan.md (all tasks checked), source files complete and tests passing, pipeline state showing 'failed' with token limit error.",
+      "files": []
+    }
+  ]
+}

package/package.json

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

package/src/scaffold.js

@@ -156,11 +156,11 @@ export async function installSkills(platform, skills, projectRoot, dryRun) {
       if (!frontmatter.name) frontmatter.name = skillName;
       await fs.writeFile(path.join(targetDir, 'SKILL.md'), buildMarkdown(frontmatter, body));
 
-      // 复制 assets/、scripts/ 和 references/
-      for (const subdir of ['assets', 'scripts', 'references']) {
-        const srcSubdir = path.join(corePath, subdir);
-        if (await fs.pathExists(srcSubdir)) {
-          await fs.copy(srcSubdir, path.join(targetDir, subdir));
+      // 复制所有子目录（assets/, scripts/, references/ 等）
+      const cbEntries = await fs.readdir(corePath, { withFileTypes: true });
+      for (const entry of cbEntries) {
+        if (entry.isDirectory()) {
+          await fs.copy(path.join(corePath, entry.name), path.join(targetDir, entry.name));
         }
       }
 
@@ -170,9 +170,9 @@ export async function installSkills(platform, skills, projectRoot, dryRun) {
       const content = await fs.readFile(skillMdPath, 'utf8');
       const converted = convertSkillToCommand(content, skillName);
 
-      const hasAssets = await fs.pathExists(path.join(corePath, 'assets'));
-      const hasScripts = await fs.pathExists(path.join(corePath, 'scripts'));
-      const hasReferences = await fs.pathExists(path.join(corePath, 'references'));
+      // Discover all subdirectories in the skill
+      const clEntries = await fs.readdir(corePath, { withFileTypes: true });
+      const skillSubdirs = clEntries.filter(e => e.isDirectory()).map(e => e.name);
 
       // Always write the command file at the flat level (.claude/commands/skillName.md)
       // so Claude Code shows it as /skillName (not /skillName:skillName).
@@ -185,16 +185,13 @@ export async function installSkills(platform, skills, projectRoot, dryRun) {
       await fs.ensureDir(commandsDir);
       await fs.writeFile(path.join(commandsDir, `${skillName}.md`), converted);
 
-      if (hasAssets || hasScripts || hasReferences) {
-        // Place assets/scripts outside .claude/commands/ to prevent Claude Code
+      if (skillSubdirs.length > 0) {
+        // Place subdirectories outside .claude/commands/ to prevent Claude Code
         // from registering them as slash commands (e.g. /skillName:assets:file).
         const assetTargetDir = path.join(projectRoot, '.claude', 'command-assets', skillName);
         await fs.ensureDir(assetTargetDir);
-        for (const subdir of ['assets', 'scripts', 'references']) {
-          const srcSubdir = path.join(corePath, subdir);
-          if (await fs.pathExists(srcSubdir)) {
-            await fs.copy(srcSubdir, path.join(assetTargetDir, subdir));
-          }
+        for (const subdir of skillSubdirs) {
+          await fs.copy(path.join(corePath, subdir), path.join(assetTargetDir, subdir));
         }
       }
       console.log(chalk.green(`      ✓ .claude/commands/${skillName}.md`));