@lifeaitools/rdc-skills 0.24.41 → 0.25.0

package/commands/prototype.md

@@ -1,145 +1,145 @@
----
-name: rdc: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.
----
-
-> **⚠️ 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:prototype — Prototype Builder
-
-## When to Use
-
-- Project lead wants to see a design before committing to implementation
-- A new component or page needs visual review before wiring to database
-- Testing a data layout or interaction pattern
-- Building a visual mockup for approval
-
-## What This Produces
-
-- JSX/TSX prototype file → `docs/source/<ComponentName>.jsx`
-- prototype_registry entry in database
-- design_context entries for key decisions
-
-## Prototype Rules
-
-1. **Self-contained** — no real database calls. Mock data arrays only.
-2. **Realistic data** — mock data must reflect actual schema field names
-3. **Full fidelity** — looks exactly like the final product should look
-4. **Annotated** — key design decisions commented at the top of the file
-5. **Handoff-ready** — includes the spec block at the bottom
-
-## Standard Mock Data Pattern
-
-Use realistic field names from the actual database schema:
-
-```tsx
-// Mock data — mirrors your_table
-const MOCK_DATA = [
-  {
-    id: "uuid-1",
-    slug: "example-slug",
-    name: "Example Name",
-    description: "...",
-    location_city: "City",
-    location_state: "State",
-    status: "active",
-    category: "example-category",
-    total_capital: 1000000,
-    total_area: 2400,
-    deploy_url: "https://...",
-    tags: ["tag1", "tag2"],
-    alignment: ["value1", "value2"],
-    web_visible: true,
-    ticker_label: "LABEL",
-    ticker_capital: "$1M",
-    scores: { field1: 82, field2: 71, field3: 68 },
-  },
-];
-```
-
-## File Header Template
-
-```tsx
-/**
- * <ComponentName>.jsx — PROTOTYPE
- * ─────────────────────────────────────────────
- * Status: Prototype — reference only, not production code
- * Created: <date>
- * Route (production target): <app-route>
- *
- * Key design decisions:
- * 1. <Decision and rationale>
- * 2. <Decision and rationale>
- *
- * What to preserve in production:
- * - <Design element>
- * - <Interaction pattern>
- *
- * What production implementation must do differently:
- * - Replace mock data with database query
- * - Import <Component> from @regen/ui instead of inline implementation
- * - Extract <Part> into shared component at src/components/<name>
- *
- * Production agent type: frontend | backend | data | viz
- * Production guide: .rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md)
- */
-```
-
-## File Footer Template
-
-```tsx
-// ─── HANDOFF SPEC ─────────────────────────────
-// Production files:
-//   apps/<app>/src/app/<route>/page.tsx           (server component)
-//   apps/<app>/src/app/<route>/<Name>Client.tsx   (client component)
-//   apps/<app>/src/app/<route>/<Name>Wrapper.tsx  (modal/state shell, if needed)
-//
-// Design system components to use (do not re-implement):
-//   <ComponentName> — <what it does>
-//
-// Database tables:
-//   <table> — <what to query>
-//
-// Form field schema additions needed:
-//   <table>.<column> — <input_type> — <label>
-```
-
-## After Building — Register and Record
-
-```sql
--- Register prototype
-INSERT INTO prototype_registry (name, component, source_path, notes, created_by)
-VALUES (
-  '<Name> Prototype v1',
-  '<ComponentName>',
-  'docs/source/<ComponentName>.jsx',
-  '<One-line description of key design: layout, data shape, interactions>',
-  'planning'
-);
-
--- Record design decisions
-INSERT INTO design_context (topic, context_type, summary, source, created_by)
-VALUES
-  ('<Topic>', 'prototype', 'Prototype built with <X> layout and <Y> interaction pattern', 'planning', 'planning'),
-  ('<Topic>', 'decision',  '<Key decision made during prototyping and why>', 'planning', 'planning');
-```
-
-## Handoff
-
-After prototype is approved, use `rdc:handoff` to create the plan doc and database work items.
-
-Or tell the project lead:
-```
-Prototype complete.
-File: docs/source/<ComponentName>.jsx
-Registered: prototype_registry
-
-To hand off to CLI build: use /rdc:handoff
-To build immediately: use /rdc:build
-```
+---
+name: rdc: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.
+---
+
+> **⚠️ 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:prototype — Prototype Builder
+
+## When to Use
+
+- Project lead wants to see a design before committing to implementation
+- A new component or page needs visual review before wiring to database
+- Testing a data layout or interaction pattern
+- Building a visual mockup for approval
+
+## What This Produces
+
+- JSX/TSX prototype file → `docs/source/<ComponentName>.jsx`
+- prototype_registry entry in database
+- design_context entries for key decisions
+
+## Prototype Rules
+
+1. **Self-contained** — no real database calls. Mock data arrays only.
+2. **Realistic data** — mock data must reflect actual schema field names
+3. **Full fidelity** — looks exactly like the final product should look
+4. **Annotated** — key design decisions commented at the top of the file
+5. **Handoff-ready** — includes the spec block at the bottom
+
+## Standard Mock Data Pattern
+
+Use realistic field names from the actual database schema:
+
+```tsx
+// Mock data — mirrors your_table
+const MOCK_DATA = [
+  {
+    id: "uuid-1",
+    slug: "example-slug",
+    name: "Example Name",
+    description: "...",
+    location_city: "City",
+    location_state: "State",
+    status: "active",
+    category: "example-category",
+    total_capital: 1000000,
+    total_area: 2400,
+    deploy_url: "https://...",
+    tags: ["tag1", "tag2"],
+    alignment: ["value1", "value2"],
+    web_visible: true,
+    ticker_label: "LABEL",
+    ticker_capital: "$1M",
+    scores: { field1: 82, field2: 71, field3: 68 },
+  },
+];
+```
+
+## File Header Template
+
+```tsx
+/**
+ * <ComponentName>.jsx — PROTOTYPE
+ * ─────────────────────────────────────────────
+ * Status: Prototype — reference only, not production code
+ * Created: <date>
+ * Route (production target): <app-route>
+ *
+ * Key design decisions:
+ * 1. <Decision and rationale>
+ * 2. <Decision and rationale>
+ *
+ * What to preserve in production:
+ * - <Design element>
+ * - <Interaction pattern>
+ *
+ * What production implementation must do differently:
+ * - Replace mock data with database query
+ * - Import <Component> from @regen/ui instead of inline implementation
+ * - Extract <Part> into shared component at src/components/<name>
+ *
+ * Production agent type: frontend | backend | data | viz
+ * Production guide: .rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md)
+ */
+```
+
+## File Footer Template
+
+```tsx
+// ─── HANDOFF SPEC ─────────────────────────────
+// Production files:
+//   apps/<app>/src/app/<route>/page.tsx           (server component)
+//   apps/<app>/src/app/<route>/<Name>Client.tsx   (client component)
+//   apps/<app>/src/app/<route>/<Name>Wrapper.tsx  (modal/state shell, if needed)
+//
+// Design system components to use (do not re-implement):
+//   <ComponentName> — <what it does>
+//
+// Database tables:
+//   <table> — <what to query>
+//
+// Form field schema additions needed:
+//   <table>.<column> — <input_type> — <label>
+```
+
+## After Building — Register and Record
+
+```sql
+-- Register prototype
+INSERT INTO prototype_registry (name, component, source_path, notes, created_by)
+VALUES (
+  '<Name> Prototype v1',
+  '<ComponentName>',
+  'docs/source/<ComponentName>.jsx',
+  '<One-line description of key design: layout, data shape, interactions>',
+  'planning'
+);
+
+-- Record design decisions
+INSERT INTO design_context (topic, context_type, summary, source, created_by)
+VALUES
+  ('<Topic>', 'prototype', 'Prototype built with <X> layout and <Y> interaction pattern', 'planning', 'planning'),
+  ('<Topic>', 'decision',  '<Key decision made during prototyping and why>', 'planning', 'planning');
+```
+
+## Handoff
+
+After prototype is approved, use `rdc:handoff` to create the plan doc and database work items.
+
+Or tell the project lead:
+```
+Prototype complete.
+File: docs/source/<ComponentName>.jsx
+Registered: prototype_registry
+
+To hand off to CLI build: use /rdc:handoff
+To build immediately: use /rdc:build
+```

package/commands/release.md

@@ -1,49 +1,49 @@
----
-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.
----
-
-# rdc:release — Generic Release
-
-> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
-> Checklist-only output. No raw git/npm/CI dumps.
-> One checklist upfront, updated in place, shown again at end with 1-line verdict.
-
-## Checklist
-
-```
-rdc:release: <repo> vX.Y.Z -> vA.B.C
-[ ] Source path resolved
-[ ] Release metadata read
-[ ] Working tree clean or user-approved dirty scope identified
-[ ] Current version detected
-[ ] New version computed
-[ ] Dry-run gate handled
-[ ] Version files updated
-[ ] Tests/self-test passed
-[ ] Commit created
-[ ] 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
-```
-
-## Rules
-
-- 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.
-
-## RDC Skills Package
-
-After publishing this package to npm, a clean-box install should use:
-
-```bash
-npm install -g @lifeaitools/rdc-skills@latest
-rdc-skills-install --profile core
-```
+---
+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.
+---
+
+# rdc:release — Generic Release
+
+> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
+> Checklist-only output. No raw git/npm/CI dumps.
+> One checklist upfront, updated in place, shown again at end with 1-line verdict.
+
+## Checklist
+
+```
+rdc:release: <repo> vX.Y.Z -> vA.B.C
+[ ] Source path resolved
+[ ] Release metadata read
+[ ] Working tree clean or user-approved dirty scope identified
+[ ] Current version detected
+[ ] New version computed
+[ ] Dry-run gate handled
+[ ] Version files updated
+[ ] Tests/self-test passed
+[ ] Commit created
+[ ] 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
+```
+
+## Rules
+
+- 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.
+
+## RDC Skills Package
+
+After publishing this package to npm, a clean-box install should use:
+
+```bash
+npm install -g @lifeaitools/rdc-skills@latest
+rdc-skills-install --profile core
+```

package/commands/report.md

@@ -1,99 +1,99 @@
----
-name: rdc: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.
----
-
-> **⚠️ 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:report — Nightly Report
-
-## When to Use
-- End of a build session
-- Project lead asks for a report or summary
-- Nightly scheduled task
-- Before handing off to another session
-- Called by `rdc:overnight` at the end of every session
-
-## Arguments
-- `rdc:report` — interactive, prints summary to conversation
-- `rdc:report --unattended` — silent mode, writes file only, returns status block
-
-## Procedure
-
-1. **Query completed work (last 24h or since last report):**
-   ```sql
-   SELECT title, labels, completed_at, notes
-   FROM work_items
-   WHERE completed_at > now() - interval '24 hours'
-   ORDER BY completed_at;
-   ```
-
-2. **Query open work:**
-   ```sql
-   SELECT title, status, priority, labels
-   FROM work_items
-   WHERE status IN ('todo', 'in_progress', 'blocked')
-   ORDER BY priority, created_at;
-   ```
-
-3. **Git stats (since last report or last 24h):**
-   ```bash
-   git log --since="24 hours ago" --shortstat --oneline
-   git diff --shortstat HEAD~N  # where N = commits in window
-   ```
-
-4. **Infrastructure deployment snapshot** (if MCP available):
-   - List all apps with current status
-   - Flag any failures
-
-5. **Write report** to `.rdc/reports/YYYY-MM-DD.md` (fallback: `.rdc/reports/YYYY-MM-DD.md` if `.rdc/` does not exist):
-   ```markdown
-   # Daily Report — YYYY-MM-DD
-
-   ## Completed Today
-   | Item | Project | Priority |
-
-   ## Git Activity
-   - Commits: N
-   - Files changed: N
-   - Lines: +N / -N
-
-   ## Open Work
-   ### Urgent (N)
-   ### High (N)
-   ### Normal (N)
-
-   ## Deployment Status
-   | App | Domain | Status |
-
-   ## Blockers
-   <any blocked items or failed deploys>
-
-   ## Next Session Recommendation
-   <highest priority unstarted work>
-   ```
-
-6. **Check if weekly rollup needed** (if today is Sunday):
-   - Aggregate daily reports for the week
-   - Write `.rdc/reports/week-YYYY-WNN.md` (fallback: `.rdc/reports/week-YYYY-WNN.md`)
-
-7. **Report results:**
-   - Interactive: print summary to conversation
-   - Unattended: no interactive output, emit status block only:
-     ```
-     REPORT_STATUS: { report_path, completed_count, open_count, blockers_count }
-     ```
-
-## Rules
-- Reports go in `.rdc/reports/` (fallback: `.rdc/reports/`) — create dir if missing
-- One report per day — overwrite if re-run same day
-- Keep under 100 lines — scannable, not exhaustive
-- Include links to relevant CLAUDE.md files where helpful
-- Always end with "Next Session Recommendation"
-- Unattended: NEVER print to conversation — write file only
+---
+name: rdc: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.
+---
+
+> **⚠️ 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:report — Nightly Report
+
+## When to Use
+- End of a build session
+- Project lead asks for a report or summary
+- Nightly scheduled task
+- Before handing off to another session
+- Called by `rdc:overnight` at the end of every session
+
+## Arguments
+- `rdc:report` — interactive, prints summary to conversation
+- `rdc:report --unattended` — silent mode, writes file only, returns status block
+
+## Procedure
+
+1. **Query completed work (last 24h or since last report):**
+   ```sql
+   SELECT title, labels, completed_at, notes
+   FROM work_items
+   WHERE completed_at > now() - interval '24 hours'
+   ORDER BY completed_at;
+   ```
+
+2. **Query open work:**
+   ```sql
+   SELECT title, status, priority, labels
+   FROM work_items
+   WHERE status IN ('todo', 'in_progress', 'blocked')
+   ORDER BY priority, created_at;
+   ```
+
+3. **Git stats (since last report or last 24h):**
+   ```bash
+   git log --since="24 hours ago" --shortstat --oneline
+   git diff --shortstat HEAD~N  # where N = commits in window
+   ```
+
+4. **Infrastructure deployment snapshot** (if MCP available):
+   - List all apps with current status
+   - Flag any failures
+
+5. **Write report** to `.rdc/reports/YYYY-MM-DD.md` (fallback: `.rdc/reports/YYYY-MM-DD.md` if `.rdc/` does not exist):
+   ```markdown
+   # Daily Report — YYYY-MM-DD
+
+   ## Completed Today
+   | Item | Project | Priority |
+
+   ## Git Activity
+   - Commits: N
+   - Files changed: N
+   - Lines: +N / -N
+
+   ## Open Work
+   ### Urgent (N)
+   ### High (N)
+   ### Normal (N)
+
+   ## Deployment Status
+   | App | Domain | Status |
+
+   ## Blockers
+   <any blocked items or failed deploys>
+
+   ## Next Session Recommendation
+   <highest priority unstarted work>
+   ```
+
+6. **Check if weekly rollup needed** (if today is Sunday):
+   - Aggregate daily reports for the week
+   - Write `.rdc/reports/week-YYYY-WNN.md` (fallback: `.rdc/reports/week-YYYY-WNN.md`)
+
+7. **Report results:**
+   - Interactive: print summary to conversation
+   - Unattended: no interactive output, emit status block only:
+     ```
+     REPORT_STATUS: { report_path, completed_count, open_count, blockers_count }
+     ```
+
+## Rules
+- Reports go in `.rdc/reports/` (fallback: `.rdc/reports/`) — create dir if missing
+- One report per day — overwrite if re-run same day
+- Keep under 100 lines — scannable, not exhaustive
+- Include links to relevant CLAUDE.md files where helpful
+- Always end with "Next Session Recommendation"
+- Unattended: NEVER print to conversation — write file only