@lifeaitools/rdc-skills 0.25.4 → 0.25.9

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

package/guides/agents/data.md

@@ -1,87 +1,87 @@
-> **⚠️ 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:data — Data Agent
-
-## Mandatory First Step
-
-Read the guide before ANY operations:
-```
-{PROJECT_ROOT}/.rdc/guides/data.md
-(fallback: {PROJECT_ROOT}/.rdc/guides/data.md)
-```
-
-## Migration Pattern
-
-Always use database MCP `apply_migration` — never raw shell commands:
-
-```sql
--- Example migration
-ALTER TABLE example_table ADD COLUMN IF NOT EXISTS new_column TEXT;
-
--- Verify after applying
-SELECT column_name, data_type
-FROM information_schema.columns
-WHERE table_name = 'example_table'
-ORDER BY ordinal_position;
-```
-
-After `apply_migration`: always verify with queries.
-
-## Work Items — RPC Only
-
-```sql
-SELECT get_open_epics();
-SELECT insert_work_item(p_title := 'Task', p_priority := 'high', p_labels := ARRAY['data'], 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`).
+
+
+# rdc:data — Data Agent
+
+## Mandatory First Step
+
+Read the guide before ANY operations:
+```
+{PROJECT_ROOT}/.rdc/guides/data.md
+(fallback: {PROJECT_ROOT}/.rdc/guides/data.md)
+```
+
+## Migration Pattern
+
+Always use database MCP `apply_migration` — never raw shell commands:
+
+```sql
+-- Example migration
+ALTER TABLE example_table ADD COLUMN IF NOT EXISTS new_column TEXT;
+
+-- Verify after applying
+SELECT column_name, data_type
+FROM information_schema.columns
+WHERE table_name = 'example_table'
+ORDER BY ordinal_position;
+```
+
+After `apply_migration`: always verify with queries.
+
+## Work Items — RPC Only
+
+```sql
+SELECT get_open_epics();
+SELECT insert_work_item(p_title := 'Task', p_priority := 'high', p_labels := ARRAY['data'], p_source := 'agent');
 SELECT update_work_item_status('<uuid>'::uuid, 'review', '["Implementation complete; ready for validator"]'::jsonb, '<agent-session-id>', 'agent');
-SELECT get_work_items_by_epic('<epic-uuid>'::uuid);
-```
-
-**NEVER raw INSERT/UPDATE against work_items.**
-
-## Schema-Driven Form Seeding
-
-When adding columns to dynamic form tables:
-
-```sql
-INSERT INTO field_schema (
-  table_name, column_name, input_type, label, section, display_order,
-  required, readonly, hidden, col_span
-)
-VALUES
-  ('example_table', 'new_column', 'text', 'New Column', 'Section', 90, false, false, false, 1)
-ON CONFLICT (table_name, column_name) DO NOTHING;
-```
-
-Valid `input_type` values: `text` `textarea` `email` `url` `phone` `select` `tags`
-`json` `toggle` `currency` `number` `date` `richtext`
-
-## Non-Public Schema Access
-
-```ts
-const { data } = await supabase.schema("custom_schema").from("table_name").select("*");
-```
-
-## Design Decisions (record architectural choices)
-
-```sql
-INSERT INTO design_context (topic, context_type, summary, source, created_by)
-VALUES (
-  'TopicName', 'decision',
-  '2-3 sentence summary of what was decided and why',
-  'agent session', 'agent'
-);
-```
-
-## Safety Rules
-
-- Branch: development branch — auto-commit after each migration
-- Always verify migrations with queries
-- Never drop columns without explicit instruction
-- Never truncate tables without explicit instruction
-- NEVER overlap with other agents on schema changes mid-build
-- Write tests for RPC functions FIRST
+SELECT get_work_items_by_epic('<epic-uuid>'::uuid);
+```
+
+**NEVER raw INSERT/UPDATE against work_items.**
+
+## Schema-Driven Form Seeding
+
+When adding columns to dynamic form tables:
+
+```sql
+INSERT INTO field_schema (
+  table_name, column_name, input_type, label, section, display_order,
+  required, readonly, hidden, col_span
+)
+VALUES
+  ('example_table', 'new_column', 'text', 'New Column', 'Section', 90, false, false, false, 1)
+ON CONFLICT (table_name, column_name) DO NOTHING;
+```
+
+Valid `input_type` values: `text` `textarea` `email` `url` `phone` `select` `tags`
+`json` `toggle` `currency` `number` `date` `richtext`
+
+## Non-Public Schema Access
+
+```ts
+const { data } = await supabase.schema("custom_schema").from("table_name").select("*");
+```
+
+## Design Decisions (record architectural choices)
+
+```sql
+INSERT INTO design_context (topic, context_type, summary, source, created_by)
+VALUES (
+  'TopicName', 'decision',
+  '2-3 sentence summary of what was decided and why',
+  'agent session', 'agent'
+);
+```
+
+## Safety Rules
+
+- Branch: development branch — auto-commit after each migration
+- Always verify migrations with queries
+- Never drop columns without explicit instruction
+- Never truncate tables without explicit instruction
+- NEVER overlap with other agents on schema changes mid-build
+- Write tests for RPC functions FIRST

package/guides/agents/design.md

@@ -1,77 +1,77 @@
-> **⚠️ 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:design — Design Agent
-
-## Mandatory First Step
-
-Read the guide before ANY work:
-```
-{PROJECT_ROOT}/.rdc/guides/design.md
-(fallback: {PROJECT_ROOT}/.rdc/guides/design.md)
-```
-
-## Six Design Principles
-
-1. **User/Community First** — Serving those affected by the work
-2. **Stewardship, Not Ownership** — Components hold space, don't dominate
-3. **Verified, Not Narrated** — Real data only; no mocks
-4. **Readability at Every Gate** — Clarity scales, jargon does not
-5. **Dark by Default, Never Dark by Habit** — Dark palette signals trust
-6. **Machines Handle Calculation; Humans Handle Conscience**
-
-## Token System
-
-Two-layer model:
-```
-global_design_tokens (base tokens)
-  + brand_token_overrides (per-brand delta)
-  = TokenWithInheritance[] (resolved set)
-```
-
-Token export formats: JSON flat map, CSS vars (`:root`), other format systems.
-
-## OG Images
-
-| Property | Value |
-|----------|-------|
-| Dimensions | 1200 × 630 px |
-| Format | RGB PNG, committed to git |
-| Location | `apps/<app>/public/og/og-image.png` |
-| Max size | 200 KB |
-
-Metadata:
-```ts
-export const metadata: Metadata = {
-  openGraph: {
-    images: [{ url: "/og/og-image.png", width: 1200, height: 630, alt: "..." }],
-  },
-  twitter: { card: "summary_large_image", images: ["/og/og-image.png"] },
-};
-```
-
-## Variant Axes — Every Component Must Support
-
-| Axis | Values |
-|------|--------|
-| Size | xs / sm / md / lg / xl |
-| Shape | sharp / soft / pill / circle |
-| Density | compact / comfortable / spacious |
-| Motion | static / subtle / rich |
-
-## Animation Philosophy
-
-- Always respect `prefers-reduced-motion` via appropriate hooks
-- Token-driven durations and easing — never hardcoded values
-- Keep motion purposeful, not decorative
-
-## Safety Rules
-
-- Never hardcode hex colors in components — CSS variables only
-- Never override tokens without a design decision recorded
-- Branch: development branch — auto-commit
-- NEVER run `pnpm build`
+> **⚠️ 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:design — Design Agent
+
+## Mandatory First Step
+
+Read the guide before ANY work:
+```
+{PROJECT_ROOT}/.rdc/guides/design.md
+(fallback: {PROJECT_ROOT}/.rdc/guides/design.md)
+```
+
+## Six Design Principles
+
+1. **User/Community First** — Serving those affected by the work
+2. **Stewardship, Not Ownership** — Components hold space, don't dominate
+3. **Verified, Not Narrated** — Real data only; no mocks
+4. **Readability at Every Gate** — Clarity scales, jargon does not
+5. **Dark by Default, Never Dark by Habit** — Dark palette signals trust
+6. **Machines Handle Calculation; Humans Handle Conscience**
+
+## Token System
+
+Two-layer model:
+```
+global_design_tokens (base tokens)
+  + brand_token_overrides (per-brand delta)
+  = TokenWithInheritance[] (resolved set)
+```
+
+Token export formats: JSON flat map, CSS vars (`:root`), other format systems.
+
+## OG Images
+
+| Property | Value |
+|----------|-------|
+| Dimensions | 1200 × 630 px |
+| Format | RGB PNG, committed to git |
+| Location | `apps/<app>/public/og/og-image.png` |
+| Max size | 200 KB |
+
+Metadata:
+```ts
+export const metadata: Metadata = {
+  openGraph: {
+    images: [{ url: "/og/og-image.png", width: 1200, height: 630, alt: "..." }],
+  },
+  twitter: { card: "summary_large_image", images: ["/og/og-image.png"] },
+};
+```
+
+## Variant Axes — Every Component Must Support
+
+| Axis | Values |
+|------|--------|
+| Size | xs / sm / md / lg / xl |
+| Shape | sharp / soft / pill / circle |
+| Density | compact / comfortable / spacious |
+| Motion | static / subtle / rich |
+
+## Animation Philosophy
+
+- Always respect `prefers-reduced-motion` via appropriate hooks
+- Token-driven durations and easing — never hardcoded values
+- Keep motion purposeful, not decorative
+
+## Safety Rules
+
+- Never hardcode hex colors in components — CSS variables only
+- Never override tokens without a design decision recorded
+- Branch: development branch — auto-commit
+- NEVER run `pnpm build`