prizmkit 1.1.4 → 1.1.5

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.4",
-  "bundledAt": "2026-04-04T10:53:06.101Z",
-  "bundledFrom": "5cdc680"
+  "frameworkVersion": "1.1.5",
+  "bundledAt": "2026-04-04T15:56:26.382Z",
+  "bundledFrom": "902d4ef"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.4",
+  "version": "1.1.5",
   "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-implement/references/deploy-guide-protocol.md

@@ -0,0 +1,69 @@
+# Deploy Guide Update Protocol
+
+When dependency manifests change during implementation, update `deploy_guide.md` at the project root.
+
+## Detection
+
+1. Check if any dependency manifests were modified in this session:
+   ```bash
+   git diff --name-only HEAD -- package.json requirements*.txt Pipfile pyproject.toml go.mod Cargo.toml pom.xml build.gradle Gemfile composer.json docker-compose*.yml Dockerfile .tool-versions 2>/dev/null
+   ```
+2. If no manifest files changed → skip this step entirely
+3. If manifest files changed, scan for **newly added** dependencies (not version bumps):
+   ```bash
+   git diff -U0 HEAD -- package.json requirements*.txt Pipfile pyproject.toml go.mod Cargo.toml pom.xml build.gradle Gemfile composer.json docker-compose*.yml Dockerfile .tool-versions 2>/dev/null | grep '^\+' | grep -v '^\+\+\+' | head -30
+   ```
+
+## Recording
+
+For each genuinely new framework/tool, record in `deploy_guide.md` at project root:
+
+| Field | Description | Source |
+|-------|-------------|--------|
+| **Name** | Framework/tool name | Package name from manifest |
+| **Version** | Installed version or constraint | Version spec from manifest |
+| **Purpose** | Why it was introduced | You just added it — you know why |
+| **Install Command** | How to install locally | Standard install command for the ecosystem |
+| **Key Config** | Config files or env vars needed | Config files you just created/modified |
+| **Notes** | Setup gotchas, required services | Docker services, manual steps, env vars |
+
+## Template for `deploy_guide.md`
+
+```markdown
+# Deploy Guide
+
+> Auto-maintained by PrizmKit. Manual edits are preserved.
+> Last updated: YYYY-MM-DD
+
+## Frameworks & Tools
+
+### <Framework Name>
+
+- **Version**: <version constraint>
+- **Purpose**: <why this framework is used>
+- **Install**:
+  ```bash
+  <install command>
+  ```
+- **Key Config**:
+  - `<config file or env var>`: <description>
+- **Notes**:
+  - <any setup gotchas, required external services, manual steps>
+```
+
+## Update Rules
+
+- Create file if absent; append new sections if file exists
+- Update version if framework already documented
+- Preserve manually added content
+- Keep entries sorted alphabetically
+
+## Filter Out
+
+- Patch version bumps of existing deps
+- Dev-only tools needing no setup (linters, formatters)
+- Transitive/lock-file-only changes
+
+## Final Step
+
+Stage the file: `git add deploy_guide.md`

package/bundled/skills/prizmkit-init/references/config-schema.md

@@ -0,0 +1,64 @@
+# config.json Schema — Tech Stack Fields
+
+## Merge Strategy
+
+Handles re-init without losing user edits:
+
+- Read existing `config.json` if present
+- If `tech_stack` field exists AND `_auto_detected` is `false` or absent:
+  → **SKIP** — user has manually configured tech stack, preserve their settings
+- If `tech_stack` field exists AND `_auto_detected` is `true`:
+  → **MERGE** — overwrite auto-detected values with new detection results, but preserve any keys the user added manually (keys not in the new detection result)
+- If `tech_stack` field does NOT exist:
+  → **WRITE** full detected tech stack with `"_auto_detected": true`
+- Only include fields that were actually detected (no empty/null values)
+
+## Field Definitions
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `adoption_mode` | string | `"passive"` \| `"advisory"` \| `"active"` |
+| `platform` | string | `"codebuddy"` \| `"claude"` \| `"both"` |
+| `tech_stack` | object | Detected or user-provided tech stack |
+| `tech_stack._auto_detected` | boolean | `true` if auto-detected, `false` if user-provided |
+
+## Examples
+
+Fullstack project:
+```json
+{
+  "adoption_mode": "passive",
+  "platform": "claude",
+  "tech_stack": {
+    "language": "TypeScript",
+    "runtime": "Node.js 20",
+    "frontend_framework": "React",
+    "frontend_styling": "Tailwind CSS",
+    "backend_framework": "Express.js",
+    "database": "PostgreSQL",
+    "orm": "Prisma",
+    "testing": "Vitest",
+    "bundler": "Vite",
+    "project_type": "fullstack",
+    "_auto_detected": true
+  }
+}
+```
+
+Pure Python backend:
+```json
+{
+  "adoption_mode": "passive",
+  "platform": "claude",
+  "tech_stack": {
+    "language": "Python",
+    "runtime": "Python >=3.11",
+    "backend_framework": "FastAPI",
+    "database": "PostgreSQL",
+    "orm": "SQLAlchemy",
+    "testing": "pytest",
+    "project_type": "backend",
+    "_auto_detected": true
+  }
+}
+```

package/bundled/skills/prizmkit-init/references/tech-stack-catalog.md

@@ -0,0 +1,13 @@
+# Tech Stack Detection — Field Catalog
+
+Adaptive field list — only include fields that apply to the project being scanned.
+
+- **Language & Runtime**: e.g. TypeScript + Node.js 20, Python 3.11, Go 1.22
+- **Frontend framework** (if applicable): React, Vue.js, Angular, Next.js, Svelte, etc.
+- **Frontend styling** (if applicable): Tailwind CSS, SCSS, Styled Components, Material UI, etc.
+- **Backend framework** (if applicable): Express.js, FastAPI, Django, NestJS, Gin, etc.
+- **Database** (if applicable): PostgreSQL, MySQL, MongoDB, Redis, SQLite — detected from deps or `docker-compose.yml`
+- **ORM** (if applicable): Prisma, Drizzle, TypeORM, SQLAlchemy, Mongoose, etc.
+- **Bundler** (if applicable): Vite, Webpack, esbuild, Rollup, Turborepo
+- **Testing**: Vitest, Jest, pytest, Go test, etc.
+- **Project type** (inferred): `frontend` | `backend` | `fullstack` | `library` | `cli` | `monorepo`

package/bundled/skills/prizmkit-init/references/update-supplement.md

@@ -0,0 +1,9 @@
+# Update Supplement — Post-Merge Gap-Fill Procedure
+
+Runs after tech stack merge in Update mode:
+
+1. **Module scan**: Re-scan project directories using the same TWO-TIER model from Step 1. Compare discovered modules against existing MODULE_INDEX in root.prizm.
+2. **Missing L1 check**: For any discovered module with no corresponding L1 `.prizm` doc → create L1 immediately and add to MODULE_INDEX.
+3. **Missing L2 check**: For any module/sub-module that has source files with meaningful logic but no L2 `.prizm` doc → create L2 using the L2 GENERATION TEMPLATE. Judgment call: skip trivial wrapper directories or single-config modules.
+4. **Stale L1 check**: For existing L1 docs, verify FILES count and KEY_FILES are still accurate. Update if source directory contents have changed significantly.
+5. **Report**: Include in the Update report: modules added, L1 docs created, L2 docs created, stale docs refreshed.

package/bundled/skills/prizmkit-plan/assets/spec-template.md

@@ -0,0 +1,56 @@
+# Feature: [FEATURE_TITLE]
+
+## Overview
+[One paragraph describing the feature purpose and business value]
+
+## User Stories
+
+### US1: [Story Title]
+**As a** [role]
+**I want** [capability]
+**So that** [benefit]
+
+**Acceptance Criteria:**
+- [ ] Given [context], When [action], Then [expected result]
+
+## Scope
+
+### In Scope
+- [Item 1]
+
+### Out of Scope
+- [Item 1]
+
+## Dependencies
+- [Dependency 1]: [Why needed]
+
+## Data Model (if feature involves database changes)
+
+### Existing Schema Reference
+<!-- Read existing schema/model files BEFORE designing new tables. Document observed conventions here. -->
+- Tables reviewed: [list existing tables related to this feature]
+- Naming convention: [snake_case/camelCase — match existing]
+- ID strategy: [UUID/auto-increment — match existing]
+- Timestamp pattern: [created_at/updated_at — match existing]
+- Soft delete: [yes/no, field name — match existing]
+
+### New/Modified Entities
+| Entity | Type (new/modify) | Key Fields | Relationships | Constraints |
+|--------|-------------------|------------|---------------|-------------|
+| [entity_name] | new | [field: type] | [FK to existing_table] | [NOT NULL, UNIQUE, etc.] |
+
+### Open Data Model Questions
+<!-- All questions here MUST be resolved before /prizmkit-plan generates Tasks -->
+- [NEEDS CLARIFICATION] [Any uncertain data model decisions — field types, nullability, relationships]
+
+## Constraints
+- [Constraint 1]
+
+## Clarifications
+[NEEDS CLARIFICATION]: [Ambiguous item]
+
+## Review Checklist
+- [ ] All user stories have acceptance criteria
+- [ ] Scope boundaries are clearly defined
+- [ ] Dependencies are identified
+- [ ] No implementation details (WHAT not HOW)

package/bundled/skills/prizmkit-plan/references/clarify-guide.md

@@ -0,0 +1,67 @@
+# Clarification Phase — Execution Guide
+
+Invoked automatically during `/prizmkit-plan` Phase 0 (specify) when `[NEEDS CLARIFICATION]` markers exist, or during Phase 1 (design) when data model ambiguities arise.
+
+---
+
+## Question Strategy
+
+**Ask one question at a time.** Batching questions produces lower-quality answers.
+
+For each question:
+1. Cite the exact location in spec.md (e.g., "§3.2 says...")
+2. State what is ambiguous and why it matters for implementation
+3. Provide a **recommended answer** with rationale — gives the user a concrete starting point to accept, modify, or reject
+
+**Prioritize by implementation impact** (highest first):
+1. Data model (entities, relationships, field types, constraints, naming) — **hardest to change after code is written**
+2. Functional scope boundaries
+3. UX flow and error handling
+4. Non-functional requirements (performance, security)
+5. Edge cases and integration points
+
+## Update Discipline
+
+After **each** user answer:
+- Immediately update `spec.md` (do not batch at the end)
+- Remove the resolved `[NEEDS CLARIFICATION]` marker
+- Re-evaluate for new ambiguities exposed by the answer
+
+## No Limits Policy
+
+**There is no cap on rounds or questions.** Keep asking until:
+- All `[NEEDS CLARIFICATION]` markers are removed, AND
+- No vague or underspecified areas remain, AND
+- You are fully confident about the requirements
+
+If the user's answer raises new questions — ask those too. If a previously-resolved item needs revisiting due to new context — go back.
+
+## Early Termination
+
+If the user says "done", "stop", or "enough" — end immediately and output a summary of:
+- What was resolved
+- What remains unclear (list any open `[NEEDS CLARIFICATION]` items)
+
+## Example Exchange
+
+**Question:**
+> §3.2 says "User can upload files" but doesn't specify file types or size limits.
+>
+> **Recommended:** Accept JPEG, PNG, PDF up to 10MB — covers common use cases without straining storage.
+>
+> Do you agree, or different constraints?
+
+**User:** "Also allow SVG, make it 25MB"
+
+**Action:** Update spec.md §3.2 → `File upload: JPEG, PNG, PDF, SVG. Max 25MB per file.` Remove marker.
+
+**Follow-up question triggered by answer:**
+> SVGs can contain embedded scripts (XSS risk). Should uploaded SVGs be sanitized (strip `<script>` + event handlers), or restricted to trusted users only?
+>
+> **Recommended:** Sanitize all SVG uploads — allows all users to upload safely.
+
+## Guidelines
+
+- Stay at WHAT/WHY level — no implementation details (HOW) in spec
+- If an answer contradicts an existing requirement, surface the conflict and ask which takes precedence
+- If the user seems fatigued: "I have N more questions — continue now or later?" — but never silently stop with unresolved ambiguities

package/bundled/skills/prizmkit-retrospective/references/knowledge-injection-steps.md

@@ -0,0 +1,49 @@
+# Knowledge Injection — Detailed Steps (2a–2c)
+
+**2a.** Gather context — read the **actual code that was changed** plus any available artifacts:
+
+- `git diff HEAD` — the real source of truth for what happened
+- `.prizmkit/specs/###-feature-name/context-snapshot.md` — read the '## Implementation Log' section (Dev's changes, decisions, discoveries) and '## Review Notes' section (Reviewer's findings). These are the **preferred source** for pre-categorized decisions and findings. If these sections exist, prefer them over re-extracting from git diff.
+- `.prizmkit/specs/###-feature-name/plan.md` — if feature work, read planned vs actual
+- `.prizmkit/bugfix/<id>/fix-report.md` — if bugfix, read what was discovered
+- `.prizmkit/specs/###-feature-name/failure-log.md` — if a previous session failed, read DISCOVERED_TRAPS. These are high-value TRAPS because they come from actual failures — prioritize injecting them into `.prizm-docs/`
+- The relevant `.prizm-docs/` L1/L2 docs for affected modules
+
+**2b.** Extract knowledge from what was **observed in code**, not invented:
+
+**TRAPS** (highest priority) — things that look safe but break:
+- Minimal format: `- [SEVERITY] <description> | FIX: <approach>`
+- Full format: `- [SEVERITY] <description> | FIX: <approach> | REF: <hash> | STALE_IF: <glob>`
+- Source: actual bugs hit, surprising behavior discovered in code, non-obvious coupling
+
+**TRAPS severity classification**:
+- `[CRITICAL]`: data loss, security, financial error, system crash
+- `[HIGH]`: functional failure, silent error, interface incompatibility
+- `[LOW]`: misleading naming, non-intuitive API, minor performance issue
+
+When writing TRAPS:
+- Severity prefix is MANDATORY (e.g., `[CRITICAL]`, `[HIGH]`, `[LOW]`)
+- OPTIONAL: append `| REF: <7-char-hash>` when you know the relevant commit (for traceability)
+- OPTIONAL: append `| STALE_IF: <glob>` when the TRAP is tightly coupled to specific files (for auto-expiry detection)
+
+**Consuming [REVIEW] markers** (from staleness check 1g):
+- If you encounter a TRAP prefixed with `[REVIEW]` (e.g., `[REVIEW][HIGH] ...`), verify whether the trap is still valid by checking the current code. If still valid: remove the `[REVIEW]` prefix, keeping the severity. If no longer relevant: delete the TRAP entry and append CHANGELOG.
+
+**RULES** — conventions established or constraints discovered:
+- Format: `- MUST/NEVER/PREFER: <rule>`
+- Source: patterns that proved necessary during implementation
+
+**DECISIONS** — key design choices that affect future development:
+- Format: `- <what was decided> — <rationale>`
+- Source: non-obvious design choices, interface conventions, cross-module contracts
+- Only record decisions that a future AI session would benefit from knowing
+- Do NOT record obvious implementation details that can be derived by reading the code
+
+**QUALITY GATE**: Every item must answer: "If a new AI session reads only `.prizm-docs/` and this entry, does it gain actionable understanding?" If not, discard. Do not record trivially observable code patterns — the AI can read the code directly.
+
+**2c.** Inject into the correct `.prizm-docs/` file:
+- Module-level TRAPS/RULES/DECISIONS → the affected **L2** `.prizm` file. If the target L2 does not exist, create it first using the L2 GENERATION TEMPLATE before injecting knowledge. (TRAPS/DECISIONS/RULES belong in L2, not L1.)
+- Project-level RULES/PATTERNS → `root.prizm` (respect the current format — MODULE_INDEX or MODULE_GROUPS — do not convert between them during injection)
+- Cross-module concerns spanning 2+ modules → `root.prizm` CROSS_CUTTING section
+
+**RULE**: Only add genuinely new information. Never duplicate existing entries. Never rewrite entire files.

package/bundled/skills/prizmkit-retrospective/references/structural-sync-steps.md

@@ -0,0 +1,63 @@
+# Structural Sync — Detailed Steps (1a–1g)
+
+**1a.** Get changed files:
+```bash
+git diff --cached --name-status
+```
+If nothing staged, fallback:
+```bash
+git diff --name-status
+```
+
+**1b.** Read `.prizm-docs/root.prizm` to get MODULE_INDEX (or MODULE_GROUPS). Map each changed file to its module.
+
+**1c.** Classify changes:
+- `A` (added) → add to KEY_FILES, check for new INTERFACES
+- `D` (deleted) → remove from KEY_FILES, update FILE count
+- `M` (modified) → check if public interfaces or dependencies changed
+- `R` (renamed) → update all path references
+
+**1d.** Update affected docs (bottom-up: L2 → L1 → L0):
+
+- **L2**: If L2 exists → update KEY_FILES, INTERFACES, DATA_FLOW, DEPENDENCIES, CHANGELOG, TRAPS, DECISIONS. If L2 does NOT exist AND the module has Added or Modified source files in the current diff with meaningful logic (not trivial config) → create L2 using the L2 GENERATION TEMPLATE, then populate from source.
+- **L1**: Update FILES count, KEY_FILES (if major files added/removed), DEPENDENCIES (if module-level deps changed). **L1 does NOT contain INTERFACES, DATA_FLOW, TRAPS, or DECISIONS** — those belong in L2 only.
+- **L0 root.prizm**: Update MODULE_INDEX file counts only if counts changed. Update CROSS_CUTTING if cross-module concerns changed. Update only if structural change (module added/removed).
+
+**1d-migrate.** Legacy TRAPS format migration (opportunistic):
+While updating an affected L1/L2 doc, if you encounter TRAPS entries **without** a severity prefix (e.g., `- foo | FIX: bar` instead of `- [LOW] foo | FIX: bar`), prepend `[LOW]` as a conservative default. This clears legacy format debt incrementally — only in files already being touched, never as a bulk operation.
+
+**1e.** If new directory qualifies as a module (per MODULE_DISCOVERY_CRITERIA in PRIZM-SPEC Section 9.1 Step 2) and matches no existing module:
+1. Create L1 doc immediately, add to MODULE_INDEX.
+2. If the current diff includes Added or Modified source files with meaningful logic in this module → create L2 immediately using the L2 GENERATION TEMPLATE. Otherwise defer L2 to the next session that touches this module.
+
+**1f.** Enforce size limits:
+- L0 > 4KB → if using MODULE_INDEX with > 15 entries, convert to MODULE_GROUPS format (group by functional domain). Otherwise, consolidate MODULE_INDEX descriptions.
+- L1 > 4KB → trim KEY_FILES descriptions, ensure RULES <= 3 entries
+- L2 > 5KB → archive old CHANGELOG entries
+
+**SKIP structural sync if**: only internal implementation changed (no interface/dependency impact), only comments/whitespace, only .prizm files. **DO NOT skip** test file changes or bug fixes — they may reveal TRAPS worth capturing in L2.
+
+**1g. TRAPS staleness check** (only when an L2 doc's TRAPS section has > 10 entries):
+
+(Note: `/prizmkit-prizm-docs` Validate uses a lower threshold of > 8 entries to flag TRAPS needing staleness metadata. This step uses > 10 because it performs actual cleanup, which is more expensive. Validate warns early; this step acts later.)
+
+Perform a quick staleness scan on existing TRAPS to prevent unbounded accumulation:
+1. If a TRAP has `STALE_IF:` and the glob-matched files no longer exist (verified via `ls`) → delete the TRAP entry, append CHANGELOG: `remove: archived stale TRAP - <summary>`
+2. If a TRAP has `REF:` → check if the referenced file still exists and the REF commit is less than 180 days old (via `git log --since="180 days ago" <hash> 2>/dev/null`). If the file is deleted OR the REF commit is older than 180 days → prepend `[REVIEW]` to the severity, signaling it needs verification during the next retrospective Job 2
+3. Process at most 5 of the oldest TRAPS per L2 doc per session (to bound context cost)
+
+This step is lightweight — it only triggers when TRAPS exceed 10 entries, and processes at most 5 per run.
+
+**1h. Periodic full TRAPS audit** (runs approximately once every 10 retrospective sessions):
+
+Check `.prizm-docs/changelog.prizm` for the marker `audit: traps-audit full-scan`. If the marker does not exist, OR the most recent `audit: traps-audit full-scan` entry has 10+ other changelog entries after it:
+
+1. Scan ALL L2 `.prizm` files (not just ones touched this session)
+2. For each L2 doc with TRAPS entries:
+   - Verify referenced file paths still exist (via `ls`)
+   - If `STALE_IF:` glob matches zero files → delete the TRAP, append CHANGELOG: `remove: archived stale TRAP - <summary>`
+   - If `REF:` commit is older than 180 days AND the referenced file was significantly refactored (>50% lines changed since REF commit) → prepend `[REVIEW]`
+3. Process at most 3 TRAPS per L2 doc to bound context cost (total max ~15 TRAPS per audit)
+4. Append to `.prizm-docs/changelog.prizm`: `- root | audit: traps-audit full-scan — checked N docs, removed M stale, marked K for review`
+
+This is a lightweight background pass. If the project has fewer than 5 L2 docs, skip this step (not enough accumulation to warrant auditing).

package/package.json

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

package/src/config.js

@@ -0,0 +1,504 @@
+/**
+ * PrizmKit Config Command
+ *
+ * Reconfigure an existing PrizmKit installation without a full reinstall.
+ * Supports changing platform, AI CLI, skills suite, rules, team, and pipeline.
+ *
+ * Flow: READ manifest → PROMPT user → COMPUTE DIFF → DISPLAY SUMMARY → EXECUTE
+ *
+ * Preserves runtime files (.prizm-docs/, dev-pipeline/state/, .prizmkit/specs/).
+ */
+
+import chalk from 'chalk';
+import fs from 'fs-extra';
+import path from 'path';
+import { readFileSync } from 'fs';
+import { dirname, join } from 'path';
+import { fileURLToPath } from 'url';
+import { confirm } from '@inquirer/prompts';
+
+import { readManifest, writeManifest, buildManifest, diffManifest } from './manifest.js';
+import {
+  loadMetadata,
+  loadRulesMetadata,
+  getAgentsDir,
+} from './metadata.js';
+import {
+  installSkills,
+  installAgents,
+  installSettings,
+  installTeamConfig,
+  installProjectMemory,
+  installPipeline,
+  installGitignore,
+  resolveSkillList,
+  resolvePipelineFileList,
+} from './scaffold.js';
+import {
+  removeSkillFiles,
+  removeAgentFiles,
+  removeRuleFiles,
+  removePipelineFiles,
+} from './upgrade.js';
+import { detectPlatform } from './detect-platform.js';
+import {
+  selectPlatform,
+  selectAiCli,
+  selectSkillSuite,
+  selectRulesPreset,
+  confirmTeamMode,
+  confirmPipeline,
+} from './prompts.js';
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const pkg = JSON.parse(readFileSync(join(__dirname, '..', 'package.json'), 'utf-8'));
+
+// ============================================================
+// Helpers
+// ============================================================
+
+/**
+ * Detect which platforms are actually installed on filesystem.
+ */
+async function detectInstalledPlatforms(projectRoot) {
+  const hasClaude = await fs.pathExists(path.join(projectRoot, '.claude', 'commands'))
+                    || await fs.pathExists(path.join(projectRoot, '.claude', 'agents'));
+  const hasCodeBuddy = await fs.pathExists(path.join(projectRoot, '.codebuddy', 'skills'))
+                       || await fs.pathExists(path.join(projectRoot, '.codebuddy', 'agents'));
+
+  if (hasClaude && hasCodeBuddy) return 'both';
+  if (hasCodeBuddy) return 'codebuddy';
+  if (hasClaude) return 'claude';
+  return null;
+}
+
+/**
+ * Expand a platform string to an array of individual platforms.
+ */
+function expandPlatforms(platform) {
+  return platform === 'both' ? ['codebuddy', 'claude'] : [platform];
+}
+
+const platformLabel = (p) => p === 'both' ? 'CodeBuddy + Claude Code'
+  : p === 'codebuddy' ? 'CodeBuddy' : 'Claude Code';
+
+/**
+ * Remove all PrizmKit-owned platform-specific files for a single platform.
+ * Selective removal — only removes known PrizmKit files, leaves user-created files intact.
+ */
+async function removePlatformFiles(platform, projectRoot, manifest, dryRun) {
+  const skillNames = manifest?.files?.skills || [];
+  const agentFileNames = manifest?.files?.agents || [];
+  const ruleFileNames = manifest?.files?.rules || [];
+
+  if (skillNames.length) {
+    console.log(chalk.blue(`\n    删除 ${platformLabel(platform)} skills:`));
+    await removeSkillFiles(platform, projectRoot, skillNames, dryRun);
+  }
+
+  if (agentFileNames.length) {
+    console.log(chalk.blue(`\n    删除 ${platformLabel(platform)} agents:`));
+    await removeAgentFiles(platform, projectRoot, agentFileNames, dryRun);
+  }
+
+  if (ruleFileNames.length) {
+    console.log(chalk.blue(`\n    删除 ${platformLabel(platform)} rules:`));
+    await removeRuleFiles(platform, projectRoot, ruleFileNames, dryRun);
+  }
+
+  // Settings
+  const settingsFile = platform === 'claude'
+    ? path.join(projectRoot, '.claude', 'settings.json')
+    : path.join(projectRoot, '.codebuddy', 'settings.json');
+  if (await fs.pathExists(settingsFile)) {
+    if (dryRun) {
+      console.log(chalk.gray(`      [dry-run] remove ${path.relative(projectRoot, settingsFile)}`));
+    } else {
+      await fs.remove(settingsFile);
+      console.log(chalk.red(`      ✗ removed ${path.relative(projectRoot, settingsFile)}`));
+    }
+  }
+
+  // Team info
+  if (platform === 'claude') {
+    const teamInfo = path.join(projectRoot, '.claude', 'team-info.json');
+    if (await fs.pathExists(teamInfo)) {
+      if (dryRun) {
+        console.log(chalk.gray('      [dry-run] remove .claude/team-info.json'));
+      } else {
+        await fs.remove(teamInfo);
+        console.log(chalk.red('      ✗ removed .claude/team-info.json'));
+      }
+    }
+  } else if (platform === 'codebuddy') {
+    const homeDir = process.env.HOME || process.env.USERPROFILE;
+    const teamDir = path.join(homeDir, '.codebuddy', 'teams', 'prizm-dev-team');
+    if (await fs.pathExists(teamDir)) {
+      if (dryRun) {
+        console.log(chalk.gray('      [dry-run] remove ~/.codebuddy/teams/prizm-dev-team/'));
+      } else {
+        await fs.remove(teamDir);
+        console.log(chalk.red('      ✗ removed ~/.codebuddy/teams/prizm-dev-team/'));
+      }
+    }
+  }
+
+  // Project memory file
+  const memoryFile = platform === 'claude' ? 'CLAUDE.md' : 'CODEBUDDY.md';
+  const memoryPath = path.join(projectRoot, memoryFile);
+  if (await fs.pathExists(memoryPath)) {
+    if (dryRun) {
+      console.log(chalk.gray(`      [dry-run] remove ${memoryFile}`));
+    } else {
+      await fs.remove(memoryPath);
+      console.log(chalk.red(`      ✗ removed ${memoryFile}`));
+    }
+  }
+
+  // Command assets (Claude only)
+  if (platform === 'claude') {
+    const assetsDir = path.join(projectRoot, '.claude', 'command-assets');
+    if (await fs.pathExists(assetsDir)) {
+      if (dryRun) {
+        console.log(chalk.gray('      [dry-run] remove .claude/command-assets/'));
+      } else {
+        await fs.remove(assetsDir);
+        console.log(chalk.red('      ✗ removed .claude/command-assets/'));
+      }
+    }
+  }
+}
+
+// ============================================================
+// Main
+// ============================================================
+
+/**
+ * Run the config reconfiguration command.
+ * @param {string} directory - target project directory
+ * @param {Object} options - CLI options from commander
+ */
+export async function runConfig(directory, options = {}) {
+  const projectRoot = path.resolve(directory || '.');
+  const dryRun = Boolean(options.dryRun);
+  const nonInteractive = Boolean(options.nonInteractive);
+
+  console.log('');
+  console.log(chalk.bold('  PrizmKit Config'));
+  console.log(`  Target: ${projectRoot}`);
+  if (dryRun) console.log(chalk.yellow('  Mode: dry-run'));
+  console.log('');
+
+  // ── Phase 1: READ current state ──────────────────────────────────────────
+
+  const oldManifest = await readManifest(projectRoot);
+  if (!oldManifest) {
+    console.log(chalk.red('  ✗ 未找到 .prizmkit/manifest.json'));
+    console.log(chalk.gray('    请先运行 `npx prizmkit install .` 安装 PrizmKit。'));
+    console.log('');
+    return;
+  }
+
+  // Read user config
+  const configPath = path.join(projectRoot, '.prizmkit', 'config.json');
+  let userConfig = {};
+  if (await fs.pathExists(configPath)) {
+    try { userConfig = await fs.readJSON(configPath); } catch { /* ignore */ }
+  }
+
+  // Filesystem-based platform detection (overrides manifest)
+  const detectedPlatform = await detectInstalledPlatforms(projectRoot) || oldManifest.platform || 'claude';
+
+  const currentConfig = {
+    platform: detectedPlatform,
+    suite: oldManifest.suite || 'core',
+    rules: oldManifest.options?.rules || 'recommended',
+    team: oldManifest.options?.team ?? true,
+    pipeline: oldManifest.options?.pipeline ?? true,
+    aiCli: userConfig.ai_cli || oldManifest.options?.aiCli || '',
+  };
+
+  // Display current config
+  console.log(chalk.bold('  当前配置:'));
+  console.log(`    平台:     ${chalk.cyan(platformLabel(currentConfig.platform))}`);
+  console.log(`    AI CLI:   ${currentConfig.aiCli ? chalk.cyan(currentConfig.aiCli) : chalk.gray('(未设置)')}`);
+  console.log(`    技能套件: ${chalk.cyan(currentConfig.suite)}`);
+  console.log(`    规则:     ${chalk.cyan(currentConfig.rules)}`);
+  console.log(`    团队模式: ${currentConfig.team ? chalk.green('启用') : chalk.gray('禁用')}`);
+  console.log(`    流水线:   ${currentConfig.pipeline ? chalk.green('启用') : chalk.gray('禁用')}`);
+  console.log('');
+
+  // ── Phase 2: PROMPT for new config ───────────────────────────────────────
+
+  let newConfig;
+
+  if (nonInteractive) {
+    // Non-interactive: only change what's explicitly specified via CLI options
+    if (!options.platform && !options.skills && !options.rules
+        && options.aiCli === undefined && options.team === undefined && options.pipeline === undefined) {
+      console.log(chalk.yellow('  ⚠ 非交互式模式下未指定任何变更。'));
+      console.log(chalk.gray('    使用 --platform, --skills, --rules, --ai-cli, --team/--no-team, --pipeline/--no-pipeline'));
+      return;
+    }
+
+    newConfig = {
+      platform: options.platform || currentConfig.platform,
+      suite: options.skills || currentConfig.suite,
+      rules: options.rules || currentConfig.rules,
+      team: options.team !== undefined ? options.team : currentConfig.team,
+      pipeline: options.pipeline !== undefined ? options.pipeline : currentConfig.pipeline,
+      aiCli: options.aiCli !== undefined ? options.aiCli : currentConfig.aiCli,
+    };
+  } else {
+    // Interactive: let user select each setting
+    const detected = detectPlatform();
+
+    try {
+      console.log(chalk.bold('  选择新配置（按 Enter 保持当前值）:\n'));
+
+      const newPlatform = await selectPlatform(currentConfig.platform, detected);
+      const newAiCli = await selectAiCli(currentConfig.aiCli, detected);
+
+      const metadata = await loadMetadata();
+      const newSuite = await selectSkillSuite(currentConfig.suite, metadata);
+      const newRules = await selectRulesPreset(currentConfig.rules);
+      const newTeam = await confirmTeamMode(currentConfig.team);
+      const newPipeline = await confirmPipeline(currentConfig.pipeline);
+
+      newConfig = {
+        platform: newPlatform,
+        suite: newSuite,
+        rules: newRules,
+        team: newTeam,
+        pipeline: newPipeline,
+        aiCli: newAiCli,
+      };
+    } catch (err) {
+      if (err.message?.includes('User force closed')) {
+        console.log(chalk.yellow('\n  配置已取消。'));
+        return;
+      }
+      throw err;
+    }
+  }
+
+  // ── Phase 3: COMPUTE DIFF ────────────────────────────────────────────────
+
+  const changes = [];
+  if (newConfig.platform !== currentConfig.platform) {
+    changes.push(`平台: ${platformLabel(currentConfig.platform)} → ${platformLabel(newConfig.platform)}`);
+  }
+  if (newConfig.aiCli !== currentConfig.aiCli) {
+    changes.push(`AI CLI: ${currentConfig.aiCli || '(未设置)'} → ${newConfig.aiCli || '(未设置)'}`);
+  }
+  if (newConfig.suite !== currentConfig.suite) {
+    changes.push(`技能套件: ${currentConfig.suite} → ${newConfig.suite}`);
+  }
+  if (newConfig.rules !== currentConfig.rules) {
+    changes.push(`规则: ${currentConfig.rules} → ${newConfig.rules}`);
+  }
+  if (newConfig.team !== currentConfig.team) {
+    changes.push(`团队模式: ${currentConfig.team ? '启用' : '禁用'} → ${newConfig.team ? '启用' : '禁用'}`);
+  }
+  if (newConfig.pipeline !== currentConfig.pipeline) {
+    changes.push(`流水线: ${currentConfig.pipeline ? '启用' : '禁用'} → ${newConfig.pipeline ? '启用' : '禁用'}`);
+  }
+
+  // ── Phase 4: DISPLAY SUMMARY + CONFIRM ───────────────────────────────────
+
+  if (changes.length === 0) {
+    console.log(chalk.green('\n  ✓ 配置未变更，无需操作。'));
+    console.log('');
+    return;
+  }
+
+  console.log(chalk.bold('\n  变更摘要:'));
+  for (const change of changes) {
+    console.log(`    ${chalk.yellow('→')} ${change}`);
+  }
+
+  // Warn about destructive changes
+  if (newConfig.platform !== currentConfig.platform) {
+    const oldPlatforms = expandPlatforms(currentConfig.platform);
+    const newPlatforms = expandPlatforms(newConfig.platform);
+    const dropping = oldPlatforms.filter(p => !newPlatforms.includes(p));
+    if (dropping.length) {
+      console.log(chalk.yellow(`\n  ⚠ 将移除 ${dropping.map(platformLabel).join(', ')} 的 PrizmKit 文件`));
+    }
+  }
+  console.log('');
+
+  if (dryRun) {
+    console.log(chalk.yellow('  [dry-run] 预览完成，未修改任何文件。'));
+    console.log('');
+    return;
+  }
+
+  if (!nonInteractive) {
+    const proceed = await confirm({
+      message: '确认应用配置变更?',
+      default: true,
+    });
+    if (!proceed) {
+      console.log(chalk.yellow('  配置已取消。'));
+      return;
+    }
+  }
+
+  // ── Phase 5: EXECUTE ─────────────────────────────────────────────────────
+
+  console.log(chalk.bold('\n  应用配置变更...\n'));
+
+  const oldPlatforms = expandPlatforms(currentConfig.platform);
+  const newPlatforms = expandPlatforms(newConfig.platform);
+  const platformsToRemove = oldPlatforms.filter(p => !newPlatforms.includes(p));
+  const platformsToAdd = newPlatforms.filter(p => !oldPlatforms.includes(p));
+  const platformsToUpdate = newPlatforms.filter(p => oldPlatforms.includes(p));
+
+  // Resolve new file lists
+  const newSkillList = await resolveSkillList(newConfig.suite);
+  const agentsDir = getAgentsDir();
+  const newAgentFiles = (await fs.readdir(agentsDir)).filter(f => f.endsWith('.md'));
+  const rulesMeta = await loadRulesMetadata();
+  const rulesPresetDef = rulesMeta.presets[newConfig.rules] || rulesMeta.presets.recommended;
+  const newRuleFiles = (rulesPresetDef?.rules || []).map(name => `${name}.md`);
+  const newPipelineFiles = newConfig.pipeline ? resolvePipelineFileList() : [];
+
+  // 5a. Remove files for platforms being dropped
+  for (const p of platformsToRemove) {
+    console.log(chalk.bold(`  移除 ${platformLabel(p)} 平台文件...`));
+    await removePlatformFiles(p, projectRoot, oldManifest, false);
+  }
+
+  // 5b. Handle skill/rule diff for existing platforms (suite or rules changed)
+  if (newConfig.suite !== currentConfig.suite || newConfig.rules !== currentConfig.rules) {
+    const newTempManifest = buildManifest({
+      version: pkg.version, platform: newConfig.platform, suite: newConfig.suite,
+      skills: newSkillList, agents: newAgentFiles, rules: newRuleFiles,
+      pipeline: newPipelineFiles, team: newConfig.team, aiCli: newConfig.aiCli,
+      rulesPreset: newConfig.rules, extras: oldManifest?.files?.extras || [],
+    });
+    const diff = diffManifest(oldManifest, newTempManifest);
+
+    // Remove orphaned skills/rules from existing platforms
+    for (const p of platformsToUpdate) {
+      if (diff.skills.removed.length) {
+        console.log(chalk.blue(`\n    删除多余 skills (${platformLabel(p)}):`));
+        await removeSkillFiles(p, projectRoot, diff.skills.removed, false);
+      }
+      if (diff.rules.removed.length) {
+        console.log(chalk.blue(`\n    删除多余 rules (${platformLabel(p)}):`));
+        await removeRuleFiles(p, projectRoot, diff.rules.removed, false);
+      }
+    }
+  }
+
+  // 5c. Install/update files for new + existing platforms
+  const allTargetPlatforms = [...platformsToAdd, ...platformsToUpdate];
+  const needsReinstall = newConfig.platform !== currentConfig.platform
+    || newConfig.suite !== currentConfig.suite
+    || newConfig.rules !== currentConfig.rules
+    || newConfig.team !== currentConfig.team;
+
+  for (const p of allTargetPlatforms) {
+    const isNew = platformsToAdd.includes(p);
+
+    if (isNew || needsReinstall) {
+      console.log(chalk.bold(`\n  ${isNew ? '安装' : '更新'} ${platformLabel(p)} 环境...\n`));
+
+      console.log(chalk.blue('    Skills:'));
+      await installSkills(p, newSkillList, projectRoot, false);
+
+      console.log(chalk.blue('\n    Agents:'));
+      await installAgents(p, projectRoot, false);
+
+      console.log(chalk.blue('\n    Settings & Rules:'));
+      await installSettings(p, projectRoot, { pipeline: newConfig.pipeline, rules: newConfig.rules }, false);
+
+      if (isNew) {
+        console.log(chalk.blue('\n    Project Memory:'));
+        await installProjectMemory(p, projectRoot, false);
+      }
+
+      if (newConfig.team) {
+        console.log(chalk.blue('\n    Team Config:'));
+        await installTeamConfig(p, projectRoot, false);
+      }
+    }
+  }
+
+  // 5d. Pipeline changes
+  if (newConfig.pipeline !== currentConfig.pipeline) {
+    if (newConfig.pipeline) {
+      console.log(chalk.blue('\n    安装 Pipeline:'));
+      await installPipeline(projectRoot, false);
+    } else {
+      console.log(chalk.blue('\n    移除 Pipeline 框架文件（保留 state/）:'));
+      const oldPipelineFiles = oldManifest?.files?.pipeline || [];
+      if (oldPipelineFiles.length) {
+        await removePipelineFiles(projectRoot, oldPipelineFiles, false);
+      }
+    }
+  }
+
+  // 5e. Update .gitignore
+  console.log(chalk.blue('\n    Gitignore:'));
+  await installGitignore(projectRoot, { pipeline: newConfig.pipeline }, false);
+
+  // 5f. Update .prizmkit/config.json (ai_cli)
+  if (newConfig.aiCli !== currentConfig.aiCli) {
+    const prizmkitDir = path.join(projectRoot, '.prizmkit');
+    await fs.ensureDir(prizmkitDir);
+    let existingConfig = {};
+    if (await fs.pathExists(configPath)) {
+      try { existingConfig = await fs.readJSON(configPath); } catch { /* ignore */ }
+    }
+    if (newConfig.aiCli) {
+      existingConfig.ai_cli = newConfig.aiCli;
+    } else {
+      delete existingConfig.ai_cli;
+    }
+    await fs.writeJSON(configPath, existingConfig, { spaces: 2 });
+    console.log(chalk.green(`\n      ✓ .prizmkit/config.json (ai_cli: ${newConfig.aiCli || '(cleared)'})`));
+  }
+
+  // 5g. Write new manifest
+  const newManifest = buildManifest({
+    version: pkg.version,
+    platform: newConfig.platform,
+    suite: newConfig.suite,
+    skills: newSkillList,
+    agents: newAgentFiles,
+    rules: newRuleFiles,
+    pipeline: newPipelineFiles,
+    team: newConfig.team,
+    aiCli: newConfig.aiCli,
+    rulesPreset: newConfig.rules,
+    extras: oldManifest?.files?.extras || [],
+  });
+
+  // Preserve original installedAt
+  if (oldManifest?.installedAt) {
+    newManifest.installedAt = oldManifest.installedAt;
+  }
+
+  await writeManifest(projectRoot, newManifest);
+  console.log(chalk.green('      ✓ .prizmkit/manifest.json'));
+
+  // ── Done ─────────────────────────────────────────────────────────────────
+
+  console.log('');
+  console.log(chalk.bold('  ════════════════════════════════════════════════'));
+  console.log(chalk.green.bold('  ✅ 配置变更完成！'));
+  console.log(chalk.bold('  ════════════════════════════════════════════════'));
+  console.log('');
+
+  console.log(chalk.gray('  新配置:'));
+  console.log(chalk.gray(`    平台:     ${platformLabel(newConfig.platform)}`));
+  console.log(chalk.gray(`    AI CLI:   ${newConfig.aiCli || '(未设置)'}`));
+  console.log(chalk.gray(`    技能套件: ${newConfig.suite}`));
+  console.log(chalk.gray(`    规则:     ${newConfig.rules}`));
+  console.log(chalk.gray(`    团队模式: ${newConfig.team ? '启用' : '禁用'}`));
+  console.log(chalk.gray(`    流水线:   ${newConfig.pipeline ? '启用' : '禁用'}`));
+  console.log('');
+}

package/src/prompts.js

@@ -0,0 +1,210 @@
+/**
+ * Reusable prompting functions for PrizmKit CLI.
+ * These functions encapsulate the interactive UI used by both install and config commands.
+ */
+
+import { select, confirm, checkbox, input } from '@inquirer/prompts';
+import chalk from 'chalk';
+
+/**
+ * Select target platform (codebuddy, claude, or both).
+ * @param {string} currentPlatform - current platform value
+ * @param {Object} detected - detected environment info (e.g., { cbc: true, claude: false })
+ * @returns {Promise<string>} - 'codebuddy', 'claude', or 'both'
+ */
+export async function selectPlatform(currentPlatform, detected = {}) {
+  const platform = await select({
+    message: '选择目标平台 (决定安装的目录结构):',
+    choices: [
+      {
+        name: `CodeBuddy (.codebuddy/)${detected.cbc ? chalk.green(' ← 已检测到 cbc') : ''}`,
+        value: 'codebuddy',
+      },
+      {
+        name: `Claude Code (.claude/)${(detected.claude || detected.claudeInternal) ? chalk.green(' ← 已检测到') : ''}`,
+        value: 'claude',
+      },
+      {
+        name: '同时安装两个平台',
+        value: 'both',
+      },
+    ],
+    default: currentPlatform || detected.suggested || 'claude',
+  });
+  return platform;
+}
+
+/**
+ * Select AI CLI command (cbc, claude, custom, or skip).
+ * @param {string} currentCommand - current AI CLI command
+ * @param {Object} detected - detected environment info
+ * @returns {Promise<string>} - 'cbc', 'claude', custom string, or ''
+ */
+export async function selectAiCli(currentCommand, detected = {}) {
+  const cliChoices = [
+    {
+      name: `cbc — CodeBuddy CLI${detected.cbc ? chalk.green(' ✓ 已安装') : chalk.gray(' (未检测到)')}`,
+      value: 'cbc',
+    },
+    {
+      name: `claude — Claude Code${detected.claude ? chalk.green(' ✓ 已安装') : chalk.gray(' (未检测到)')}`,
+      value: 'claude',
+    },
+    {
+      name: '自定义 — 输入其他命令',
+      value: '__custom__',
+    },
+    {
+      name: '跳过 — 稍后手动配置',
+      value: '',
+    },
+  ];
+
+  const knownCliValues = ['cbc', 'claude'];
+  const cliDefault = knownCliValues.includes(currentCommand)
+    ? currentCommand
+    : (currentCommand ? '__custom__' : (detected.suggestedCli || ''));
+
+  const cliSelection = await select({
+    message: '选择底层 AI CLI 可执行命令:',
+    choices: cliChoices,
+    default: cliDefault,
+  });
+
+  let aiCli = cliSelection;
+  if (cliSelection === '__custom__') {
+    aiCli = await input({
+      message: '输入自定义 AI CLI 命令:',
+      default: currentCommand || (detected.suggestedCli || ''),
+      validate: (v) => v.trim() ? true : '请输入命令',
+    });
+  }
+
+  return aiCli;
+}
+
+/**
+ * Select skill suite (core, minimal, or recommended:<type>).
+ * @param {string} currentSuite - current suite value
+ * @param {Object} metadata - skill metadata with suites definitions
+ * @returns {Promise<string>} - 'core', 'minimal', or 'recommended:type'
+ */
+export async function selectSkillSuite(currentSuite, metadata) {
+  const choices = [
+    {
+      name: `Core — 核心工作流 (${metadata.suites.core.skills.length} 个技能)`,
+      value: 'core',
+    },
+    {
+      name: `Minimal — 最小可用 (${metadata.suites.minimal.skills.length} 个技能)`,
+      value: 'minimal',
+    },
+  ];
+
+  // Add recommended options if available
+  if (metadata.recommendations) {
+    for (const [type, rec] of Object.entries(metadata.recommendations)) {
+      const baseSkills = rec.base === '*'
+        ? Object.keys(metadata.skills).length
+        : metadata.suites[rec.base]?.skills?.length || 0;
+      choices.push({
+        name: `Recommended: ${type} (${baseSkills} 个技能)`,
+        value: `recommended:${type}`,
+      });
+    }
+  }
+
+  const skillSuite = await select({
+    message: '选择技能套件:',
+    choices,
+    default: currentSuite || 'core',
+  });
+
+  return skillSuite;
+}
+
+/**
+ * Select external skills via checkbox.
+ * @param {Array<string>} currentSkills - currently selected external skills
+ * @param {Object} metadata - skill metadata with external_skills definitions
+ * @returns {Promise<Array<string>>} - array of selected skill names
+ */
+export async function selectExternalSkills(currentSkills, metadata) {
+  const knownExternalSkills = metadata.external_skills?.known || [];
+  if (knownExternalSkills.length === 0) {
+    return [];
+  }
+
+  const selectedSkills = await checkbox({
+    message: '选择要安装的第三方 Skills（可选，需要网络）:',
+    choices: knownExternalSkills.map(s => ({
+      name: `${s.name} — ${s.description}`,
+      value: s.name,
+      checked: (currentSkills || []).includes(s.name),
+    })),
+  });
+
+  return selectedSkills;
+}
+
+/**
+ * Confirm team mode setting.
+ * @param {boolean} currentValue - current team mode value
+ * @returns {Promise<boolean>}
+ */
+export async function confirmTeamMode(currentValue = true) {
+  const team = await confirm({
+    message: '启用多 Agent 团队模式 (prizm-dev-team)?',
+    default: currentValue,
+  });
+  return team;
+}
+
+/**
+ * Confirm pipeline setting.
+ * @param {boolean} currentValue - current pipeline value
+ * @returns {Promise<boolean>}
+ */
+export async function confirmPipeline(currentValue = true) {
+  const pipeline = await confirm({
+    message: '安装自动化流水线 (dev-pipeline)?',
+    default: currentValue,
+  });
+  return pipeline;
+}
+
+/**
+ * Select rules preset (recommended, minimal, or none).
+ * @param {string} currentPreset - current rules preset
+ * @returns {Promise<string>} - 'recommended', 'minimal', or 'none'
+ */
+export async function selectRulesPreset(currentPreset = 'recommended') {
+  const rulesPreset = await select({
+    message: '安装 AI 行为规则 (rules):',
+    choices: [
+      { name: 'Recommended — 全部规则 (推荐)', value: 'recommended' },
+      { name: 'Minimal — 仅渐进式加载 + 通用规则', value: 'minimal' },
+      { name: 'None — 不安装规则', value: 'none' },
+    ],
+    default: currentPreset,
+  });
+  return rulesPreset;
+}
+
+/**
+ * Display a summary of changes and confirm with user.
+ * @param {Object} summary - summary object with change descriptions
+ * @param {boolean} dryRun - whether this is a dry-run
+ * @returns {Promise<boolean>} - true if user confirms
+ */
+export async function confirmChanges(summary, dryRun = false) {
+  const message = dryRun
+    ? 'Review the changes above. These are the changes that would be made (dry-run mode).'
+    : 'Review the changes above. Proceed with configuration?';
+
+  const proceed = await confirm({
+    message,
+    default: true,
+  });
+  return proceed;
+}