create-claude-cabinet 0.12.1 → 0.13.0

package/lib/cli.js

@@ -373,7 +373,7 @@ const MODULES = {
     mandatory: false,
     default: true,
     lean: true,
-    templates: ['skills/onboard', 'skills/seed', 'skills/cc-upgrade', 'skills/link', 'skills/unlink', 'skills/extract'],
+    templates: ['skills/onboard', 'skills/seed', 'skills/cc-upgrade', 'skills/cc-link', 'skills/cc-unlink', 'skills/cc-extract'],
   },
   'validate': {
     name: 'Validate',
@@ -755,7 +755,7 @@ async function run() {
         // Note: publish is CC-source-repo-only, not shipped to consumers.
         const alwaysCopyPhases = [
           'skills/onboard', 'skills/seed',
-          'skills/cc-upgrade', 'skills/extract',
+          'skills/cc-upgrade', 'skills/cc-extract',
         ];
         const isSkill = tmpl.startsWith('skills/') && !alwaysCopyPhases.some(p => tmpl.startsWith(p));
         const results = await copyTemplates(srcPath, destPath, {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-cabinet",
-  "version": "0.12.1",
+  "version": "0.13.0",
   "description": "Claude Cabinet — opinionated process scaffolding for Claude Code projects",
   "bin": {
     "create-claude-cabinet": "bin/create-claude-cabinet.js"

package/templates/README.md

@@ -40,20 +40,20 @@ templates, see [EXTENSIONS.md](EXTENSIONS.md).
 | `skills/debrief-quick/` | Quick debrief variant — core phases only, skip presentation. |
 | `skills/execute/` | Execute a plan with cabinet member checkpoints. 3-checkpoint protocol (pre-implementation, per-file-group, pre-commit). 5 phase files. |
 | `skills/execute-plans/` | Batch execution of multiple plans with conflict detection. |
-| `skills/extract/` | Analyze project artifacts and propose upstream extraction candidates for Claude Cabinet. |
+| `skills/cc-extract/` | Analyze project artifacts and propose upstream extraction candidates for Claude Cabinet. |
 | `skills/investigate/` | Structured codebase exploration: frame, observe, hypothesize, test, conclude. |
-| `skills/link/` | Set up local development linking for Claude Cabinet source repo work. |
+| `skills/cc-link/` | Set up local development linking for Claude Cabinet source repo work. |
 | `skills/memory/` | Browse, search, and manage semantic memory via omega. |
 | `skills/menu/` | Dynamically discover and display all available skills. Reads from `_index.json`. |
 | `skills/onboard/` | Conversational onboarding. Interviews you, generates briefings, wires the session loop. Re-runnable. 8 phase files. |
 | `skills/orient/` | Session start. Load context, sync data, scan work, run health checks, spawn cabinet consultations, show skills menu. 7 phase files. |
 | `skills/orient-quick/` | Quick orient variant — core phases only, skip presentation. |
 | `skills/plan/` | Structured planning with cabinet critique. Research, overlap check, draft, critique, completeness, present, file. 9 phase files. |
-| `skills/publish/` | Publish workflow (CC source repo only, not shipped to consumers). |
+| `skills/cc-publish/` | Publish workflow (CC source repo only, not shipped to consumers). |
 | `skills/pulse/` | Self-description accuracy check. Count freshness, dead references, staleness. 3 phase files. |
 | `skills/seed/` | Recruit new cabinet members. Detect technology signals, propose expertise, build collaboratively. 4 phase files. |
 | `skills/triage-audit/` | Audit finding triage via local web UI or CLI. Load, present, apply verdicts. 3 phase files. |
-| `skills/unlink/` | Remove local development linking. Returns to published npm package. |
+| `skills/cc-unlink/` | Remove local development linking. Returns to published npm package. |
 | `skills/validate/` | Run structural validation checks. Validators defined in phase files. |
 | `skills/work-tracker/` | Open the work tracking UI interactively. Starts local server. |
 

package/templates/cabinet/directives-project.yaml

@@ -15,9 +15,9 @@
 # Format:
 #
 #   cabinet-record-keeper:
-#     standing-mandate: [publish]
+#     standing-mandate: [cc-publish]
 #     directives:
-#       publish: >
+#       cc-publish: >
 #         Check all docs for staleness and missing additions
 #         before the version is published.
 #

package/templates/skills/{extract → cc-extract}/SKILL.md

@@ -1,14 +1,14 @@
 ---
-name: extract
+name: cc-extract
 description: |
   Analyze non-CC skills, cabinet members, and other artifacts in a consuming
   project and propose candidates for upstreaming into Claude Cabinet as
   generic templates. Does not perform the extraction — files a proposal
   that surfaces during orient in the CC repo. Use when: "extract",
-  "upstream this", "should this be in CC?", "/extract".
+  "upstream this", "should this be in CC?", "/cc-extract".
 ---
 
-# /extract — Propose Artifacts for Upstreaming to CC
+# /cc-extract — Propose Artifacts for Upstreaming to CC
 
 ## Purpose
 
@@ -154,9 +154,9 @@ After filing, summarize:
 
 The user can target specific artifacts:
 
-- `/extract` — scan everything
-- `/extract skills/my-skill` — evaluate a specific skill
-- `/extract cabinet-members` — evaluate all custom cabinet members
+- `/cc-extract` — scan everything
+- `/cc-extract skills/my-skill` — evaluate a specific skill
+- `/cc-extract cabinet-members` — evaluate all custom cabinet members
 
 ## What This Does NOT Do
 

package/templates/skills/{link → cc-link}/SKILL.md

@@ -1,13 +1,13 @@
 ---
-name: link
+name: cc-link
 description: |
   Set up local development linking for Claude Cabinet. Detects whether
   you're in the CC source repo or a consuming project and runs the
   appropriate npm link command. Use when: "link", "local dev", "use local
-  CC", "/link".
+  CC", "/cc-link".
 ---
 
-# /link — Local Development Linking
+# /cc-link — Local Development Linking
 
 ## Purpose
 
@@ -21,7 +21,7 @@ Before doing anything, determine where you are:
 **CC source repo** (`package.json` has `name: "create-claude-cabinet"`):
 - Run `npm link` to register the package globally
 - This makes the local checkout available to any project that links to it
-- Tell the user: "Registered locally. In your other projects, run `/link`
+- Tell the user: "Registered locally. In your other projects, run `/cc-link`
   to connect them to this checkout."
 
 **Any other project** (anything that isn't the CC source repo):
@@ -38,7 +38,7 @@ Before doing anything, determine where you are:
 
 The CC source repo must have been linked first (`npm link` from the CC
 directory). If a consuming project tries to link and the global link
-doesn't exist, npm will error. In that case, tell the user to run `/link`
+doesn't exist, npm will error. In that case, tell the user to run `/cc-link`
 in their CC checkout first.
 
 ## What This Encodes

package/templates/skills/{publish → cc-publish}/SKILL.md

@@ -1,13 +1,13 @@
 ---
-name: publish
+name: cc-publish
 description: |
   Publish a new version of Claude Cabinet to npm. Analyzes changes since
   last release, suggests a version bump (patch/minor/major), updates
   package.json, commits, tags, and publishes. Use when: "publish",
-  "release", "ship it", "/publish".
+  "release", "ship it", "/cc-publish".
 ---
 
-# /publish — Release to npm
+# /cc-publish — Release to npm
 
 ## Purpose
 
@@ -74,8 +74,7 @@ With user confirmation:
   present, run a full install (`node bin/create-claude-cabinet.js --yes`).
   If only lean modules, run `--lean`. Never downgrade a full install to
   lean.
-- After the install, verify `package.json` wasn't corrupted (the db-setup
-  module adds `"type": "module"` which may not be wanted — check if the
-  pre-install `package.json` had it and revert if not).
+- After the install, verify `package.json` wasn't corrupted — check that
+  no unexpected fields were added or existing fields changed.
 - Update `system-status.md` if it exists
 - Report the published version and npm URL

package/templates/skills/{unlink → cc-unlink}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: unlink
+name: cc-unlink
 description: |
   Remove local development linking for Claude Cabinet. Returns the
   project to using the published npm version. Use when: "unlink",
-  "stop using local CC", "use published version", "/unlink".
+  "stop using local CC", "use published version", "/cc-unlink".
 ---
 
-# /unlink — Remove Local Development Link
+# /cc-unlink — Remove Local Development Link
 
 ## Purpose
 

package/templates/skills/debrief/SKILL.md

@@ -307,7 +307,7 @@ it in the report for the user to confirm, edit, or dismiss. If
 confirmed, the feedback is delivered to the CC repo (via local link
 or GitHub issue). If nothing — the phase is silent.
 
-This is different from `/extract` (which proposes generalizable
+This is different from `/cc-extract` (which proposes generalizable
 artifacts for upstreaming). This captures field friction: what hurt,
 what was confusing, what needed a workaround.
 
@@ -341,7 +341,7 @@ If the user says no, move on.
 **Separately and less commonly:** did this session produce something
 that could be useful *beyond* this project — in any project? A
 generalizable pattern, cabinet member, or convention? If so, mention
-`/extract` as an option for proposing it upstream to CC. This is
+`/cc-extract` as an option for proposing it upstream to CC. This is
 rarer than project-specific skills.
 
 ### 11. Cabinet Check (core)

package/templates/skills/debrief/phases/upstream-feedback.md

@@ -19,7 +19,7 @@ one narrow question: **was there friction with anything CC provided?**
 - A missing capability that required a workaround
 - An unclear SKILL.md that led to wasted time
 
-This is NOT the same as `/extract` (which looks for generalizable
+This is NOT the same as `/cc-extract` (which looks for generalizable
 artifacts to upstream). This is field feedback — "this thing you shipped
 hurt when I used it."
 
@@ -75,7 +75,7 @@ friction points (rare), present each separately.
 ### 4. Deliver
 
 If the user confirms, deliver the feedback. Detection and delivery
-follow the same pattern as `/extract`:
+follow the same pattern as `/cc-extract`:
 
 **If linked** (the CC package resolves to a local directory — check
 if `node -e "console.log(require.resolve('create-claude-cabinet'))"`