@lifeaitools/rdc-skills 0.9.37 → 0.9.38

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rdc",
-  "version": "0.9.37",
+  "version": "0.9.38",
   "description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight unattended builds with work-item tracking and TDD enforcement.",
   "author": {
     "name": "LIFEAI",

package/CHANGELOG.md

@@ -7,6 +7,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## v0.9.38 — Clean-box npm install hardening
+
+### Fixed
+
+- **Fresh Claude home install.** The installer now creates `CLAUDE_HOME` and `settings.json` when they do not exist, so a first-time machine is not blocked before Claude has written config files.
+- **Public package portability.** Removed the most brittle user-machine paths from public skill docs and hooks, replacing them with `{PROJECT_ROOT}`, `{RDC_SKILLS_ROOT}`, or environment-derived paths.
+- **Hook path fallback.** Commit hygiene hooks now use the current OS home directory instead of a user-specific fallback path.
+
+### Added
+
+- **npm binaries.** `rdc-skills-install` and `rdc-skills-self-test` are exposed from the npm package for simpler clean-box installs.
+
+---
+
 ## v0.9.37 — RDC hook loop guard and behavior tests
 
 ### Fixed

package/commands/deploy.md

@@ -55,7 +55,7 @@ rdc:deploy: <slug> → <domain>
 ```
 rdc:deploy new: <slug>
 [ ] Registry entry loaded (or interactive create)
-[ ] DNS path chosen (A: *.dev.place.fund  B: apex  C: other zone)
+[ ] DNS path chosen (A: staging wildcard  B: apex  C: other zone)
 [ ] DNS record verified or wildcard confirmed
 [ ] Cloudflare proxy setting correct for DNS path
 [ ] server_uuid, project_uuid, environment_uuid, github_app_uuid resolved
@@ -103,7 +103,7 @@ rdc:deploy audit: fleet scan
 [ ] Env var drift (registry.env_vars_needed vs Coolify env)
 [ ] Branch mismatches (Coolify git_branch ≠ expected)
 [ ] Disk space on 64.237.54.189
-[ ] CF proxy misconfigs on *.dev.place.fund
+[ ] DNS/proxy misconfigs on configured staging wildcard
 [ ] Duplicate apps (same repo, multiple UUIDs)
 
 Findings:
@@ -127,7 +127,7 @@ There is no Coolify MCP server — do not reference `@masonator/coolify-mcp`.
 
 ```bash
 _COOLIFY=$(curl -s http://127.0.0.1:52437/v/coolify-api)
-curl -s -H "Authorization: Bearer $_COOLIFY" https://deploy.regendevcorp.com/api/v1/applications
+curl -s -H "Authorization: Bearer $_COOLIFY" "$DEPLOY_API_BASE/api/v1/applications"
 ```
 
 If clauth daemon is not responding:
@@ -143,7 +143,7 @@ BLOCKED: clauth daemon not responding. Run scripts\restart-clauth.bat, unlock at
   ```
   Server UUID:     ih386anenvvvn6fy1umtyow0
   Server IP:       64.237.54.189
-  Dashboard:       https://deploy.regendevcorp.com
+  Dashboard:       <deployment-dashboard-url>
   GitHub App UUID: xdmcy60putp5h9j7k4kwg9c3
   ```
 

package/commands/design.md

@@ -15,7 +15,7 @@ Use `skills/design/SKILL.md` as the source of truth.
 
 - Studio, Palette Library, brand-token, theme, component, or live-editor work
 - Any design task that must understand RDC's real token tables and Studio routes
-- UI critique, audit, polish, colorize, type, layout, or craft work in `regen-root`
+- UI critique, audit, polish, colorize, type, layout, or craft work in `{PROJECT_ROOT}`
 - Agent-side color-system exploration using Rampa CLI
 
 ## Arguments

package/commands/overnight.md

@@ -30,13 +30,13 @@ description: >-
 **First action — set the overnight sentinel** so the `no-stop-open-epics` Stop hook engages (interactive sessions are not gated by it):
 
 ```bash
-mkdir -p C:/Dev/regen-root/.rdc && touch C:/Dev/regen-root/.rdc/overnight.lock
+mkdir -p {PROJECT_ROOT}/.rdc && touch {PROJECT_ROOT}/.rdc/overnight.lock
 ```
 
 **Last action at end of run (success OR failure) — remove the sentinel:**
 
 ```bash
-rm -f C:/Dev/regen-root/.rdc/overnight.lock
+rm -f {PROJECT_ROOT}/.rdc/overnight.lock
 ```
 
 If the sentinel file does not exist, the Stop hook will NOT block — which means interactive sessions stop freely and only `rdc:overnight` is held to the "drain the queue" contract.

package/commands/release.md

@@ -1,159 +1,49 @@
 ---
-name: rdc:release
 description: >-
-  Atomic release. Usage `rdc:release <repo> [version]` or `rdc:release <repo> --patch|--minor|--major` or `rdc:release <repo> --dry-run` — bump, commit, tag, push, wait CI, install, verify, restart. Known repos: clauth, rdc-skills, regen-media, gws. No user handoff.
+  Atomic release. Usage `rdc:release <repo> [version]` or `rdc:release <repo> --patch|--minor|--major|--dry-run` — bump, commit, tag, push, wait CI/publish, install, and verify. Uses repo-local release metadata.
 ---
 
+# rdc:release — Generic Release
+
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
-> Checklist-only output. No tool-call narration. No raw git/npm/CI dumps.
+> Checklist-only output. No raw git/npm/CI dumps.
 > One checklist upfront, updated in place, shown again at end with 1-line verdict.
 
-> **Sandbox contract:** This skill honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Destructive external calls (git tag push, CI poll, npm publish verification, global install, daemon restart) short-circuit under the flag — the checklist still runs, but each destructive step echoes `[RDC_TEST] skipping <step>` instead of mutating external state.
-
-# rdc:release — Atomic LIFEAI Package Release
-
-## Purpose
-
-Dave has Bash access. Therefore Dave should never be asked to run install
-commands. This skill handles the complete release loop for any LIFEAI-published
-package so the user sees one checklist and one verdict, not a series of "now run
-this" handoffs.
-
-## Arguments
-
-- `rdc:release <repo>` — patch bump (default), full loop
-- `rdc:release <repo> <version>` — explicit version (e.g. `1.6.0`)
-- `rdc:release <repo> --minor` | `--major` | `--patch` — semver bump
-- `rdc:release <repo> --dry-run` — show checklist and planned version, do nothing
-- `rdc:release` (no args) — list known repos, ask which
-
-## Known repos
-
-Resolve `<repo>` to source path + install mechanism:
-
-| Repo | Source path | Publish | Install | Post-install |
-|------|-------------|---------|---------|--------------|
-| `clauth` | `C:/Dev/clauth` | npm via tag → GitHub Actions | `npm install -g @lifeaitools/clauth@latest` | `curl -s -X POST http://127.0.0.1:52437/restart` |
-| `rdc-skills` | `C:/Dev/rdc-skills` | local (no npm) | `bash C:/Dev/rdc-skills/scripts/install.sh` + cp fallback | none |
-| `regen-media` | `C:/Dev/regen-root/mcp-servers/regen-media` | local | restart MCP server | none |
-| `gws` | `C:/Dev/regen-root/mcp-servers/gws` | local | restart MCP server | none |
-
-Add new repos to this table as they emerge. If user specifies an unknown repo,
-ask for the source path and install command.
-
-## Checklist (run every mode)
+## Checklist
 
 ```
-rdc:release: <repo> vX.Y.Z → vA.B.C
+rdc:release: <repo> vX.Y.Z -> vA.B.C
 [ ] Source path resolved
-[ ] Working tree clean (git status)
-[ ] Current version detected (package.json)
+[ ] Release metadata read
+[ ] Working tree clean or user-approved dirty scope identified
+[ ] Current version detected
 [ ] New version computed
-[ ] Dry-run gate (if --dry-run, stop here)
-[ ] package.json bumped (all version fields)
+[ ] Dry-run gate handled
+[ ] Version files updated
+[ ] Tests/self-test passed
 [ ] Commit created
-[ ] Tag vA.B.C created
-[ ] Push to origin
-[ ] Push --tags to origin
-[ ] CI run located (gh run list, if applicable)
-[ ] CI completed successfully (poll every 20s, 10min timeout)
-[ ] npm registry shows vA.B.C (if npm package, poll every 15s, 3min timeout)
-[ ] Local install executed
-[ ] Installed version verified matches vA.B.C
-[ ] Post-install action (daemon restart, etc., if applicable)
-[ ] Smoke test (ping health endpoint or binary --version)
-✅ rdc:release <repo>: vA.B.C live and installed
+[ ] Tag created
+[ ] Branch and tag pushed
+[ ] CI/publish status verified
+[ ] Registry/package/deploy target shows vA.B.C, if applicable
+[ ] Local install/update executed, if applicable
+[ ] Installed/runtime version verified
+[ ] Smoke test passed
+✅ rdc:release <repo>: vA.B.C live and verified
 ```
 
-## Execution details (silent to user — don't narrate)
+## Rules
 
-### 1. Version bump
-- Read `package.json`, parse version
-- Apply bump: patch (default), minor, major, or explicit
-- Rewrite all `version` fields (some packages have version in `claude.version` too)
+- Do not release without explicit user authorization.
+- Prefer repo-local release instructions in `.rdc/release.json`, README, package scripts, or CI workflows.
+- Never force push or bypass hooks.
+- Never declare success without verifying the installed or deployed version.
 
-### 2. Commit + tag + push
-```bash
-cd <source_path>
-git add package.json
-git commit -m "chore(release): vA.B.C"
-if [ "$RDC_TEST" != "1" ]; then
-  git tag vA.B.C
-  git push && git push --tags
-else
-  echo "[RDC_TEST] skipping git tag + git push --tags"
-fi
-```
-Never `--no-verify`. Never `--force`. If pre-commit hook fails, fix root cause, don't skip.
+## RDC Skills Package
 
-*Under `$RDC_TEST=1`, sections 3 (CI poll), 4 (npm registry poll), 5 (install), 6 (verify install), 7 (post-install), and 8 (smoke test) are also skipped — echo `[RDC_TEST] skipping <section>` for each and mark the checklist line as `[~]`.*
+After publishing this package to npm, a clean-box install should use:
 
-### 3. CI poll (for repos with GH Actions publish)
 ```bash
-# Locate the run triggered by the tag push
-gh run list --repo LIFEAI/<repo> --limit 5 --json status,conclusion,headBranch,databaseId
-# Poll its status field every 20s until conclusion ∈ {success, failure, cancelled}
-# Max 10 minutes — if timeout, fail with [!] and report run URL
+npm install -g @lifeaitools/rdc-skills@latest
+rdc-skills-install --profile core
 ```
-
-### 4. npm registry poll (only if published to npm)
-```bash
-npm view @lifeaitools/<repo> version
-# Poll every 15s until matches new version
-# Max 3 minutes — usually lands within 30-60s after CI success
-```
-
-### 5. Install
-- **clauth:** `npm install -g @lifeaitools/clauth@latest`
-- **rdc-skills:** `bash C:/Dev/rdc-skills/scripts/install.sh` — if output shows only one file copied (known bug), fall back to `cp C:/Dev/rdc-skills/skills/*.md ~/.claude/skills/user/ && cp C:/Dev/rdc-skills/skills/*.md C:/Dev/regen-root/.claude/skills/user/`
-- **MCP servers:** restart the server process (find its PID, kill, respawn — or document how)
-
-### 6. Verify install
-- **clauth:** `curl -s http://127.0.0.1:52437/ping | jq -r .app_version` — must equal new version
-- **rdc-skills:** `ls ~/.claude/skills/user/rdc-release.md` (or whichever file is new in this release) — must exist
-- **Global npm:** `npm list -g --depth=0 @lifeaitools/<repo>` — version matches
-
-### 7. Post-install
-- **clauth:** `curl -s -X POST http://127.0.0.1:52437/restart` — wait 3s — ping again
-- Others: N/A
-
-### 8. Smoke test
-- **clauth:** new tool roundtrip (e.g., `curl -s http://127.0.0.1:52437/get/openai | head -c 10` succeeds without error)
-- **rdc-skills:** load one new skill file and check frontmatter parses
-- **MCP:** server responds to `tools/list`
-
-## Failure modes → checklist outcome
-
-| Failure | Marker | Next |
-|---------|--------|------|
-| Dirty working tree | `[!]` line 2 | Abort with one-sentence diff summary; ask user to commit or stash |
-| Pre-commit hook fails | `[!]` line 7 | Fix root cause, re-stage, retry (NEVER --no-verify) |
-| CI fails | `[!]` line 11 | Print run URL, tail 20 lines of failing job, ask user |
-| npm doesn't register | `[!]` line 12 | Print npm error, check if CI actually published (not a silent skip) |
-| Install script broken | `[!]` line 13 | Fall back to manual cp; note the installer bug as a task |
-| Version mismatch after install | `[!]` line 14 | Uninstall + clean install; if still wrong, likely cache issue |
-| Post-install restart fails | `[!]` line 15 | Print ping error; instruct user to run `scripts\restart-clauth.bat` manually |
-
-Even on failure, show the full checklist with `[!]` markers so user sees exactly
-where it stopped.
-
-## Dry-run mode
-
-Prints the checklist + resolved version bump + every command that WOULD run, but
-executes nothing beyond reads. Use when user says "what would you do" or before
-risky major bumps.
-
-## Never
-
-- Never release on behalf of the user without an explicit `rdc:release` invocation
-- Never skip CI verification ("it'll probably work" is how stale installs happen)
-- Never `--force` push, never `--no-verify`, never `--no-gpg-sign`
-- Never touch `main` — release tags go on the default branch the repo uses (`master` for clauth, rdc-skills)
-- Never declare success without verifying the installed version matches
-
-## Related
-
-- `.claude/rules/clauth.md` — clauth release workflow source of truth
-- `feedback_version_bump_must_tag.md` (memory) — never bump without tagging
-- `feedback_clauth_ci.md` (memory) — CI publish pattern
-- `feedback_just_do_it.md` (memory) — don't hand commands to Dave; run them

package/commands/self-test.md

@@ -29,7 +29,7 @@ description: >-
 
 1. **Run the linter:**
    ```bash
-   node C:/Dev/rdc-skills/scripts/self-test.mjs
+   node {RDC_SKILLS_ROOT}/scripts/self-test.mjs
    ```
 
 2. **Interpret exit codes:**

package/commands/watch.md

@@ -24,7 +24,7 @@ description: >-
    ```bash
    node ${CLAUDE_PLUGIN_ROOT}/scripts/watch-init.mjs
    ```
-   (If `CLAUDE_PLUGIN_ROOT` is not set, resolve the plugin path from your invocation context. On Windows it's typically `C:/Dev/rdc-skills`.)
+   (If `CLAUDE_PLUGIN_ROOT` is not set, resolve the plugin path from your invocation context or the installed plugin cache.)
 
 2. **Parse the output.** The script prints `run_id`, `log_path`, `current`, `viewer`, and `open_hint`. Capture `log_path` and `viewer` for the rest of the session.
 

package/guides/agent-bootstrap.md

@@ -137,7 +137,7 @@ When `RDC_TEST=1` is set, the skill is running inside the Tier 2 sandbox harness
 **Bash pattern:**
 ```bash
 if [ "$RDC_TEST" != "1" ]; then
-  curl -X POST "https://deploy.regendevcorp.com/api/v1/applications/$UUID/deploy" ...
+  curl -X POST "$DEPLOY_API_BASE/api/v1/applications/$UUID/deploy" ...
 else
   echo "[RDC_TEST] skipping Coolify deploy"
 fi
@@ -156,7 +156,7 @@ if (process.env.RDC_TEST !== '1') {
 
 **New-skill contract:** every new `rdc:*` skill MUST honor `RDC_TEST` before shipping. Tier 2 manifests will fail any skill that writes to external state under the flag.
 
-**Known blocker:** The `check-cwd.js` SessionStart hook hard-blocks Claude sessions launched from `C:/Dev/rdc-skills`. The hook must check `process.env.RDC_TEST === '1'` and call `process.exit(0)` early to allow Tier 2 sandbox runs. Without this bypass, all Tier 2 headless invocations fail with `exit_code: -1`. File: `~/.claude/hooks/check-cwd.js`.
+**Known blocker:** Project-specific cwd hooks must check `process.env.RDC_TEST === '1'` and call `process.exit(0)` early to allow Tier 2 sandbox runs. Without this bypass, headless self-test invocations can fail before the skill loads. File: `~/.claude/hooks/check-cwd.js`.
 
 ---
 

package/hooks/check-cwd.js

@@ -1,18 +1,18 @@
 #!/usr/bin/env node
-// Hard blocks session if CWD is not the regen-root project directory.
+// Hard blocks session if CWD is not the expected project directory.
 // Exits with code 1 to fail the hook + outputs a blocking systemMessage.
 
 const { execSync } = require('child_process');
 const hookLog = require('./hook-logger');
 const cwd     = process.cwd().replace(/\\/g, '/');
 
-let expected = 'regen-root';
+let expected = process.env.RDC_PROJECT_SCOPE || 'regen-root';
 try {
   expected = execSync('git rev-parse --show-toplevel', { encoding: 'utf8', stdio: 'pipe' })
     .trim().replace(/\\/g, '/');
 } catch (_) {}
 
-if (!cwd.endsWith('regen-root')) {
+if (!cwd.endsWith(expected)) {
   hookLog('check-cwd', 'SessionStart', 'block', { cwd, expected });
   process.stdout.write(JSON.stringify({
     systemMessage:

package/hooks/no-stop-open-epics.js

@@ -5,7 +5,7 @@
  * Fires on every Stop event where Claude decided to end_turn.
  * Queries get_open_epics() via Supabase REST.
  * Only blocks if epics with status=todo exist — in_progress means another session owns them.
- * Only fires in the regen-root project (scope guard on event.cwd).
+ * Only fires in the configured project scope (scope guard on event.cwd).
  *
  * Exit codes:
  *   0 = allow stop
@@ -15,8 +15,9 @@
  *   NEXT_PUBLIC_SUPABASE_URL=https://<ref>.supabase.co
  *   NEXT_PUBLIC_SUPABASE_ANON_KEY=<key>
  *
- * PROJECT SCOPE in package.json or plugin config:
- *   "hookScope": "regen-root"   ← folder name that must appear in event.cwd
+ * PROJECT SCOPE:
+ *   RDC_PROJECT_SCOPE=<folder-name>   folder name that must appear in event.cwd
+ *   RDC_PROJECT_ROOT=<path>           root used to find .rdc/overnight.lock and .env.local
  */
 
 const fs = require('fs');
@@ -24,11 +25,12 @@ const path = require('path');
 
 // ── Config — override these per project ──────────────────────────────────────
 
-const PROJECT_SCOPE = 'regen-root'; // only block in sessions inside this folder name
-const OVERNIGHT_SENTINEL = 'C:/Dev/regen-root/.rdc/overnight.lock'; // only fire when this exists
+const PROJECT_SCOPE = process.env.RDC_PROJECT_SCOPE || 'regen-root'; // LIFEAI default; override per project
+const PROJECT_ROOT = process.env.RDC_PROJECT_ROOT || process.cwd();
+const OVERNIGHT_SENTINEL = process.env.RDC_OVERNIGHT_LOCK || path.join(PROJECT_ROOT, '.rdc', 'overnight.lock');
 const ENV_PATHS = [
-  'C:/Dev/regen-root/apps/rdc-marketing-engine/.env.local',
-  'C:/Dev/regen-root/.env.local',
+  ...(process.env.RDC_ENV_PATHS ? process.env.RDC_ENV_PATHS.split(path.delimiter) : []),
+  path.join(PROJECT_ROOT, '.env.local'),
 ];
 const SUPABASE_URL = process.env.SUPABASE_URL || readEnvVar('NEXT_PUBLIC_SUPABASE_URL');
 

package/hooks/require-work-item-on-commit.js

@@ -18,10 +18,11 @@
 
 const fs      = require('fs');
 const path    = require('path');
+const os      = require('os');
 const hookLog = require('./hook-logger');
 
 const MARKER_FILE = path.join(
-  process.env.USERPROFILE || process.env.HOME || 'C:/Users/DaveLadouceur',
+  process.env.USERPROFILE || process.env.HOME || os.homedir(),
   '.claude',
   'fixit.marker'
 );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.9.37",
+  "version": "0.9.38",
   "description": "RDC typed-agent dispatch skill suite for Claude Code - plan, build, review, overnight builds",
   "keywords": [
     "claude-code",
@@ -19,9 +19,13 @@
     "type": "plugin",
     "skills": "skills/",
     "guides": "guides/",
-    "version": "0.9.37",
+    "version": "0.9.38",
     "commands": "commands/"
   },
+  "bin": {
+    "rdc-skills-install": "scripts/install-rdc-skills.js",
+    "rdc-skills-self-test": "scripts/self-test.mjs"
+  },
   "scripts": {
     "install-rdc-skills": "node scripts/install-rdc-skills.js",
     "uninstall:win": "powershell -ExecutionPolicy Bypass -File scripts/uninstall.ps1",

package/scripts/install-rdc-skills.js

@@ -766,8 +766,12 @@ async function main() {
   console.log('');
 
   if (!fs.existsSync(claudeHome)) {
-    fail(`CLAUDE_HOME not found: ${claudeHome}`);
-    process.exit(1);
+    fs.mkdirSync(claudeHome, { recursive: true });
+    warn(`CLAUDE_HOME did not exist — created ${claudeHome}`);
+  }
+  if (!fs.existsSync(settingsPath)) {
+    writeJson(settingsPath, {});
+    info(`       created settings.json`);
   }
 
   // Read version + git SHA once

package/skills/build/SKILL.md

@@ -301,8 +301,8 @@ Read the task title and description, then:
     ⚠️ The validator does NOT use `isolation: "worktree"` — it must read the fully merged develop branch. Omit the isolation parameter for this dispatch only.
 
     ```
-    "Read C:/Dev/regen-root/.rdc/guides/agent-bootstrap.md then C:/Dev/regen-root/.rdc/guides/verify.md.
-     Read C:/Dev/regen-root/.rdc/guides/engineering-behavior.md before validating scope, deviations, and evidence.
+    "Read {PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md then {PROJECT_ROOT}/.rdc/guides/verify.md.
+     Read {PROJECT_ROOT}/.rdc/guides/engineering-behavior.md before validating scope, deviations, and evidence.
      Validate these work items: [list of IDs and titles].
      Apps touched: [list].
      Git diff since build start: [attach or reference].

package/skills/co-develop/SKILL.md

@@ -110,7 +110,7 @@ the source of truth.
   "skill": "rdc:review",
   "task": "Audit the current diff for regressions before merge.",
   "context": {
-    "repo": "C:\\Dev\\regen-root",
+    "repo": "{PROJECT_ROOT}",
     "work_item_id": "<optional-uuid>",
     "branch": "develop",
     "owned_files": []

package/skills/deploy/SKILL.md

@@ -66,10 +66,10 @@ Template selection:
 
 ```
 rdc:deploy new: <slug>
-[ ] .dockerignore present at regen-root root (ls C:/Dev/regen-root/.dockerignore — STOP if missing)
+[ ] .dockerignore present at project root (`ls {PROJECT_ROOT}/.dockerignore` — STOP if missing)
 [ ] Template loaded from docs/runbooks/coolify-app-templates.json (pick nextjs-app / static-site / mcp-server)
 [ ] Required vars substituted: NAME, APP_PATH, DOMAIN, BRANCH, PROJECT_UUID, ENVIRONMENT_UUID [+ TURBO_FILTER / PORT]
-[ ] DNS path chosen (A: *.dev.place.fund  B: apex  C: other zone)
+[ ] DNS path chosen (A: staging wildcard  B: apex  C: other zone)
 [ ] DNS record verified or wildcard confirmed
 [ ] Cloudflare proxy setting correct for DNS path
 [ ] Application created via POST /applications/private-github-app (template payload)
@@ -117,7 +117,7 @@ rdc:deploy audit: fleet scan
 [ ] Env var drift (registry.env_vars_needed vs Coolify env)
 [ ] Branch mismatches (Coolify git_branch ≠ expected)
 [ ] Disk space on 64.237.54.189
-[ ] CF proxy misconfigs on *.dev.place.fund
+[ ] DNS/proxy misconfigs on configured staging wildcard
 [ ] Duplicate apps (same repo, multiple UUIDs)
 
 Findings:
@@ -145,39 +145,39 @@ _COOLIFY=$(curl -s http://127.0.0.1:52437/v/coolify-api)
 
 # List applications
 curl -s -H "Authorization: Bearer $_COOLIFY" \
-  https://deploy.regendevcorp.com/api/v1/applications
+  "$DEPLOY_API_BASE/api/v1/applications"
 
 # Get application details
 curl -s -H "Authorization: Bearer $_COOLIFY" \
-  https://deploy.regendevcorp.com/api/v1/applications/<uuid>
+  "$DEPLOY_API_BASE/api/v1/applications/<uuid>"
 
 # Deploy (trigger)
 curl -s -X POST -H "Authorization: Bearer $_COOLIFY" \
-  https://deploy.regendevcorp.com/api/v1/applications/<uuid>/deploy
+  "$DEPLOY_API_BASE/api/v1/applications/<uuid>/deploy"
 
 # Get deployment logs
 curl -s -H "Authorization: Bearer $_COOLIFY" \
-  https://deploy.regendevcorp.com/api/v1/deployments/<deployment-id>
+  "$DEPLOY_API_BASE/api/v1/deployments/<deployment-id>"
 
 # Set env var
 curl -s -X POST -H "Authorization: Bearer $_COOLIFY" \
   -H "Content-Type: application/json" \
   -d '{"key":"<KEY>","value":"<VALUE>"}' \
-  https://deploy.regendevcorp.com/api/v1/applications/<uuid>/envs
+  "$DEPLOY_API_BASE/api/v1/applications/<uuid>/envs"
 
 # Set watch_paths
 curl -s -X PATCH -H "Authorization: Bearer $_COOLIFY" \
   -H "Content-Type: application/json" \
   -d '{"watch_paths":"apps/<name>/**\npackages/**"}' \
-  https://deploy.regendevcorp.com/api/v1/applications/<uuid>
+  "$DEPLOY_API_BASE/api/v1/applications/<uuid>"
 ```
 
 **Never print `$_COOLIFY` to stdout.** Inline from clauth only — do not assign raw strings.
 
 If clauth daemon is not responding (`curl -s http://127.0.0.1:52437/ping` fails):
 ```
-BLOCKED: clauth daemon is not responding.
-Fix: Run C:\Dev\regen-root\scripts\restart-clauth.bat, then unlock at http://127.0.0.1:52437
+BLOCKED: credential provider is not responding.
+Fix: start the project's credential provider or configure deployment credentials through env vars, then retry.
 I cannot proceed until this is resolved.
 ```
 
@@ -189,7 +189,7 @@ I cannot proceed until this is resolved.
   ```
   Server UUID:     ih386anenvvvn6fy1umtyow0
   Server IP:       64.237.54.189
-  Dashboard:       https://deploy.regendevcorp.com
+  Dashboard:       <deployment-dashboard-url>
   GitHub App UUID: xdmcy60putp5h9j7k4kwg9c3
   ```
 

package/skills/design/SKILL.md

@@ -19,7 +19,7 @@ RDC-owned design execution for Studio and LIFEAI interfaces. This skill is the S
 
 - Studio, Palette Library, brand-token, theme, component, or live-editor work
 - Any design task that must understand RDC's real token tables and Studio routes
-- UI critique, audit, polish, colorize, type, layout, or craft work in `regen-root`
+- UI critique, audit, polish, colorize, type, layout, or craft work in `{PROJECT_ROOT}`
 - Agent-side color-system exploration using Rampa CLI
 - Preparing token-aware implementation instructions for frontend/backend/data agents
 
@@ -166,7 +166,7 @@ Project docs to read for Studio work:
 8. **Verify.**
    - Run scoped tests only.
    - For Studio: prefer route smoke checks, token API checks, and browser screenshots when UI changed.
-   - For CLI prompt work: run `node C:/Dev/rdc-skills/scripts/rdc-design-cli.mjs <command> <brief>` and inspect the generated report under `.rdc/reports/rdc-design-cli/`.
+   - For CLI prompt work: run `node {RDC_SKILLS_ROOT}/scripts/rdc-design-cli.mjs <command> <brief>` and inspect the generated report under `.rdc/reports/rdc-design-cli/`.
 
 ## Command Menu
 
@@ -188,15 +188,15 @@ Project docs to read for Studio work:
 Use the local helper to see exactly how much instruction text the skill is generating before sending it through an agent:
 
 ```powershell
-node C:/Dev/rdc-skills/scripts/rdc-design-cli.mjs studio "audit the Studio palette page"
-node C:/Dev/rdc-skills/scripts/rdc-design-cli.mjs palette "generate a PRT palette workflow"
-node C:/Dev/rdc-skills/scripts/rdc-design-cli.mjs --json theme "RDC earth-forward light theme"
+node {RDC_SKILLS_ROOT}/scripts/rdc-design-cli.mjs studio "audit the Studio palette page"
+node {RDC_SKILLS_ROOT}/scripts/rdc-design-cli.mjs palette "generate a PRT palette workflow"
+node {RDC_SKILLS_ROOT}/scripts/rdc-design-cli.mjs --json theme "RDC earth-forward light theme"
 ```
 
 The helper writes logs to:
 
 ```text
-C:/Dev/rdc-skills/.rdc/reports/rdc-design-cli/
+{RDC_SKILLS_ROOT}/.rdc/reports/rdc-design-cli/
 ```
 
 Each run includes character count, word count, approximate token count, references loaded, and the final prompt text.

package/skills/fs-mcp/SKILL.md

@@ -11,7 +11,7 @@ description: "Usage `rdc:fs-mcp <task>` — Use the File System MCP bridge for l
 # rdc:fs-mcp — File System MCP Bridge
 
 ## When to Use
-- Claude.ai, Cowork, or another remote surface needs live access to `C:/Dev/regen-root` through the File System MCP.
+- Claude.ai, Cowork, or another remote surface needs live access to `{PROJECT_ROOT}` through the File System MCP.
 - You need to read, search, or list current local repo files without relying on GitHub freshness.
 - You need to write a small/scratch file through FS MCP.
 - You need to move a larger cloud file into the local repo.
@@ -88,7 +88,7 @@ Required Claude.ai handoff shape:
 
 ```json
 {
-  "repo": "LIFEAI/regen-root",
+  "repo": "<owner>/<repo>",
   "remote": "origin",
   "ref": "claude-ai/docs-upload-123",
   "paths": ["docs/plans/foo.md"],

package/skills/plan/SKILL.md

@@ -227,7 +227,7 @@ Q1. Which Coolify project does this app belong to?
     → Record: project_uuid + environment_uuid (staging or production)
 
 Q2. What is the domain?
-    → *.dev.place.fund subdomain? (staging / internal tools)
+    → staging wildcard subdomain? (staging / internal tools)
     → Custom subdomain on an existing zone? (e.g. app.regendevcorp.com)
     → Apex domain? (e.g. place.fund itself)
     → Domain on a different zone entirely? (e.g. skymesasouth.com)
@@ -238,7 +238,7 @@ Q3. Is this domain already in our Cloudflare account?
     → If NS not delegated to Cloudflare: A record in Cloudflare does nothing — must go to registrar
 
 Q4. Does this app need Cloudflare proxy (orange cloud)?
-    → *.dev.place.fund: NEVER proxy — breaks Traefik Let's Encrypt HTTP-01 cert provisioning
+    → Traefik/Let's Encrypt HTTP-01 staging wildcards are often safest unproxied; verify your platform's DNS requirements.
     → Custom domain needing DDoS/CDN: proxy OK only if SSL mode = Full (strict) + origin cert provisioned
     → Any doubt: start unproxied, add proxy after confirming SSL works