@lifeaitools/rdc-skills 0.35.6 → 0.35.8

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`

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/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/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/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/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

package/guides/agents/content.md

@@ -1,94 +1,94 @@
-> **⚠️ 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`).
-
-
-# rdc:content — Content Agent
-
-## Mandatory First Step
-
-Read the guide before writing ANY copy:
-```
-{PROJECT_ROOT}/.rdc/guides/content.md
-(fallback: {PROJECT_ROOT}/.rdc/guides/content.md)
-```
-
-## Core Message Development
-
-Before writing any copy:
-
-1. Define the lead word or core concept (e.g., "Stewardship", "Community", "Trust")
-2. State the core message in 1-2 sentences
-3. List language to always use
-4. List language to never use
-5. Define target audiences and key messages for each
-
-## Language Rules Pattern
-
-### Always Use
-- Core concept words (replace vague synonyms)
-- Specific, measurable terms
-- Active voice where possible
-- Real data, not approximations
-
-### Never Use
-| Avoid | Use Instead |
-|-------|-------------|
-| Vague concept | Specific term |
-| Passive construction | Active voice |
-| Clichéd term | Domain-specific language |
-
-## Regulatory Context
-
-Verify what regulations apply to your content before writing:
-- Never guarantee results or returns
-- Use ranges and targets, not promises
-- Include necessary disclaimers
-- Maintain transparency about assumptions
-
-## Audience Segments
-
-Define key audiences and their primary concerns:
-- What matters to this group?
-- What is their current perception?
-- What action do you want them to take?
-
-## Key Facts
-
-Maintain a source-of-truth list:
-- Financial figures
-- Timelines
-- Commitments
-- Metrics
-
-Never invent these — always verify.
-
-## Tone Template
-
-- Authority level: high/medium/low
-- Formality: formal/casual
-- Technical depth: detailed/accessible
-- Emotion: neutral/passionate
-- Speed: short/long form
-
-## Content Queue (save to database)
-
-```sql
-INSERT INTO content_queue (title, content_type, status, draft_body)
-VALUES (
-  'Email subject or article title',
-  'email_sequence',  -- or: social_post, article, newsletter, landing_copy
-  'draft',
-  '...'
-);
-```
-
-## Safety Rules
-
-- Never invent data — verify all figures
-- Never make legal claims — use "may be" language
-- Use prohibited words list when provided
-- Always include disclaimers for regulated content
-- Branch: development branch — commit content files to repo
+> **⚠️ 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`).
+
+
+# rdc:content — Content Agent
+
+## Mandatory First Step
+
+Read the guide before writing ANY copy:
+```
+{PROJECT_ROOT}/.rdc/guides/content.md
+(fallback: {PROJECT_ROOT}/.rdc/guides/content.md)
+```
+
+## Core Message Development
+
+Before writing any copy:
+
+1. Define the lead word or core concept (e.g., "Stewardship", "Community", "Trust")
+2. State the core message in 1-2 sentences
+3. List language to always use
+4. List language to never use
+5. Define target audiences and key messages for each
+
+## Language Rules Pattern
+
+### Always Use
+- Core concept words (replace vague synonyms)
+- Specific, measurable terms
+- Active voice where possible
+- Real data, not approximations
+
+### Never Use
+| Avoid | Use Instead |
+|-------|-------------|
+| Vague concept | Specific term |
+| Passive construction | Active voice |
+| Clichéd term | Domain-specific language |
+
+## Regulatory Context
+
+Verify what regulations apply to your content before writing:
+- Never guarantee results or returns
+- Use ranges and targets, not promises
+- Include necessary disclaimers
+- Maintain transparency about assumptions
+
+## Audience Segments
+
+Define key audiences and their primary concerns:
+- What matters to this group?
+- What is their current perception?
+- What action do you want them to take?
+
+## Key Facts
+
+Maintain a source-of-truth list:
+- Financial figures
+- Timelines
+- Commitments
+- Metrics
+
+Never invent these — always verify.
+
+## Tone Template
+
+- Authority level: high/medium/low
+- Formality: formal/casual
+- Technical depth: detailed/accessible
+- Emotion: neutral/passionate
+- Speed: short/long form
+
+## Content Queue (save to database)
+
+```sql
+INSERT INTO content_queue (title, content_type, status, draft_body)
+VALUES (
+  'Email subject or article title',
+  'email_sequence',  -- or: social_post, article, newsletter, landing_copy
+  'draft',
+  '...'
+);
+```
+
+## Safety Rules
+
+- Never invent data — verify all figures
+- Never make legal claims — use "may be" language
+- Use prohibited words list when provided
+- Always include disclaimers for regulated content
+- Branch: development branch — commit content files to repo

package/guides/agents/cs2.md

@@ -1,56 +1,56 @@
-> **⚠️ 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`).
-
-
-# rdc:cs2 — CS 2.0 Agent
-
-## Mandatory First Step
-
-Read the guide before ANY code:
-```
-{PROJECT_ROOT}/.rdc/guides/cs2.md
-(fallback: {PROJECT_ROOT}/.rdc/guides/cs2.md)
-```
-
-Also read the master spec:
-```
-{PROJECT_ROOT}/docs/systems/cs2/cs2-master-spec.md
-{PROJECT_ROOT}/docs/systems/cs2/package-map.md
-```
-
-## The Paradigm Check
-
-**Before writing ANY code, ask:**
-> "Is this building a new computational primitive, or am I wiring a UI to a database?"
-
-If the latter — STOP. That is CS 1.0 thinking. Route to `rdc:frontend` + `rdc:backend`.
-
-## Package Dependency Graph
-
-Respect this — never create circular deps:
-
-```
-Layer 0 (roots): cs2, core-primitive-1, core-primitive-2
-Layer 1: system-a(core-primitive-1), system-b(core-primitive-2)
-Layer 2: advanced-system(system-a, system-b)
-```
-
-Apps depend on `@regen/` packages. **Apps never depend on each other.**
-
-## TypeScript — No `any`, No Escape Hatches
-
-CS 2.0 packages must be fully typed. If you hit a type boundary you cannot express,
-that is a signal the abstraction is wrong — fix the model, not the types.
-
-## Safety Rules
-
-- Branch: development branch — auto-commit per package
-- NEVER run `pnpm build` — use `npx tsc --noEmit --project packages/<n>/tsconfig.json`
-- Respect the dependency graph — no circular deps
-- Never self-modify governance weights from executing layers
-- All immutable proofs are permanent — never update committed data
-- NEVER overlap agents on the same package
-- Write tests FIRST — red → implement → green
+> **⚠️ 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`).
+
+
+# rdc:cs2 — CS 2.0 Agent
+
+## Mandatory First Step
+
+Read the guide before ANY code:
+```
+{PROJECT_ROOT}/.rdc/guides/cs2.md
+(fallback: {PROJECT_ROOT}/.rdc/guides/cs2.md)
+```
+
+Also read the master spec:
+```
+{PROJECT_ROOT}/docs/systems/cs2/cs2-master-spec.md
+{PROJECT_ROOT}/docs/systems/cs2/package-map.md
+```
+
+## The Paradigm Check
+
+**Before writing ANY code, ask:**
+> "Is this building a new computational primitive, or am I wiring a UI to a database?"
+
+If the latter — STOP. That is CS 1.0 thinking. Route to `rdc:frontend` + `rdc:backend`.
+
+## Package Dependency Graph
+
+Respect this — never create circular deps:
+
+```
+Layer 0 (roots): cs2, core-primitive-1, core-primitive-2
+Layer 1: system-a(core-primitive-1), system-b(core-primitive-2)
+Layer 2: advanced-system(system-a, system-b)
+```
+
+Apps depend on `@regen/` packages. **Apps never depend on each other.**
+
+## TypeScript — No `any`, No Escape Hatches
+
+CS 2.0 packages must be fully typed. If you hit a type boundary you cannot express,
+that is a signal the abstraction is wrong — fix the model, not the types.
+
+## Safety Rules
+
+- Branch: development branch — auto-commit per package
+- NEVER run `pnpm build` — use `npx tsc --noEmit --project packages/<n>/tsconfig.json`
+- Respect the dependency graph — no circular deps
+- Never self-modify governance weights from executing layers
+- All immutable proofs are permanent — never update committed data
+- NEVER overlap agents on the same package
+- Write tests FIRST — red → implement → green