@lifeaitools/rdc-skills 0.35.5 → 0.35.7

package/commands/flow.md

@@ -1,7 +1,6 @@
 ---
 name: flow
-description: >-
-  Usage `rdc:flow [status|<state> ["<reason>"]|normal]` — show or set the current flow state. Flow is the single FSM surface for both work-shape (plan/design/collab/build/refactor/overnight/harness-testing) and ceremony relaxation (hotfix/maintenance). Supersedes `rdc:mode` — hotfix/maintenance are flow values now, not a separate system.
+description: rdc:flow [status|<state> ["<reason>"]|normal] — show or set the flow state
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
@@ -49,7 +48,7 @@ rdc:flow normal                   # clear — back to no flow declared
 ### 1. Read the current state
 
 ```bash
-node -e "import('file:///C:/Dev/lifeai-env/hooks/lib/rdc-flow.mjs').then(m=>console.log(JSON.stringify(m.currentState(),null,2)))"
+node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-flow.mjs').href).then(m=>console.log(JSON.stringify(m.currentState(),null,2)))"
 ```
 
 `currentState()` reads BOTH axes at once — the declared flow AND any live `rdc-mode.mjs` hotfix/maintenance window — because a relaxed mode overrides a required flow (loosest state wins) and a status check that only showed flow would miss that override entirely. Report `flow` (or `null` if nothing declared — the fail-closed default), `flowReason`/`flowSetBy`/`flowSetAt` when set, and `mode` (`normal` unless a hotfix/maintenance window is open), with `modeReason`/`modeMinutesLeft` when it isn't.
@@ -57,7 +56,7 @@ node -e "import('file:///C:/Dev/lifeai-env/hooks/lib/rdc-flow.mjs').then(m=>cons
 ### 2. Setting a plain work-shape flow — no reason required
 
 ```bash
-node -e "import('file:///C:/Dev/lifeai-env/hooks/lib/rdc-flow.mjs').then(m=>console.log(JSON.stringify(m.setFlow(process.argv[1],{setBy:process.argv[2]}),null,2)))" "<flow>" "<session-id>"
+node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-flow.mjs').href).then(m=>console.log(JSON.stringify(m.setFlow(process.argv[1],{setBy:process.argv[2]}),null,2)))" "<flow>" "<session-id>"
 ```
 
 ### 3. Setting hotfix or maintenance — a reason is REQUIRED
@@ -65,7 +64,7 @@ node -e "import('file:///C:/Dev/lifeai-env/hooks/lib/rdc-flow.mjs').then(m=>cons
 Refuse to proceed without one — `setFlow` throws on an empty reason for these two values, by design, same as `setMode` always did: an unexplained disarm is how a temporary state becomes permanent.
 
 ```bash
-node -e "import('file:///C:/Dev/lifeai-env/hooks/lib/rdc-flow.mjs').then(m=>console.log(JSON.stringify(m.setFlow('hotfix',{reason:process.argv[1],setBy:process.argv[2]}),null,2)))" "<reason>" "<session-id>"
+node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-flow.mjs').href).then(m=>console.log(JSON.stringify(m.setFlow('hotfix',{reason:process.argv[1],setBy:process.argv[2]}),null,2)))" "<reason>" "<session-id>"
 ```
 
 Then state plainly, in the checklist: **which guards are now relaxed, that the safety set is still armed, and that this stays active until explicitly cleared (no TTL — active management, not a silent timer).**
@@ -73,7 +72,7 @@ Then state plainly, in the checklist: **which guards are now relaxed, that the s
 ### 4. Returning to normal
 
 ```bash
-node -e "import('file:///C:/Dev/lifeai-env/hooks/lib/rdc-flow.mjs').then(m=>{m.clearFlow();console.log('cleared')})"
+node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-flow.mjs').href).then(m=>{m.clearFlow();console.log('cleared')})"
 ```
 
 Do this **as soon as the incident is over**, or the moment the declared work-shape changes.

package/commands/full-analysis.md

@@ -1,12 +1,6 @@
 ---
 name: full-analysis
-description: >-
-  Usage `rdc:full-analysis <path> [--diff <ref>]` — runs all seven surfaces
-  (solid-validator, architecture-reviewer, clean-code-analyzer,
-  package-design, pattern-advisor, testing-strategy, and
-  pattern-refactoring-guide on anything the others flag) and merges into
-  one report. The full form/fit/function pass — use before merging a new
-  package or a significant refactor, not for routine edits.
+description: rdc:full-analysis <path> [--diff <ref>] — run all seven review surfaces over a path
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/get-refactoring-plan.md

@@ -1,10 +1,6 @@
 ---
 name: get-refactoring-plan
-description: >-
-  Usage `rdc:get-refactoring-plan <finding>` — turns a solid-validator/
-  architecture-reviewer/pattern-advisor finding into a step-ordered
-  before/after refactor plan. Produces a plan, does not apply it. See
-  skills/pattern-refactoring-guide.
+description: rdc:get-refactoring-plan <finding> — turn a finding into a step-ordered before/after plan
 ---
 
 # get-refactoring-plan

package/commands/handoff.md

@@ -1,7 +1,6 @@
 ---
 name: handoff
-description: >-
-  Usage `rdc:handoff <topic>` — structured handoff from planning session to CLI agents. Produces plan doc in .rdc/plans/, work items in DB, prototype registry entry if applicable. Use when plan/prototype is finalized and ready for implementation.
+description: rdc:handoff () - [--from-prototype] — turn a plan or prototype into work items and artifacts
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/help.md

@@ -1,8 +1,6 @@
 ---
 name: help
-description: >-
-  Usage `rdc:help` or `rdc` — manifest-driven menu of all MCP skills with
-  argument syntax, requirements, decision hints, and direct MCP/curl access.
+description: rdc:help () — list all MCP skills with usage, requirements and slash form
 ---
 
 > **Output contract:** Checklist/table output only. No raw MCP/JSON/log dumps.

package/commands/mode.md

@@ -1,7 +1,6 @@
 ---
 name: mode
-description: >-
-  Usage `rdc:mode [status|hotfix "<reason>" [minutes]|normal]` — show or set the operating mode. HotFix relaxes ceremony gates for a bounded window; it never relaxes a safety guard.
+description: rdc:mode [status|hotfix "<reason>" [minutes]|normal] — show or set the operating mode
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
@@ -70,7 +69,7 @@ rdc:mode normal                       # close it early
 ### 1. Read the current mode
 
 ```bash
-node -e "import('file:///C:/Dev/lifeai-env/hooks/lib/rdc-mode.mjs').then(m=>console.log(JSON.stringify(m.currentMode(),null,2)))"
+node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-mode.mjs').href).then(m=>console.log(JSON.stringify(m.currentMode(),null,2)))"
 ```
 
 Report `mode`, and when not normal also `reason`, `setBy`, and `minutesLeft`.
@@ -84,7 +83,7 @@ unexplained disarm is how a temporary state becomes permanent, and the reason is
 the entire content of the audit line.
 
 ```bash
-node -e "import('file:///C:/Dev/lifeai-env/hooks/lib/rdc-mode.mjs').then(m=>console.log(JSON.stringify(m.setMode('hotfix',{reason:process.argv[1],minutes:Number(process.argv[2]||60),setBy:process.argv[3]}),null,2)))" "<reason>" "<minutes>" "<session-id>"
+node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-mode.mjs').href).then(m=>console.log(JSON.stringify(m.setMode('hotfix',{reason:process.argv[1],minutes:Number(process.argv[2]||60),setBy:process.argv[3]}),null,2)))" "<reason>" "<minutes>" "<session-id>"
 ```
 
 Then state plainly, in the checklist: **which guards are now off, that the safety
@@ -93,7 +92,7 @@ set is still armed, and the exact wall-clock time the window closes.**
 ### 3. Returning to normal
 
 ```bash
-node -e "import('file:///C:/Dev/lifeai-env/hooks/lib/rdc-mode.mjs').then(m=>{m.clearMode();console.log('normal')})"
+node -e "import(require('url').pathToFileURL(process.env.LIFEAI_ENV + '/hooks/lib/rdc-mode.mjs').href).then(m=>{m.clearMode();console.log('normal')})"
 ```
 
 Do this **as soon as the incident is over**. The window expiring on its own is

package/commands/overnight.md

@@ -1,7 +1,6 @@
 ---
 name: overnight
-description: >-
-  Usage `rdc:overnight [epic-id|label=X]` — unattended overnight supervisor, chains preplan → plan → build → review → report across all high-priority epics in --unattended mode. Use for "run overnight", "build while I sleep".
+description: rdc:overnight ([scope]) — drain the work queue unattended, end to end
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/plan.md

@@ -1,7 +1,6 @@
 ---
 name: plan
-description: >-
-  Usage `rdc:plan <topic> [--unattended]` — architecture doc with design decisions, tradeoffs, work packages. Creates Supabase epics/tasks. Use after rdc:preplan or when given clear architectural direction.
+description: rdc:plan (topic) — produce architecture, decisions and an epic with tasks
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/preplan.md

@@ -1,7 +1,6 @@
 ---
 name: preplan
-description: >-
-  Usage `rdc:preplan <topic> [--unattended]` — research best practices, analyze codebase, compare approaches, surface unknowns before committing to a plan. Produces a research doc. No decisions, no code.
+description: rdc:preplan (topic) — research the unknowns before committing to an architecture
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/prototype.md

@@ -1,7 +1,6 @@
 ---
 name: prototype
-description: >-
-  Usage `rdc:prototype <description>` — build JSX/TSX prototype for review before CLI handoff. Saves to docs/source/, registers in prototype_registry. Use for "mock this up", "show me what it looks like". Reference material only, not production.
+description: rdc:prototype (description) — build a JSX/TSX mockup for visual review
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/quick-check.md

@@ -1,9 +1,6 @@
 ---
 name: quick-check
-description: >-
-  Usage `rdc:quick-check <path>` — fast mechanical-only pass: solid-validator
-  score + boundary check. No dispatched judgment agents. For a tight
-  iteration loop, not a merge gate.
+description: rdc:quick-check <path> — fast mechanical pass, SOLID score and boundary check
 ---
 
 # quick-check

package/commands/recover.md

@@ -1,7 +1,6 @@
 ---
 name: recover
-description: >-
-  Usage `rdc:recover [list|start]` — deterministic post-crash recovery: detect, repair (CodeFlow/PM2 only), verify, then find and resume abandoned Claude/Codex worktree-lane sessions.
+description: rdc:recover [list|start] — detect, repair and resume after a crash
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/release.md

@@ -1,6 +1,6 @@
 ---
-description: >-
-  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.
+
+description: rdc:release (repo, [version]) - [--patch, --minor, --major, --dry-run] — bump, tag, publish and verify a package
 ---
 
 # rdc:release — Generic Release

package/commands/report.md

@@ -1,7 +1,6 @@
 ---
 name: report
-description: >-
-  Usage `rdc:report [--unattended]` — nightly markdown report, writes to .rdc/reports/YYYY-MM-DD.md. Covers completed/open work items, per-project progress, infra status, git stats, test counts.
+description: rdc:report () — write the session summary to .rdc/reports/
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/review-arch.md

@@ -1,9 +1,6 @@
 ---
 name: review-arch
-description: >-
-  Usage `rdc:review-arch <path> [--diff <ref>]` — layering/dependency-
-  direction review, mechanical + judgment (FIT corner). See
-  skills/architecture-reviewer.
+description: rdc:review-arch <path> [--diff <ref>] — review layering and dependency direction
 ---
 
 # review-arch

package/commands/review.md

@@ -1,10 +1,6 @@
 ---
 name: review
-description: >-
-  Usage `rdc:review [--unattended]` — post-build quality gate: tsc, tests,
-  stale docs, export conflicts, a mandatory pr-review-toolkit:code-reviewer
-  pass, and the form/fit/function gate (solid-validator + architecture-
-  reviewer) across modified packages. See skills/review.
+description: rdc:review () - [--unattended] — post-build gate over tsc, tests, docs and code review
 ---
 
 # review

package/commands/self-test.md

@@ -1,7 +1,6 @@
 ---
 name: self-test
-description: >-
-  Usage `rdc:self-test [--strict] [--skill <name>] [--json] [--fix] [--tier2] [--parallel <n>] [--quick]` — validates every rdc-*.md skill: frontmatter, Usage marker, name↔filename match, referenced guides/rules/hooks exist, output contract banner, plugin manifest, duplicate-name + collision checks. Tier 1 static lint; Tier 2 behavioral runs via headless Claude or Codex in isolated worktrees + Supabase branch. Run before every release.
+description: rdc:self-test () - [--strict] — validate every rdc skill, the manifest and tooling
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/status.md

@@ -1,7 +1,6 @@
 ---
 name: status
-description: >-
-  Usage `rdc:status` — open epics, work items by project, Coolify health, blockers, next recommended action. Read-only situational awareness.
+description: rdc:status () — snapshot open epics, health, blockers and next action
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/suggest-patterns.md

@@ -1,9 +1,6 @@
 ---
 name: suggest-patterns
-description: >-
-  Usage `rdc:suggest-patterns <path>` — design pattern suggestions,
-  advisory only, "no pattern needed" is a valid verdict. See
-  skills/pattern-advisor.
+description: rdc:suggest-patterns <path> — suggest design patterns; "none needed" is a valid verdict
 ---
 
 # suggest-patterns

package/commands/validate-solid.md

@@ -1,8 +1,6 @@
 ---
 name: validate-solid
-description: >-
-  Usage `rdc:validate-solid <path> [--diff <ref>]` — deterministic SOLID +
-  Clean Architecture scoring (FORM corner). See skills/solid-validator.
+description: rdc:validate-solid <path> [--diff <ref>] — score SOLID and Clean Architecture deterministically
 ---
 
 # validate-solid

package/commands/watch.md

@@ -1,7 +1,6 @@
 ---
 name: watch
-description: >-
-  Usage `rdc:watch` — initialize a session-log viewer and report its path; open it only during attended, non-test use. Zero infra, pure filesystem + static HTML.
+description: rdc:watch () — open a live session-log viewer and report its path
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/commands/workitems.md

@@ -1,7 +1,6 @@
 ---
 name: workitems
-description: >-
-  Usage `rdc:workitems <action> [args]` — create, update, query work items via Supabase RPCs. Actions: add, update, done, list, epics. Use for "add to backlog", "mark done", "show open epics", any work item CRUD.
+description: rdc:workitems ([subcommand]) — create, update and query work items directly
 ---
 
 > **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`

package/guides/agents/backend.md

@@ -1,104 +1,104 @@
-> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
-> Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
-> One checklist upfront, updated in place, shown again at end with a 1-line verdict.
-
-> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md`).
-
-> **Sandbox contract:** This guide honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Destructive external calls short-circuit under the flag.
-
-
-# rdc:backend — Backend Agent
-
-## Mandatory First Step
-
-Read the guide before ANY code:
-```
-{PROJECT_ROOT}/.rdc/guides/backend.md
-(fallback: {PROJECT_ROOT}/.rdc/guides/backend.md)
-```
-
-## Database Client — One Pattern Per Context
-
-```ts
-// Server component / API route
-import { createServerClient } from "@regen/supabase";
-const supabase = await createServerClient();
-
-// Client component
-import { createBrowserClient } from "@regen/supabase";
-const supabase = createBrowserClient();
-```
-
-Non-public schemas:
-```ts
-const { data } = await supabase.schema("custom").from("table_name").select("*");
-```
-
-## Credentials — Daemon First
-
-```bash
-curl -s http://127.0.0.1:52437/get/<service>
-```
-- Never hardcode credentials
-- Never print keys to stdout
-- If daemon is down: report BLOCKED — do not work around it
-
-## Work Items — RPC Only
-
-```sql
--- Read epics
-SELECT get_open_epics();
-
--- Create
-SELECT insert_work_item(
-  p_title := 'Task title',
-  p_priority := 'high',
-  p_parent_id := '<epic-uuid>'::uuid,
-  p_source := 'agent'
-);
-
+> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
+> Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
+> One checklist upfront, updated in place, shown again at end with a 1-line verdict.
+
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md`).
+
+> **Sandbox contract:** This guide honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Destructive external calls short-circuit under the flag.
+
+
+# rdc:backend — Backend Agent
+
+## Mandatory First Step
+
+Read the guide before ANY code:
+```
+{PROJECT_ROOT}/.rdc/guides/backend.md
+(fallback: {PROJECT_ROOT}/.rdc/guides/backend.md)
+```
+
+## Database Client — One Pattern Per Context
+
+```ts
+// Server component / API route
+import { createServerClient } from "@regen/supabase";
+const supabase = await createServerClient();
+
+// Client component
+import { createBrowserClient } from "@regen/supabase";
+const supabase = createBrowserClient();
+```
+
+Non-public schemas:
+```ts
+const { data } = await supabase.schema("custom").from("table_name").select("*");
+```
+
+## Credentials — Daemon First
+
+```bash
+curl -s http://127.0.0.1:52437/get/<service>
+```
+- Never hardcode credentials
+- Never print keys to stdout
+- If daemon is down: report BLOCKED — do not work around it
+
+## Work Items — RPC Only
+
+```sql
+-- Read epics
+SELECT get_open_epics();
+
+-- Create
+SELECT insert_work_item(
+  p_title := 'Task title',
+  p_priority := 'high',
+  p_parent_id := '<epic-uuid>'::uuid,
+  p_source := 'agent'
+);
+
 -- Implementation agents submit report + CodeFlow post, then move to review
 SELECT update_work_item_status('<uuid>'::uuid, 'review', '["Implementation complete; ready for validator"]'::jsonb, '<agent-session-id>', 'agent');
-```
-
-**NEVER write raw INSERT/UPDATE against work items.**
-
-## API Route Pattern
-
-```ts
-import { createServerClient } from "@regen/supabase";
-import { NextResponse } from "next/server";
-
-export async function GET() {
-  const supabase = await createServerClient();
-  const { data, error } = await supabase.from("table").select("*");
-  if (error) return NextResponse.json({ error: error.message }, { status: 500 });
-  return NextResponse.json(data);
-}
-
-export async function POST(request: Request) {
-  const body = await request.json();
-  const supabase = await createServerClient();
-  const { data, error } = await supabase.from("table").insert(body).select().single();
-  if (error) return NextResponse.json({ error: error.message }, { status: 400 });
-  return NextResponse.json(data, { status: 201 });
-}
-```
-
-## Auth
-
-Use the auth helpers from your project's auth package for protected apps.
-
-## Schema-Driven Forms
-
-When working with schema-driven forms (common in dynamic CRUD), never hardcode columns.
-Use the schema table to drive form rendering instead.
-
-## Safety Rules
-
-- Branch: development branch — auto-commit after logical blocks
-- NEVER run `pnpm build`
-- NEVER overlap with other agents on the same files
-- Update work items in real time — not batch at end
-- Push after each logical block *(skip if `$RDC_TEST=1` — echo `[RDC_TEST] skipping git push` instead)*
-- Write tests FIRST — red → implement → green
+```
+
+**NEVER write raw INSERT/UPDATE against work items.**
+
+## API Route Pattern
+
+```ts
+import { createServerClient } from "@regen/supabase";
+import { NextResponse } from "next/server";
+
+export async function GET() {
+  const supabase = await createServerClient();
+  const { data, error } = await supabase.from("table").select("*");
+  if (error) return NextResponse.json({ error: error.message }, { status: 500 });
+  return NextResponse.json(data);
+}
+
+export async function POST(request: Request) {
+  const body = await request.json();
+  const supabase = await createServerClient();
+  const { data, error } = await supabase.from("table").insert(body).select().single();
+  if (error) return NextResponse.json({ error: error.message }, { status: 400 });
+  return NextResponse.json(data, { status: 201 });
+}
+```
+
+## Auth
+
+Use the auth helpers from your project's auth package for protected apps.
+
+## Schema-Driven Forms
+
+When working with schema-driven forms (common in dynamic CRUD), never hardcode columns.
+Use the schema table to drive form rendering instead.
+
+## Safety Rules
+
+- Branch: development branch — auto-commit after logical blocks
+- NEVER run `pnpm build`
+- NEVER overlap with other agents on the same files
+- Update work items in real time — not batch at end
+- Push after each logical block *(skip if `$RDC_TEST=1` — echo `[RDC_TEST] skipping git push` instead)*
+- Write tests FIRST — red → implement → green