@lifeaitools/rdc-skills 0.9.23 → 0.9.25

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rdc",
-  "version": "0.9.23",
+  "version": "0.9.25",
   "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/README.md

@@ -176,7 +176,7 @@ python3 -c "import json; print(json.load(open('package.json'))['version'])"
 /rdc:help
 ```
 
-Current version: **v0.9.23**
+Current version: **v0.9.25**
 
 ## Quick Start
 

package/commands/design.md

@@ -1,7 +1,7 @@
 ---
 name: rdc:design
 description: >-
-  Usage `rdc:design <command|brief>` — RDC-owned design skill for Studio, Palette Library, token-aware UI work, and Rampa CLI-assisted color systems. Forked/adapted from Impeccable concepts without modifying installed Impeccable.
+  Usage `rdc:design <command|brief>` — RDC-owned design skill for Studio, Palette Library, token-aware UI work, and Rampa CLI-assisted color systems.
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.9.23",
+  "version": "0.9.25",
   "description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight builds",
   "keywords": [
     "claude-code",
@@ -19,7 +19,7 @@
     "type": "plugin",
     "skills": "skills/",
     "guides": "guides/",
-    "version": "0.9.23",
+    "version": "0.9.25",
     "commands": "commands/"
   },
   "scripts": {

package/scripts/rdc-design-cli.mjs

@@ -15,16 +15,16 @@ const command = cleanArgs[0] || "help";
 const brief = cleanArgs.slice(1).join(" ").trim();
 
 const commandRefs = {
-  studio: ["studio-model", "lineage"],
-  tokens: ["studio-model", "lineage"],
-  palette: ["studio-model", "rampa", "lineage"],
-  theme: ["studio-model", "rampa", "lineage"],
-  colorize: ["rampa", "studio-model", "lineage"],
-  audit: ["studio-model", "lineage"],
-  critique: ["studio-model", "lineage"],
-  polish: ["studio-model", "lineage"],
-  craft: ["studio-model", "rampa", "lineage"],
-  help: ["lineage"],
+  studio: ["studio-model", "ownership"],
+  tokens: ["studio-model", "ownership"],
+  palette: ["studio-model", "rampa", "ownership"],
+  theme: ["studio-model", "rampa", "ownership"],
+  colorize: ["rampa", "studio-model", "ownership"],
+  audit: ["studio-model", "ownership"],
+  critique: ["studio-model", "ownership"],
+  polish: ["studio-model", "ownership"],
+  craft: ["studio-model", "rampa", "ownership"],
+  help: ["ownership"],
 };
 
 function readText(path) {
@@ -56,7 +56,7 @@ function buildPrompt() {
   const skillPath = join(skillRoot, "SKILL.md");
   if (!existsSync(skillPath)) throw new Error(`Missing skill file: ${skillPath}`);
 
-  const refs = loadReferences(commandRefs[command] || ["studio-model", "lineage"]);
+  const refs = loadReferences(commandRefs[command] || ["studio-model", "ownership"]);
   const skill = stripFrontmatter(readText(skillPath));
   const refText = refs.map((ref) => `## Reference: ${ref.name}\n\n${ref.text}`).join("\n\n");
   const target = brief || "(no brief supplied)";
@@ -77,7 +77,7 @@ function buildPrompt() {
     "",
     `Execute \`rdc:design ${command}\` for: ${target}`,
     "",
-    "Return checklist-first output, cite concrete Studio files/routes/tables when relevant, and do not mutate upstream Impeccable.",
+    "Return checklist-first output, cite concrete Studio files/routes/tables when relevant, and do not mutate unrelated installed skills or vendor artifacts.",
   ].join("\n");
 
   return { prompt, refs };

package/skills/design/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: rdc:design
 description: >-
-  Usage `rdc:design <command|brief>` — RDC-owned design skill for Studio, Palette Library, token-aware UI work, and Rampa CLI-assisted color systems. Forked/adapted from Impeccable concepts without modifying installed Impeccable.
+  Usage `rdc:design <command|brief>` — RDC-owned design skill for Studio, Palette Library, token-aware UI work, and Rampa CLI-assisted color systems.
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
@@ -14,7 +14,7 @@ description: >-
 
 # rdc:design — RDC Design Skill
 
-RDC-owned design execution for Studio and LIFEAI interfaces. This skill is inspired by and adapted from the Impeccable design workflow, but it is not the installed Impeccable skill and must not modify upstream Impeccable files.
+RDC-owned design execution for Studio and LIFEAI interfaces. This skill is the Studio-aware design authority for RDC token, palette, theme, component, and local-debug work.
 
 ## When to Use
 
@@ -24,11 +24,10 @@ RDC-owned design execution for Studio and LIFEAI interfaces. This skill is inspi
 - Agent-side color-system exploration using Rampa CLI
 - Preparing token-aware implementation instructions for frontend/backend/data agents
 
-Use the installed `impeccable` skill directly only when the task is a general upstream Impeccable workflow and does not need RDC Studio knowledge.
-
 ## Arguments
 
 - `rdc:design` — show the command menu
+- `rdc:design edit <target>` — start a local source-edit session for a URL, app, brand, route, or file
 - `rdc:design studio <target>` — Studio-aware design task
 - `rdc:design tokens <brand-or-route>` — token model, resolver, export, or governance task
 - `rdc:design palette <brief>` — Palette Library or palette generation task
@@ -47,7 +46,7 @@ Load only what applies, but do not skip the Studio model for Studio/token/palett
 |---|---|
 | Studio, tokens, palettes, themes, editor | `skills/design/reference/studio-model.md` |
 | Color generation, ramps, contrast, neutrals | `skills/design/reference/rampa.md` |
-| Attribution, fork boundary, Impeccable relationship | `skills/design/reference/lineage.md` |
+| Ownership, operating boundary, attribution files | `skills/design/reference/ownership.md` |
 
 Project docs to read for Studio work:
 
@@ -59,8 +58,10 @@ Project docs to read for Studio work:
 ## Procedure
 
 1. **Classify the task.**
+   - `edit` means start a local source-edit session. Do not show the generic command menu for `edit`.
    - `studio`, `tokens`, `palette`, and `theme` always load the Studio model.
    - `palette`, `theme`, and `colorize` also load the Rampa reference.
+   - Any task involving colors, palettes, ramps, contrast, neutrals, light/dark color pairs, status colors, chart colors, or theme colors loads the Rampa reference.
    - `audit`, `critique`, `polish`, and `craft` load Studio model when the target is inside Studio or uses Studio tokens.
 
 2. **Read the actual system context.**
@@ -74,24 +75,96 @@ Project docs to read for Studio work:
    - Live editor: RDC Native Local Debug only — `/editor/local/*`, `/api/editor/local-debug`, `/studio/debug/*`, `/studio/claude/*`, and `scripts/studio-debug-poll.mjs`.
    - Components: `@regen/ui`, Studio component registry, and existing local components.
 
-4. **Use Rampa only as proposal tooling.**
+4. **For `edit`, start the local session directly.**
+   - Intent syntax:
+     ```powershell
+     rdc:design edit <url|domain|brand|app|file>
+     ```
+   - Required variables:
+     - `target`
+     - `brandSlug`
+     - `appSlug`
+     - `repoRoot`
+     - `cwd`
+     - `connectorBaseUrl`
+     - `studioOrigin`
+     - `modeDefault`
+   - Fill missing variables from the obvious target mapping before asking:
+     - `test`, `studio_test`, `studio-test` -> `--brand test --app studio_test`
+     - `prt`, `prt-portal`, `prtrust.fund`, `dev.prtrust.fund` -> `--brand prt --app prt`
+   - If the target is a file path and brand/app are not obvious, ask one concise question for the missing brand/app. Do not search broadly or show the generic command menu.
+   - Canonical start call:
+     ```powershell
+     curl.exe -s -X POST "http://127.0.0.1:52437/studio/debug/start" `
+       -H "Content-Type: application/json" `
+       -d "{\"brandSlug\":\"<brandSlug>\",\"appSlug\":\"<appSlug>\",\"repoRoot\":\"C:/Dev/regen-root\",\"cwd\":\"C:/Dev/regen-root\",\"modeDefault\":\"direct_edit\",\"startedBy\":\"claude-cli\"}"
+     ```
+   - Expected successful response shape:
+     ```json
+     {
+       "ok": true,
+       "sessionId": "studio-...",
+       "token": "...",
+       "devUrl": "http://localhost:3006",
+       "relayBaseUrl": "http://127.0.0.1:52437/studio/debug/studio-...",
+       "claudeBaseUrl": "http://127.0.0.1:52437/studio/claude/studio-...",
+       "pollCommand": "node scripts/studio-debug-poll.mjs --session ... --token ... --relay ..."
+     }
+     ```
+   - Construct the Studio attach URL exactly:
+     ```txt
+     http://localhost:3011/editor/local/<brandSlug>?attach=1&sessionId=<sessionId>&token=<token>
+     ```
+   - Never send the user to `/editor/local/<brandSlug>` without `attach=1&sessionId=...&token=...`.
+   - Canonical poll call:
+     ```powershell
+     curl.exe -s "http://127.0.0.1:52437/studio/claude/<sessionId>/poll?token=<token>&timeout=600000"
+     ```
+   - Canonical reply call:
+     ```powershell
+     curl.exe -s -X POST "http://127.0.0.1:52437/studio/claude/<sessionId>/reply" `
+       -H "Content-Type: application/json" `
+       -d "{\"token\":\"<token>\",\"eventId\":\"<eventId>\",\"status\":\"done\",\"message\":\"Edited <path>\",\"filesChanged\":[\"<path>\"]}"
+     ```
+   - Allowed terminal statuses are `done`, `error`, `blocked`, and `needs_reference`.
+   - Convenience helper, equivalent to the canonical start call plus attach URL construction:
+     ```powershell
+     node scripts/studio-debug-start.mjs --target <url|domain|brand|app|file> [--brand <slug>] [--app <slug>] [--mode direct_edit|variant_edit|reference_replace|note] [--studio-origin http://localhost:3011] [--connector http://127.0.0.1:52437] [--repo-root C:/Dev/regen-root] [--cwd C:/Dev/regen-root] [--dev-url <url>] [--dev-command <command>] [--no-launch]
+     ```
+   - Helper output contract:
+     ```txt
+     STUDIO_URL=http://localhost:3011/editor/local/<brandSlug>?attach=1&sessionId=...&token=...
+     POLL_COMMAND=node scripts/studio-debug-poll.mjs --session ... --token ... --relay ...
+     SESSION_FILE=.studio-debug/<sessionId>.json
+     ```
+   - If using the helper, run:
+     ```powershell
+     node scripts/studio-debug-start.mjs --target <target>
+     ```
+   - Return `STUDIO_URL` and `POLL_COMMAND` to the user. If operating as Claude CLI, open or instruct opening `STUDIO_URL`, then run `POLL_COMMAND`.
+   - After an event is received, edit the source directly and reply with the helper or canonical reply call:
+     ```powershell
+     node scripts/studio-debug-poll.mjs --session <sessionId> --token <token> --relay <claudeBaseUrl> --reply <eventId> done --file <path> --message "Edited <path>"
+     ```
+
+5. **Use Rampa only as proposal tooling.**
    - Run Rampa CLI for color ramps, APCA/WCAG checks, tinted neutrals, status palettes, or data-viz palettes.
    - Treat output as draft design material.
    - Persist only after mapping into Studio token roles or Palette Library payloads.
 
-5. **Apply RDC design rules.**
+6. **Apply RDC design rules.**
    - Use Studio tokens for production surfaces.
    - Do not hardcode color/font/spacing when a token exists.
    - Do not modify locked governance tokens.
    - Keep product UIs compact, operational, and scannable.
    - Avoid generic AI design patterns and card-heavy layouts.
 
-6. **Plan edits before mutating files.**
+7. **Plan edits before mutating files.**
    - State the files/routes/tables involved.
    - Use RDC work-item protocol for non-trivial implementation.
-   - Keep upstream Impeccable installed and untouched.
+   - Keep unrelated installed skills and vendor artifacts untouched.
 
-7. **Verify.**
+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/`.
@@ -100,6 +173,7 @@ Project docs to read for Studio work:
 
 | Command | Purpose |
 |---|---|
+| `edit` | Start a local source-edit session for a URL, app, brand, route, or file |
 | `studio` | Studio-aware design/build task with token, route, and editor context |
 | `tokens` | Diagnose or design token usage, resolver flow, API/export, governance |
 | `palette` | Palette Library work, palette generation, external Palette Designer handoff |
@@ -130,9 +204,9 @@ Each run includes character count, word count, approximate token count, referenc
 
 ## Boundaries
 
-- Do not edit installed Impeccable skills.
-- Do not create another skill named `impeccable`.
-- Do not use Impeccable Live as Studio's live-edit execution path.
+- Do not edit unrelated installed skills.
+- Do not rename this skill or create duplicate aliases for it.
+- Do not use external live-edit runtimes as Studio's live-edit execution path.
 - Do not persist Rampa output directly to production without Studio token mapping.
 - Do not fork or ship Palette Designer until its license is verified.
 - Do not use Studio's deprecated `/api/editor/render` route.

package/skills/design/reference/ownership.md

@@ -0,0 +1,16 @@
+# RDC Design Ownership
+
+RDC Design is the RDC-owned design skill for Studio and LIFEAI interface work.
+
+## Operating Boundary
+
+- Use this skill for Studio, tokens, palettes, themes, local-debug editing, and RDC product UI.
+- Keep unrelated installed skills and vendor artifacts untouched.
+- Keep third-party attribution in dedicated license or notice files on disk, not in operational skill prompts.
+- Use Studio docs, Studio APIs, and token tables as the source of truth.
+
+## Attribution Files
+
+When a feature uses third-party code or derives from third-party implementation details, preserve attribution in repository license, notice, or readme files that ship with that artifact.
+
+Operational skills should describe RDC-owned workflows directly so agents do not route Studio work through unrelated tools.

package/skills/design/reference/studio-model.md

@@ -48,7 +48,7 @@ Clauth relay route families:
 
 ## Native Local Debug Model
 
-Studio live editing must use the RDC-owned local debug system, not Impeccable Live:
+Studio live editing must use the RDC-owned local debug system, not an external live-edit runtime:
 
 1. Studio starts a local session with `POST /studio/debug/start`.
 2. Studio embeds the returned local `devUrl` with debug query params.

package/skills/design/reference/lineage.md

@@ -1,31 +0,0 @@
-# RDC Design Lineage
-
-RDC Design is inspired by and adapted from the Impeccable design workflow. Upstream Impeccable remains installed separately and untouched.
-
-## Rules
-
-- Keep the installed Impeccable skill available for direct use.
-- Do not rename or overwrite installed Impeccable files.
-- Do not create a second skill named `impeccable`.
-- Use `rdc:design` for RDC, Studio, token, Palette Library, Rampa CLI, and LIFEAI interface work.
-- Preserve third-party license and notice files if source material is forked or vendored.
-
-## Attribution Text
-
-Use this attribution in docs or NOTICE files when the implementation materially derives from Impeccable:
-
-```text
-RDC Design is inspired by and adapted from the Impeccable design workflow by Paul Bakaus.
-Upstream Impeccable remains a separate installed skill.
-```
-
-## Practical Boundary
-
-Concepts such as audit, polish, colorize, shape, craft, and anti-pattern checks are useful workflow patterns. RDC Design replaces the generic project model with RDC-specific knowledge:
-
-- Studio as token authority
-- Palette Library as palette persistence boundary
-- Rampa CLI as proposal tooling
-- RDC work-item protocol
-- local Studio editor/debug routes
-- real LIFEAI app and package paths