create-claude-rails 0.5.3 → 0.5.5

package/README.md

@@ -137,6 +137,23 @@ npx create-claude-rails
 In Claude Code, run `/cor-upgrade` for conversational merge of upstream
 changes with your customizations.
 
+## Works Across Projects
+
+Claude on Rails isn't just for one project — it manages how you work
+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
+  your CoR projects. `/onboard` asks how they relate; `/orient` flags
+  when work in one might affect another.
+- **Debrief maintenance** — if you mention something new about yourself
+  or your project evolves, `/debrief` proposes updating your profile
+  and registry so the next session starts current.
+
+Install in each project folder. They're independent but aware of each
+other.
+
 ## Philosophy
 
 This started as the process layer of [Flow](https://github.com/orenmagid/flow),

package/lib/cli.js

@@ -1,6 +1,7 @@
 const prompts = require('prompts');
 const path = require('path');
 const fs = require('fs');
+const os = require('os');
 const crypto = require('crypto');
 const { copyTemplates } = require('./copy');
 const { mergeSettings } = require('./settings-merge');
@@ -180,6 +181,36 @@ async function run() {
 
   let projectDir = path.resolve(flags.targetDir);
 
+  // --- User identity + project registry ---
+  const claudeHome = path.join(os.homedir(), '.claude');
+  const registryPath = path.join(claudeHome, 'cor-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) {
+    const claudeMdContent = fs.existsSync(claudeMdPath) ? fs.readFileSync(claudeMdPath, 'utf8') : '';
+    if (!claudeMdContent.includes('# About Me')) {
+      console.log('  This looks like your first time using Claude on Rails.');
+      console.log('  Quick question so Claude knows who you are across all projects.\n');
+      const { userName } = await prompts({ type: 'text', name: 'userName', message: "What's your name?" });
+      const { userRole } = await prompts({ type: 'text', name: 'userRole', message: 'What do you do? (e.g. "I run a bakery", "I\'m a freelance designer")' });
+      if (userName || userRole) {
+        let profile = '\n# About Me\n\n';
+        if (userName) profile += `Name: ${userName}\n`;
+        if (userRole) profile += `${userRole}\n`;
+        profile += '\n<!-- Added by Claude on Rails. Claude sees this in every project. -->\n';
+        profile += '<!-- Edit ~/.claude/CLAUDE.md to update. -->\n';
+        fs.appendFileSync(claudeMdPath, profile);
+        console.log('\n  ✓ Saved to ~/.claude/CLAUDE.md — Claude will know this everywhere.\n');
+      }
+    }
+  }
+
   // --- Directory detection ---
   const dirState = detectProjectState(projectDir);
 
@@ -528,6 +559,41 @@ async function run() {
     console.log('  📝 Created .corrc.json');
   }
 
+  // --- Update project registry ---
+  if (!flags.dryRun) {
+    try {
+      let registry = { projects: [] };
+      if (fs.existsSync(registryPath)) {
+        registry = JSON.parse(fs.readFileSync(registryPath, 'utf8'));
+      }
+      const existingIdx = registry.projects.findIndex(p => p.path === projectDir);
+      const entry = {
+        path: projectDir,
+        name: path.basename(projectDir),
+        description: '',
+        version: VERSION,
+        updatedAt: new Date().toISOString(),
+      };
+      if (existingIdx >= 0) {
+        entry.name = registry.projects[existingIdx].name || entry.name;
+        entry.description = registry.projects[existingIdx].description || '';
+        registry.projects[existingIdx] = entry;
+      } else {
+        // Register with folder name. /onboard fills in name and description later.
+        registry.projects.push(entry);
+      }
+      fs.writeFileSync(registryPath, JSON.stringify(registry, null, 2) + '\n');
+      const otherCount = registry.projects.filter(p => p.path !== projectDir).length;
+      if (otherCount > 0) {
+        console.log(`  📋 Registered in project registry (${otherCount} other project${otherCount === 1 ? '' : 's'})`);
+      } else {
+        console.log('  📋 Registered in project registry');
+      }
+    } catch (err) {
+      // Non-fatal — registry is nice-to-have
+    }
+  }
+
   // --- Summary ---
   console.log('\n  ✅ Claude on Rails installed!\n');
   console.log('  Next steps:');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-rails",
-  "version": "0.5.3",
+  "version": "0.5.5",
   "description": "Claude on Rails — opinionated process scaffolding for Claude Code projects",
   "bin": {
     "create-claude-rails": "bin/create-claude-rails.js"

package/templates/skills/debrief/SKILL.md

@@ -149,6 +149,17 @@ reality so the next orient reads accurate information.
 (or equivalent) needs updating to reflect what was built, fixed, or
 changed.
 
+Also check the **user-level state** (silently — don't make this a
+conversation unless something needs updating):
+
+- **`~/.claude/CLAUDE.md`** — did the user reveal something about
+  themselves this session that isn't in their profile? A new role,
+  a new tool they use, a preference about how they work? If so,
+  propose adding it. Keep it brief — this isn't an interview.
+- **`~/.claude/cor-registry.json`** — does this project's name or
+  description still match reality? If the project has evolved
+  significantly, propose updating the registry entry.
+
 ### 5. Health Checks (core)
 
 Read `phases/health-checks.md` for end-of-session health checks. These
@@ -204,7 +215,38 @@ what was confusing, what needed a workaround.
 
 **This phase should not be skipped.** It's how CoR learns from use.
 
-### 9. Capture Loose Ends (core)
+### 9. Skill Discovery (core)
+
+Silently reflect: did this session involve a workflow the user is
+likely to repeat? Not every session produces one — most don't. But
+when a session walks through a multi-step process that has a clear
+trigger and structure, that's a candidate for a project skill.
+
+**Most sessions: nothing.** This check should be silent when there's
+nothing to surface. Don't force it.
+
+**When there's a candidate:** Describe the pattern and ask:
+
+> "We walked through [analyzing that deal / onboarding that client /
+> writing that report] step by step. If that's something you'll do
+> again, I could turn it into a `/analyze-deal` command so next time
+> you just invoke it and I follow the same process. Want me to?"
+
+If the user says yes, create the skill: a SKILL.md in
+`.claude/skills/[name]/` with the workflow captured as steps. Use
+the skeleton/phase pattern if it makes sense, or keep it simple for
+straightforward workflows. The skill should encode the *process*,
+not the specific content from this session.
+
+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, perspective, or convention? If so, mention
+`/extract` as an option for proposing it upstream to CoR. This is
+rarer than project-specific skills.
+
+### 10. Capture Loose Ends (core)
 
 Read `phases/loose-ends.md` for non-project items and environmental
 concerns to capture before closing. Sessions generate non-project
@@ -213,14 +255,14 @@ these aren't captured somewhere, they rely on human memory.
 
 **Skip (absent/empty).**
 
-### 10. Discover Custom Phases
+### 11. Discover Custom Phases
 
 After running the core phases above, check for any additional phase
 files in `phases/` that the skeleton doesn't define. These are project-
 specific extensions. Each custom phase file declares its position in
 the workflow. Execute them at their declared position.
 
-### 11. Present Report (presentation)
+### 12. Present Report (presentation)
 
 Read `phases/report.md` for how to present the debrief summary.
 
@@ -252,7 +294,7 @@ skip presentation phases. Core phases always run.
 
 - **Core phases** (always run): inventory, close-work, auto-maintenance,
   update-state, health-checks, record-lessons, upstream-feedback,
-  loose-ends, persist work
+  skill-discovery, loose-ends, persist work
 - **Presentation phases** (skippable): report
 
 A project that wants a quick debrief variant skips the report and

package/templates/skills/onboard/phases/detect-state.md

@@ -20,6 +20,19 @@ Also read `.corrc.json` if it exists — it records which modules the CLI
 installed and which were skipped (with reasons). The interview phase uses
 this to skip redundant questions.
 
+## User-Level State
+
+Before scanning the project, check the user-level layer:
+
+- **`~/.claude/CLAUDE.md`** — does a user profile exist? If yes, the
+  interview can skip identity questions. If it's sparse or stale (e.g.,
+  mentions a role the user seems to have moved past), flag it for the
+  interview phase to offer an update.
+- **`~/.claude/cor-registry.json`** — how many other projects does this
+  user have? The interview phase uses this to ask about relationships
+  between projects. If the registry doesn't exist, skip — the user may
+  have installed via npm instead of the shell installer.
+
 ## Full Scan (re-runs only)
 
 Only when `_context.md` exists, scan these artifacts to distinguish

package/templates/skills/onboard/phases/generate-context.md

@@ -69,6 +69,21 @@ Common re-run updates:
 - Updating work tracking configuration after switching tools
 - Removing stale information that no longer applies
 
+## Update Project Registry
+
+After generating the context layer, update `~/.claude/cor-registry.json`
+with what you learned from the interview. The installer registers the
+project with just its folder name and an empty description — onboard
+is where the real name and description get filled in.
+
+Find this project's entry by path and update:
+- **`name`** — the project's actual name (from the interview, not the
+  folder name, unless they match)
+- **`description`** — one line about what the project does
+
+This is a silent update — don't ask the user to confirm registry changes
+separately. The information already came from the interview.
+
 ## Quality Standards
 
 - **Populated, not padded.** Every section should contain real project

package/templates/skills/onboard/phases/interview.md

@@ -23,12 +23,15 @@ If **first time**, give a brief walkthrough before the interview:
 > Claude on Rails gives your Claude Code sessions a **session loop** —
 > a start and end routine that creates continuity between sessions.
 >
-> - **`/orient`** runs at the start. It reads where things stand — what
->   you were working on, what's due, what broke. Instead of starting
->   blind, Claude starts informed.
-> - **`/debrief`** runs at the end. It records what happened — what got
->   done, what's still open, what you learned. That's what orient reads
->   next time.
+> - **`/orient`** — you type this at the start of a session. It reads
+>   where things stand — what you were working on, what's due, what
+>   broke. Instead of starting blind, Claude starts informed.
+> - **`/debrief`** — you type this at the end of a session. It records
+>   what happened — what got done, what's still open, what you learned.
+>   That's what orient reads next time.
+>
+> Neither runs automatically — you invoke them when you're ready. If
+> you forget `/debrief`, Claude will nudge you before the session ends.
 >
 > Beyond the session loop, there are optional modules: **work tracking**
 > (a local task database), **planning** (structured plans with critique
@@ -44,6 +47,29 @@ questions about the system, answer them before moving on.
 If **experienced** (they've used it before, or say "I know how it works"),
 skip the walkthrough entirely and go straight to the interview.
 
+## User Context (Read Before Interviewing)
+
+Before asking any questions, read two global files if they exist:
+
+1. **`~/.claude/CLAUDE.md`** — the user's identity and preferences.
+   If this has an "About Me" section, you already know who they are
+   and what they do. Don't re-ask questions this answers. Acknowledge
+   it: "I see you run a real estate fund — let's talk about how this
+   project fits into that."
+
+2. **`~/.claude/cor-registry.json`** — a list of all their CoR projects.
+   If they have other projects registered, explain what that means and
+   ask how this project relates: "I see you're also using Claude on
+   Rails in [project X] — that's a separate project you've set up with
+   the same session loop. Does this project connect to that one in any
+   way? For example, does one feed data to the other, or do they share
+   code?" The answer goes into `_context.md` so orient and debrief can
+   flag when work in one project might affect the other.
+
+If neither file exists, that's fine — the installer may not have created
+them (npm install path, or the user skipped the identity questions).
+Proceed normally.
+
 ## Communication Calibration
 
 Don't ask the user how technical they are. Listen to how they talk.

package/templates/skills/orient/SKILL.md

@@ -123,6 +123,13 @@ references, failed background processes, configuration drift.
 **Skip (absent/empty).** Projects add health checks as they discover
 failure modes worth detecting early.
 
+**Built-in check (always runs):** If `~/.claude/cor-registry.json`
+exists, verify this project is in it and the entry is current. If
+other registry entries point to paths that no longer exist, silently
+note it — mention during briefing only if the user might care (e.g.,
+"Your old project 'deal-v1' seems to have been deleted — want me to
+remove it from the registry?").
+
 > **Orient vs Pulse vs Audit:** Orient health checks verify *operational*
 > state — is the system running, is data fresh, are processes alive?
 > Pulse (embedded in orient) verifies *descriptive* accuracy — do counts

package/templates/skills/orient/phases/context.md

@@ -30,6 +30,15 @@ are behavioral rules. Patterns with `enforcement: prevent` or `detect`
 should already be encoded as hooks or rules, but reading them provides
 context for why those guardrails exist.
 
+### Sibling Projects
+```
+Read ~/.claude/cor-registry.json if it exists.
+```
+If the user has other CoR projects, note them. Don't deep-read them,
+but know they exist — if work in this session touches something that
+relates to another project, mention it. "This API change might affect
+your investor-reports project too."
+
 ## Additional Context Sources
 
 Uncomment and adapt these for your project: