create-claude-cabinet 0.6.0 → 0.6.2

package/README.md

@@ -26,11 +26,11 @@ and weigh in when their expertise matters:
 Open a terminal, `cd` into your project folder, and run:
 
 ```bash
-curl -fsSL https://raw.githubusercontent.com/orenmagid/claude-on-rails/main/install.sh | bash
+curl -fsSL https://raw.githubusercontent.com/orenmagid/claude-cabinet/main/install.sh | bash
 ```
 
 That's it. If you don't have git or Node.js, it installs them.
-No choices to make — it sets up everything.
+No choices to make — you get everything.
 
 Then open [Claude Code](https://claude.ai/code) in the same folder and
 say `/onboard`. It'll interview you about your project and set everything
@@ -41,8 +41,8 @@ step-by-step walkthrough.
 
 ### For developers
 
-If you have Node.js installed and want interactive module selection,
-database setup, or the full install:
+If you have Node.js installed and want to choose which modules to
+install, or want the lean option (skips work tracking and compliance):
 
 ```bash
 npx create-claude-cabinet
@@ -55,42 +55,93 @@ it's done, open Claude Code and run `/onboard`.
 ## What You Get
 
 ### The Session Loop (always installed)
-- **`/orient`** — session briefing. Reads project state, checks health,
-  surfaces what needs attention. Every session starts informed.
-- **`/debrief`** — session close. Marks work done, records lessons,
-  updates state. Every session closes the loop so the next one starts
-  clean.
-
-### The Cabinet (opt-in)
-20 expert cabinet members who audit your project from their domain:
-**speed-freak** watches performance, **boundary-man** catches edge cases,
-**record-keeper** flags when docs drift from code, **workflow-cop**
+
+This is the foundation. You run these commands — they don't happen
+automatically.
+
+- **`/orient`** — open every session with this. Claude reads project
+  state, checks health, surfaces what needs attention, and briefs you
+  so you never start blind. Think of it as the morning briefing before
+  the cabinet gets to work.
+- **`/debrief`** — close every session with this. Claude marks work
+  done, records lessons, updates state, and prepares the briefing for
+  next time. Without debrief, the next orient starts with stale
+  information. The loop is what gives Claude memory across sessions.
+
+**The habit matters.** Orient and debrief take 30 seconds each. Skip
+them and sessions start from zero — Claude forgets what happened,
+repeats mistakes, and you spend the first 10 minutes re-explaining
+context. Keep the loop and each session picks up where the last one
+left off.
+
+### The Cabinet (included in lean)
+
+20 expert cabinet members who each own a domain and stay in their lane.
+**Speed-freak** watches performance. **Boundary-man** catches edge cases.
+**Record-keeper** flags when docs drift from code. **Workflow-cop**
 evaluates whether your process actually works. Each member has a
-portfolio, stays in it, and produces structured findings you can
-triage. Convene the whole cabinet or just the committee you need.
+portfolio, produces structured findings, and knows when to speak up
+and when to stay quiet.
+
+You convene the cabinet with **`/audit`** — run it occasionally (every
+few sessions, or before a release) to get a full review from every
+relevant member. You don't need to audit every session. The cabinet
+waits until called.
+
+Members are organized into **committees** — groups by concern, so you
+can convene just the experts you need. Security review? Convene the
+security committee. Performance concerns? Just the speed committee.
+
+### Planning + Execution (included in lean)
+
+Don't just start building — brief the cabinet first.
+
+- **`/plan`** — describe what you want to build. Claude drafts a plan,
+  then the relevant cabinet members critique it before a single line is
+  written. The security member notices the missing auth check. The
+  data integrity member catches the NULL handling gap. You approve the
+  plan, and it carries enough detail for any future session to execute
+  without re-exploring.
+- **`/execute`** — pick up an approved plan and build it step by step.
+  Cabinet members watch at each checkpoint. The plan tells Claude what
+  to do; execute makes sure it gets done right.
 
-### Planning + Execution (opt-in)
-- **`/plan`** — structured planning with cabinet critique. Before you
-  build, the relevant members weigh in on your approach.
-- **`/execute`** — step-through execution with checkpoints. Cabinet
-  members watch at each stage.
+### Work Tracking (full install)
 
-### Work Tracking (opt-in)
 Local SQLite database for actions, projects, and status tracking. Claude
 reads and writes it directly — no external service needed. Skip this if
 you already use GitHub Issues, Linear, or something else.
 
-### Compliance Stack (opt-in)
+### Compliance Stack (full install)
+
 Scoped instructions in `.claude/rules/` that load by file path. An
 enforcement pipeline that promotes recurring feedback into deterministic
 hooks — things that keep going wrong become things that can't go wrong.
 
-### Lifecycle (opt-in)
-- **`/onboard`** — conversational project interview, re-runnable as the
-  project matures.
-- **`/seed`** — detects new tech in your project, recruits cabinet
-  members with the right expertise.
-- **`/cor-upgrade`** — conversational merge when Claude Cabinet updates.
+### Lifecycle (included in lean)
+
+- **`/onboard`** — the cabinet's first briefing. Claude interviews you
+  about your project and prepares everything the members need to do
+  their jobs. Re-run it as the project matures — the interview adapts.
+- **`/seed`** — recruit new members. Claude detects new tech in your
+  project and proposes expert members to cover it. Your cabinet grows
+  with your project.
+- **`/cc-upgrade`** — when Claude Cabinet publishes updates, this skill
+  runs the installer for the mechanical parts and walks you through
+  what changed conversationally. Intelligence is the merge strategy.
+
+## Your Workflow
+
+The day-to-day rhythm:
+
+1. **Start a session** → `/orient` (get briefed)
+2. **Do your work** → talk to Claude, use `/plan` for anything non-trivial
+3. **Build it** → `/execute` to implement approved plans with cabinet oversight
+4. **Check quality** → `/audit` occasionally for a full cabinet review
+5. **Close the session** → `/debrief` (close the loop)
+
+Steps 1 and 5 are the minimum. Everything in between is yours to use as
+needed. The more you use, the more the cabinet learns about your project.
 
 ## How It Works
 
@@ -135,7 +186,7 @@ scripts/
 ├── pib-db.js        # work tracking CLI (if installed)
 └── ...              # triage tools (if audit installed)
 
-.corrc.json          # installation metadata
+.ccrc.json           # installation metadata
 ```
 
 ## Upgrading
@@ -144,13 +195,13 @@ Re-run the installer to pick up new versions:
 
 ```bash
 # Shell installer (re-downloads latest)
-curl -fsSL https://raw.githubusercontent.com/orenmagid/claude-on-rails/main/install.sh | bash
+curl -fsSL https://raw.githubusercontent.com/orenmagid/claude-cabinet/main/install.sh | bash
 
 # npm installer (if using Node.js)
 npx create-claude-cabinet
 ```
 
-In Claude Code, run `/cor-upgrade` for conversational merge of upstream
+In Claude Code, run `/cc-upgrade` for conversational merge of upstream
 changes with your customizations.
 
 ## Works Across Projects
@@ -160,7 +211,7 @@ with Claude everywhere.
 
 - **Your identity** (`~/.claude/CLAUDE.md`) — set up once, carries to
   every project. Claude always knows who you are and what you do.
-- **Project registry** (`~/.claude/cor-registry.json`) — tracks all
+- **Project registry** (`~/.claude/cc-registry.json`) — tracks all
   your projects. `/onboard` asks how they relate; `/orient` flags
   when work in one might affect another.
 - **Debrief maintenance** — if you mention something new about yourself

package/lib/cli.js

@@ -24,7 +24,7 @@ const MODULES = {
     mandatory: false,
     default: true,
     lean: true,
-    templates: ['hooks/git-guardrails.sh', 'hooks/cor-upstream-guard.sh', 'hooks/skill-telemetry.sh', 'hooks/skill-tool-telemetry.sh', 'scripts/cor-drift-check.cjs'],
+    templates: ['hooks/git-guardrails.sh', 'hooks/cc-upstream-guard.sh', 'hooks/skill-telemetry.sh', 'hooks/skill-tool-telemetry.sh', 'scripts/cc-drift-check.cjs'],
   },
   'work-tracking': {
     name: 'Work Tracking (pib-db or markdown)',
@@ -62,7 +62,7 @@ const MODULES = {
       'cabinet', 'briefing',
       'skills/cabinet-accessibility', 'skills/cabinet-anti-confirmation',
       'skills/cabinet-architecture', 'skills/cabinet-boundary-man',
-      'skills/cabinet-cor-health', 'skills/cabinet-data-integrity',
+      'skills/cabinet-cc-health', 'skills/cabinet-data-integrity',
       'skills/cabinet-debugger', 'skills/cabinet-historian',
       'skills/cabinet-organized-mind', 'skills/cabinet-process-therapist',
       'skills/cabinet-qa', 'skills/cabinet-record-keeper',
@@ -76,12 +76,12 @@ const MODULES = {
     ],
   },
   'lifecycle': {
-    name: 'Lifecycle (onboard + seed + cor-upgrade + link)',
+    name: 'Lifecycle (onboard + seed + cc-upgrade + link)',
     description: 'Onboarding prepares the briefings. Seed proposes new cabinet members when you adopt new tech.',
     mandatory: false,
     default: true,
     lean: true,
-    templates: ['skills/onboard', 'skills/seed', 'skills/cor-upgrade', 'skills/link', 'skills/unlink', 'skills/publish', 'skills/extract'],
+    templates: ['skills/onboard', 'skills/seed', 'skills/cc-upgrade', 'skills/link', 'skills/unlink', 'skills/publish', 'skills/extract'],
   },
   'validate': {
     name: 'Validate',
@@ -105,7 +105,7 @@ function detectProjectState(dir) {
   const entries = fs.readdirSync(dir);
   const signals = entries.filter(e => PROJECT_SIGNALS.includes(e));
   const hasClaude = entries.includes('.claude');
-  const hasPibrc = fs.existsSync(path.join(dir, '.corrc.json'));
+  const hasPibrc = fs.existsSync(path.join(dir, '.ccrc.json'));
 
   if (hasPibrc) return 'existing-install';
   if (signals.length > 0) return 'existing-project';
@@ -161,7 +161,7 @@ function printHelp() {
     npx create-claude-cabinet --lean          Session loop + planning + cabinet
     npx create-claude-cabinet --yes --no-db   Install everything except DB
     npx create-claude-cabinet --dry-run       Preview what would be installed
-    npx create-claude-cabinet --reset         Remove CoR files safely
+    npx create-claude-cabinet --reset         Remove CC files safely
     npx create-claude-cabinet --reset --dry-run  Preview what --reset would do
 `);
 }
@@ -193,16 +193,16 @@ async function run() {
 
   // --- User identity + project registry ---
   const claudeHome = path.join(os.homedir(), '.claude');
-  const registryPath = path.join(claudeHome, 'cor-registry.json');
+  const registryPath = path.join(claudeHome, 'cc-registry.json');
   const claudeMdPath = path.join(claudeHome, 'CLAUDE.md');
 
   if (!flags.dryRun) {
     if (!fs.existsSync(claudeHome)) fs.mkdirSync(claudeHome, { recursive: true });
   }
 
-  // First-ever CoR install: set up user identity
-  const firstCorInstall = !fs.existsSync(registryPath);
-  if (firstCorInstall && !flags.yes && !flags.lean && !flags.dryRun) {
+  // First-ever CC install: set up user identity
+  const firstCcInstall = !fs.existsSync(registryPath);
+  if (firstCcInstall && !flags.yes && !flags.lean && !flags.dryRun) {
     const claudeMdContent = fs.existsSync(claudeMdPath) ? fs.readFileSync(claudeMdPath, 'utf8') : '';
     if (!claudeMdContent.includes('# About Me')) {
       console.log('  This looks like your first time assembling a cabinet.');
@@ -432,11 +432,11 @@ async function run() {
         // use skeleton defaults. Phase files are created by /onboard
         // based on the project interview, not copied as generic templates.
         // Exception: cabinet members (always copied), and skills whose phase
-        // files ARE the instructions (onboard, seed, cor-upgrade, publish,
+        // files ARE the instructions (onboard, seed, cc-upgrade, publish,
         // extract) — these need their phases to function.
         const alwaysCopyPhases = [
           'skills/onboard', 'skills/seed',
-          'skills/cor-upgrade', 'skills/publish', 'skills/extract',
+          'skills/cc-upgrade', 'skills/publish', 'skills/extract',
         ];
         const isSkill = tmpl.startsWith('skills/') && !alwaysCopyPhases.some(p => tmpl.startsWith(p));
         const results = await copyTemplates(srcPath, destPath, {
@@ -566,7 +566,7 @@ async function run() {
       version: VERSION,
       manifest: allManifest,
     });
-    console.log('  📝 Created .corrc.json');
+    console.log('  📝 Created .ccrc.json');
   }
 
   // --- Update project registry ---

package/lib/metadata.js

@@ -1,7 +1,7 @@
 const fs = require('fs');
 const path = require('path');
 
-const METADATA_FILE = '.corrc.json';
+const METADATA_FILE = '.ccrc.json';
 
 function metadataPath(projectDir) {
   return path.join(projectDir, METADATA_FILE);

package/lib/reset.js

@@ -4,8 +4,8 @@ const crypto = require('crypto');
 const { read: readMetadata, METADATA_FILE } = require('./metadata');
 const { DEFAULT_HOOKS } = require('./settings-merge');
 
-// CoR-managed hook command patterns — used to identify hooks to remove
-const COR_HOOK_PATTERNS = [
+// CC-managed hook command patterns — used to identify hooks to remove
+const CC_HOOK_PATTERNS = [
   '.claude/hooks/git-guardrails.sh',
   '.claude/hooks/skill-telemetry.sh',
   '.claude/hooks/skill-tool-telemetry.sh',
@@ -29,10 +29,10 @@ function reconstructManifest(metadata) {
 }
 
 /**
- * Remove CoR files from a project using the manifest for safety.
+ * Remove CC files from a project using the manifest for safety.
  *
  * For each manifest entry:
- * - Hash matches → remove (unmodified CoR file)
+ * - Hash matches → remove (unmodified CC file)
  * - Hash differs → skip with [CUSTOMIZED] warning (unless --force)
  * - File missing → skip (already removed)
  *
@@ -49,7 +49,7 @@ async function reset(projectDir, { dryRun = false, force = false } = {}) {
 
   const metadata = readMetadata(projectDir);
   if (!metadata) {
-    console.log('  No .corrc.json found — nothing to reset.');
+    console.log('  No .ccrc.json found — nothing to reset.');
     return;
   }
 
@@ -60,7 +60,7 @@ async function reset(projectDir, { dryRun = false, force = false } = {}) {
   if (!manifest || Object.keys(manifest).length === 0) {
     manifest = reconstructManifest(metadata);
     if (Object.keys(manifest).length === 0) {
-      console.log('  Could not reconstruct manifest. Use --force to remove all CoR directories.\n');
+      console.log('  Could not reconstruct manifest. Use --force to remove all CC directories.\n');
       if (!force) return;
     }
   }
@@ -101,7 +101,7 @@ async function reset(projectDir, { dryRun = false, force = false } = {}) {
     }
   }
 
-  // Clean CoR hooks from settings.json
+  // Clean CC hooks from settings.json
   const settingsPath = path.join(projectDir, '.claude', 'settings.json');
   let hooksRemoved = 0;
   if (fs.existsSync(settingsPath)) {
@@ -110,7 +110,7 @@ async function reset(projectDir, { dryRun = false, force = false } = {}) {
       for (const [event, hookGroups] of Object.entries(settings.hooks)) {
         const filtered = hookGroups.filter(group => {
           const commands = group.hooks.map(h => h.command);
-          return !commands.some(cmd => COR_HOOK_PATTERNS.includes(cmd));
+          return !commands.some(cmd => CC_HOOK_PATTERNS.includes(cmd));
         });
         const removedCount = hookGroups.length - filtered.length;
         hooksRemoved += removedCount;
@@ -133,7 +133,7 @@ async function reset(projectDir, { dryRun = false, force = false } = {}) {
     }
   }
 
-  // Remove .corrc.json last
+  // Remove .ccrc.json last
   const pibrcPath = path.join(projectDir, METADATA_FILE);
   if (!dryRun && fs.existsSync(pibrcPath)) {
     fs.unlinkSync(pibrcPath);
@@ -160,7 +160,7 @@ async function reset(projectDir, { dryRun = false, force = false } = {}) {
   }
 
   if (hooksRemoved > 0) {
-    console.log(`  🔧 Removed ${hooksRemoved} CoR hook${hooksRemoved === 1 ? '' : 's'} from settings.json`);
+    console.log(`  🔧 Removed ${hooksRemoved} CC hook${hooksRemoved === 1 ? '' : 's'} from settings.json`);
   }
 
   if (!dryRun) {

package/lib/settings-merge.js

@@ -17,7 +17,7 @@ const DEFAULT_HOOKS = {
       hooks: [
         {
           type: 'command',
-          command: '.claude/hooks/cor-upstream-guard.sh',
+          command: '.claude/hooks/cc-upstream-guard.sh',
         },
       ],
     },

package/package.json

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

package/templates/README.md

@@ -59,7 +59,7 @@ adoption is straightforward: copy what you need into your project's
 | `skills/triage-audit/SKILL.md` | 5 | **Triage skeleton.** Load findings, prepare commentary, present via local web UI or CLI, apply verdicts (fix/defer/reject), create actions for approved findings. 3 phase files. |
 | `skills/onboard/SKILL.md` | 7 | **Onboarding skeleton.** Conversational interview that generates the initial context layer. Re-runnable: first run generates, subsequent runs refine. 6 phase files. |
 | `skills/seed/SKILL.md` | 7 | **Capability seeding skeleton.** Detects technology adoption signals, proposes expertise conversations, builds and maintains cabinet members collaboratively. 4 phase files. |
-| `skills/cor-upgrade/SKILL.md` | 7 | **Upgrade skeleton.** Conversational merge when new Claude Cabinet skeletons arrive. Intelligence is the merge strategy — conversation, not mechanical copy. 4 phase files. |
+| `skills/cc-upgrade/SKILL.md` | 7 | **Upgrade skeleton.** Conversational merge when new Claude Cabinet skeletons arrive. Intelligence is the merge strategy — conversation, not mechanical copy. 4 phase files. |
 
 ### Scripts (6)
 
@@ -106,7 +106,7 @@ execution, audit). Each is a named domain expert encoded in markdown.
 
 | Cabinet Member | Domain | Activation |
 |------------|--------|-----------|
-| `cor-health` | Claude Cabinet adoption health, phase file coverage, configuration drift, anti-bloat | Always-on during audit |
+| `cc-health` | Claude Cabinet adoption health, phase file coverage, configuration drift, anti-bloat | Always-on during audit |
 
 **Infrastructure files (7):**
 
@@ -395,7 +395,7 @@ There is no `box.yaml` or template engine. Configuration uses two mechanisms:
   (GTD expertise, Mantine quality, sync health, etc.). EXTENSIONS.md
   includes examples showing how to write your own domain cabinet members.
 - **Distribution mechanism** — No npm package, no installer. Copy files.
-  The `/onboard` skill guides adoption. The `/cor-upgrade` skill handles updates.
+  The `/onboard` skill guides adoption. The `/cc-upgrade` skill handles updates.
 
 ## Relationship to Flow
 
@@ -430,7 +430,7 @@ This package includes all 7 waves of the extraction:
    reusable patterns, cabinet member writing guide with 3 examples)
 7. **Lifecycle layer** — done (onboard skeleton for project adoption with
    3-mode re-runnability, seed skeleton for capability seeding from tech
-   signals, upgrade skeleton for conversational box updates, cor-health
+   signals, upgrade skeleton for conversational box updates, cc-health
    cabinet member for adoption monitoring, pib-db enhancements: status
    tracking, tags, update-action command, migration logic)
 

package/templates/briefing/_briefing-template.md

@@ -71,7 +71,7 @@ Which cabinet members need which briefing files (identity is always loaded):
 | anti-confirmation     |     |     |     |     |     |
 | architecture          |  x  |  x  |     |     |     |
 | boundary-man          |  x  |  x  |     |     |     |
-| cor-health            |     |  x  |  x  |     |     |
+| cc-health             |     |  x  |  x  |     |     |
 | data-integrity        |  x  |  x  |     |     |  x  |
 | debugger              |  x  |     |     |     |     |
 | record-keeper         |     |  x  |     |     |     |
@@ -118,7 +118,7 @@ exists so cabinet members know what's available.
   only if the interview produced content for them.
 - **/seed** adds domain extension files when specialized cabinet members
   are adopted.
-- **/cor-upgrade** can migrate a monolithic `_briefing.md` into the
+- **/cc-upgrade** can migrate a monolithic `_briefing.md` into the
   split format.
 
 ## Backward Compatibility
@@ -131,7 +131,7 @@ or if no `briefing` field is present, the system falls back to reading
 - Existing projects with a monolithic `_briefing.md` continue to work
   without changes.
 - Projects can migrate incrementally — split out one file at a time.
-- `/cor-upgrade` handles the full migration when the project is ready.
+- `/cc-upgrade` handles the full migration when the project is ready.
 
 ## Finding Format
 

package/templates/cabinet/committees-template.yaml

@@ -46,4 +46,4 @@ committees:
   #     - workflow-cop
   #     - record-keeper
   #     - process-therapist
-  #     - cor-health          # CoR adoption health, configuration drift, anti-bloat
+  #     - cc-health           # CC adoption health, configuration drift, anti-bloat

package/templates/hooks/{cor-upstream-guard.sh → cc-upstream-guard.sh}

@@ -1,12 +1,12 @@
 #!/bin/bash
-# CoR Upstream Guard — PreToolUse hook for Edit and Write tool calls
+# CC Upstream Guard — PreToolUse hook for Edit and Write tool calls
 #
 # Blocks modifications to files managed by Claude Cabinet. These files
-# are upstream-owned: updates come through /cor-upgrade, not direct edits.
+# are upstream-owned: updates come through /cc-upgrade, not direct edits.
 # Project-specific customization goes in briefing files and phase files.
 #
 # How it works:
-#   Reads .corrc.json manifest (list of CoR-installed files with hashes).
+#   Reads .ccrc.json manifest (list of CC-installed files with hashes).
 #   If the target file_path is in the manifest, block the write.
 #
 # ROLLBACK: Comment out the PreToolUse entry for this hook in
@@ -24,12 +24,12 @@ if [ -z "$FILE_PATH" ]; then
   exit 0
 fi
 
-# Find the project root (where .corrc.json lives)
+# Find the project root (where .ccrc.json lives)
 # Walk up from current directory
 find_project_root() {
   local dir="$PWD"
   while [ "$dir" != "/" ]; do
-    if [ -f "$dir/.corrc.json" ]; then
+    if [ -f "$dir/.ccrc.json" ]; then
       echo "$dir"
       return 0
     fi
@@ -41,7 +41,7 @@ find_project_root() {
 PROJECT_ROOT=$(find_project_root)
 
 if [ -z "$PROJECT_ROOT" ]; then
-  # No .corrc.json found — not a CoR project, allow everything
+  # No .ccrc.json found — not a CC project, allow everything
   echo '{"decision":"allow"}'
   exit 0
 fi
@@ -64,7 +64,7 @@ fi
 IN_MANIFEST=$(python3 -c "
 import json, sys
 try:
-    with open('$PROJECT_ROOT/.corrc.json') as f:
+    with open('$PROJECT_ROOT/.ccrc.json') as f:
         data = json.load(f)
     manifest = data.get('manifest', {})
     print('yes' if '$REL_PATH' in manifest else 'no')
@@ -73,7 +73,7 @@ except:
 " 2>/dev/null)
 
 if [ "$IN_MANIFEST" = "yes" ]; then
-  echo "{\"decision\":\"block\",\"reason\":\"Blocked: $REL_PATH is managed by Claude Cabinet. CoR-managed files are upstream-owned — edits come through /cor-upgrade, not direct modification. Put project-specific content in briefing files or phase files instead.\"}"
+  echo "{\"decision\":\"block\",\"reason\":\"Blocked: $REL_PATH is managed by Claude Cabinet. CC-managed files are upstream-owned — edits come through /cc-upgrade, not direct modification. Put project-specific content in briefing files or phase files instead.\"}"
 else
   echo '{"decision":"allow"}'
 fi

package/templates/hooks/skill-telemetry.sh

@@ -21,7 +21,6 @@ SKILLS=""
 for skill_path in "$SKILL_DIR"/*/SKILL.md; do
     [ -f "$skill_path" ] || continue
     skill=$(basename "$(dirname "$skill_path")")
-    [ "$skill" = "perspectives" ] && continue
     [ "$skill" = "_template" ] && continue
     SKILLS="$SKILLS $skill"
 done

package/templates/scripts/{cor-drift-check.cjs → cc-drift-check.cjs}

@@ -1,13 +1,13 @@
 #!/usr/bin/env node
-// CoR Drift Check — detect modified upstream-managed files
+// CC Drift Check — detect modified upstream-managed files
 //
-// Compares current file hashes against .corrc.json manifest hashes.
+// Compares current file hashes against .ccrc.json manifest hashes.
 // Reports files that have been modified since install (drift).
 //
 // Usage:
-//   node scripts/cor-drift-check.js          # exit 0 if clean, 1 if drift
-//   node scripts/cor-drift-check.js --json   # output JSON for programmatic use
-//   node scripts/cor-drift-check.js --fix    # show what /cor-upgrade would fix
+//   node scripts/cc-drift-check.js          # exit 0 if clean, 1 if drift
+//   node scripts/cc-drift-check.js --json   # output JSON for programmatic use
+//   node scripts/cc-drift-check.js --fix    # show what /cc-upgrade would fix
 
 const fs = require('fs');
 const path = require('path');
@@ -15,18 +15,18 @@ const crypto = require('crypto');
 
 const projectRoot = findProjectRoot();
 if (!projectRoot) {
-  console.error('No .corrc.json found — not a CoR project.');
+  console.error('No .ccrc.json found — not a CC project.');
   process.exit(2);
 }
 
-const metadataPath = path.join(projectRoot, '.corrc.json');
+const metadataPath = path.join(projectRoot, '.ccrc.json');
 const metadata = JSON.parse(fs.readFileSync(metadataPath, 'utf8'));
 const manifest = metadata.manifest || {};
 
 function findProjectRoot() {
   let dir = process.cwd();
   while (dir !== path.dirname(dir)) {
-    if (fs.existsSync(path.join(dir, '.corrc.json'))) return dir;
+    if (fs.existsSync(path.join(dir, '.ccrc.json'))) return dir;
     dir = path.dirname(dir);
   }
   return null;
@@ -64,7 +64,7 @@ if (args.includes('--json')) {
   console.log(JSON.stringify({ drifted, missing, clean: clean.length }, null, 2));
 } else {
   if (drifted.length === 0 && missing.length === 0) {
-    console.log(`All ${clean.length} CoR-managed files match upstream hashes.`);
+    console.log(`All ${clean.length} CC-managed files match upstream hashes.`);
   } else {
     if (drifted.length > 0) {
       console.log(`Drifted (${drifted.length} files modified from upstream):`);
@@ -76,7 +76,7 @@ if (args.includes('--json')) {
     }
     console.log(`\nClean: ${clean.length} files match.`);
     if (args.includes('--fix')) {
-      console.log('\nRun /cor-upgrade to restore drifted files to upstream versions.');
+      console.log('\nRun /cc-upgrade to restore drifted files to upstream versions.');
     }
   }
 }