@lifeaitools/rdc-skills 0.20.6 → 0.21.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rdc",
-  "version": "0.20.6",
+  "version": "0.21.0",
   "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",
@@ -30,6 +30,31 @@
     "codeflow_required": "bool — true if the skill MUST consult CodeFlow before acting on the codebase"
   },
   "skills_meta": {
+    "channel-formatter": {
+      "name": "channel-formatter",
+      "slash": "rdc:channel-formatter",
+      "category": "tooling",
+      "usage": "rdc:channel-formatter <channel> [content]",
+      "args": {
+        "positional": [
+          {
+            "name": "channel",
+            "required": false,
+            "description": "Target channel: linkedin | twitter | slack | email-ext | email-int | pitch-deck | word | pdf-report | web. Inferred from the request if omitted.",
+            "accepts": "string"
+          },
+          {
+            "name": "content",
+            "required": false,
+            "description": "Text/content to format. If omitted, formats content from the surrounding conversation.",
+            "accepts": "string"
+          }
+        ],
+        "flags": []
+      },
+      "requires": [],
+      "produces": []
+    },
     "brochure": {
       "name": "brochure",
       "slash": "rdc:brochure",

package/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## v0.21.0 — channel-formatter skill
+
+### Added
+- `rdc:channel-formatter` — channel-native output formatting for LinkedIn, Twitter/X,
+  Slack/Teams, Email (external/internal), Pitch Deck, Word/DOCX, PDF Report, and
+  Web/Landing Page. Ported from the `output-channel-formatter` claude.ai skill and
+  **inlined into a single self-contained SKILL.md** (no `references/` files) so it works
+  identically across the CLI plugin, the claude.ai web client (via `rdc_skill_get`, which
+  serves only SKILL.md), and Codex.
+
+---
+
 ## v0.9.38 — Clean-box npm install hardening
 
 ### Fixed

package/git-sha.json

@@ -1,3 +1,3 @@
 {
-  "sha": "148fb21305a527ef4a1d9b62949c1e0e2e02b042"
+  "sha": "e772addf91d7db4eff73fb14b43977f1aa578c26"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.20.6",
+  "version": "0.21.0",
   "description": "RDC typed-agent dispatch skill suite for Claude Code - plan, build, review, overnight builds",
   "keywords": [
     "claude-code",

package/skills/channel-formatter/SKILL.md

@@ -0,0 +1,299 @@
+---
+name: rdc:channel-formatter
+description: "Usage `rdc:channel-formatter <channel> [content]` — Apply precise, channel-native formatting to any output: LinkedIn, Twitter/X, Slack/Teams, Email (external/internal), Pitch Deck slides, Word/DOCX, PDF Report, and Web/Landing Page. Use EVERY TIME the user names an output channel/platform/document type, or asks to 'write a post', 'draft an email', 'format this for', 'make this a slide', 'send to LinkedIn', 'write a tweet', 'social media post', or 'reformat this for [channel]'. Each channel has its own Unicode strategy, emphasis system, length limits, and structure — never apply generic markdown to channel-specific output. Self-contained: all channel rules are inlined below (no external reference files)."
+---
+
+> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
+> The formatted deliverable IS the output. Produce the channel-correct text directly.
+> No tool-call narration, no raw markdown wrappers around channel output, no log dumps.
+
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first.
+
+> **Sandbox contract:** This skill honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. It writes no files and makes no external calls; under `RDC_TEST=1` behavior is unchanged (pure text transform).
+
+# Channel Formatter
+
+Format output precisely for the target channel. This skill is **self-contained** —
+every channel's rules are inlined below. Detect the channel, jump to its section,
+apply its rules exactly. Never apply generic markdown to a channel that doesn't render it.
+
+---
+
+## Channel Detection
+
+| If user says / context is...                          | Channel          | Go to section            |
+|-------------------------------------------------------|------------------|--------------------------|
+| LinkedIn, post, share on LinkedIn                     | LinkedIn         | [§ LinkedIn](#-linkedin) |
+| Tweet, Twitter, X post, thread                        | Twitter/X        | [§ Twitter / X](#-twitter--x) |
+| Slack, Teams, Discord, chat message                   | Slack/Teams      | [§ Slack / Teams](#-slack--teams) |
+| Email to client/investor/external, cold outreach      | Email (External) | [§ Email — External](#-email--external) |
+| Email to team, internal, Slack alternative            | Email (Internal) | [§ Email — Internal](#-email--internal) |
+| Pitch deck, slide, investor slide, one-pager slide    | Pitch Deck       | [§ Pitch Deck](#-pitch-deck) |
+| Word, DOCX, document, report, memo, letter, contract  | Word/DOCX        | [§ Word / DOCX](#-word--docx) |
+| PDF report, annual report, white paper                | PDF Report       | [§ PDF Report](#-pdf-report) |
+| Website, landing page, web copy                       | Web/Landing Page | [§ Web / Landing Page](#-web--landing-page) |
+| Artifact, JSX, React component, Claude artifact       | Artifact/JSX     | → use the `jsx-author` / `impeccable` skill instead |
+
+---
+
+## Workflow
+
+1. **Detect channel** from the request using the table above.
+2. **Jump to that channel's section** below and apply all rules exactly — do not rely on memory.
+3. **Never mix** markdown conventions across channels.
+4. If the channel is ambiguous, ask once: "Is this for [Channel A] or [Channel B]?"
+5. Produce the formatted output directly as the deliverable.
+
+## Hard Rules (all channels)
+
+- Never apply generic markdown (`##`, `**`, `-`, etc.) to LinkedIn, Email, Slack, or Twitter output.
+- Never use raw LaTeX in LinkedIn, Email, Slack, or Twitter — use Unicode math symbols.
+- Never use Word Styles notation in plain-text channels.
+- Always match the tone register of the channel (formal ≠ casual ≠ punchy).
+- For LIFEAI/PRT/RDC content, maintain REGEN-MODE voice unless Author-Mode is active.
+
+---
+
+## § LinkedIn
+
+### Core Principles
+- No markdown whatsoever — LinkedIn renders it as raw symbols.
+- Unicode is the ONLY way to achieve bold, italic, and special emphasis.
+- Emoticons are structural tools, not decoration — use them as bullet replacements and section markers.
+- Hook in line 1 — LinkedIn truncates after ~2 lines before "see more".
+- White space is content — single-line breaks create rhythm and readability.
+
+### Unicode Character Sets
+**Bold (Mathematical Bold)** — key terms, company names, headlines, CTAs:
+```
+𝗔𝗕𝗖𝗗𝗘𝗙𝗚𝗛𝗜𝗝𝗞𝗟𝗠𝗡𝗢𝗣𝗤𝗥𝗦𝗧𝗨𝗩𝗪𝗫𝗬𝗭
+𝗮𝗯𝗰𝗱𝗲𝗳𝗴𝗵𝗶𝗷𝗸𝗹𝗺𝗻𝗼𝗽𝗾𝗿𝘀𝘁𝘂𝘃𝘄𝘅𝘆𝘇
+𝟬𝟭𝟮𝟯𝟰𝟱𝟲𝟳𝟴𝟵
+```
+**Italic (Mathematical Italic)** — emphasis, quotes, sub-themes:
+```
+𝘈𝘉𝘊𝘋𝘌𝘍𝘎𝘏𝘐𝘑𝘒𝘓𝘔𝘕𝘖𝘗𝘘𝘙𝘚𝘛𝘜𝘝𝘞𝘟𝘠𝘡
+𝘢𝘣𝘤𝘥𝘦𝘧𝘨𝘩𝘪𝘫𝘬𝘭𝘮𝘯𝘰𝘱𝘲𝘳𝘴𝘵𝘶𝘷𝘸𝘹𝘺𝘻
+```
+**Bold Italic:**
+```
+𝘼𝘽𝘾𝘿𝙀𝙁𝙂𝙃𝙄𝙅𝙆𝙇𝙈𝙉𝙊𝙋𝙌𝙍𝙎𝙏𝙐𝙑𝙒𝙓𝙔𝙕
+𝙖𝙗𝙘𝙙𝙚𝙛𝙜𝙝𝙞𝙟𝙠𝙡𝙢𝙣𝙤𝙥𝙦𝙧𝙨𝙩𝙪𝙫𝙬𝙭𝙮𝙯
+```
+**Math / Equations** — Unicode symbols, never LaTeX: `× ÷ ± ≠ ≤ ≥ ≈ ∴ ∵ Σ Δ α β ∞ √ ² CO₂ H₂O → ← ⟺ % °`
+Example: instead of `E = mc^2` write `E = mc²`; instead of `\alpha_{PRT}` write `αPRT`.
+
+### Emoticons as Structure
+Section openers / bullets: 🔹 primary · 🔸 secondary · ▸ tertiary · ✅ result · ❌ contrast · ⚡ urgency · 🌱 regenerative (LIFEAI/PRT) · 💡 insight · 📌 takeaway · 🔑 key · 📊 data · 🏗️ development · 🤝 partnership · 💰 capital · 🌍 planetary.
+Dividers: `——————————————` · `▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬` · `· · · · · · · · · · · · · ·`
+
+### Post Structure
+**Standard (thought leadership):** hook line (no period, open loop) → blank → 3-6 short paragraphs (1-3 lines), emoticons as bullets → blank → insight/contrast line → blank → CTA (question/invitation) → blank → up to 3 hashtags.
+**Announcement:** bold Unicode headline → what it is (2 sentences) → 🔹×3 key points → why it matters → CTA/link → 1-2 tags.
+**Regenerative / LIFEAI (Dave voice):** manifesto opener (one line) → blank → problem with the old way (2-3 lines) → blank → 🌱 what we're building / how it differs / who it serves → blank → the stakes (one line) → blank → direct personal invitation → blank → `𝗗𝗮𝘃𝗲 𝗟𝗮𝗱𝗼𝘂𝗰𝗲𝘂𝗿 | LIFEAI | 𝘓𝘪𝘧𝘦 𝘣𝘦𝘧𝘰𝘳𝘦 𝘗𝘳𝘰𝘧𝘪𝘵𝘴` → `#RegenerativeCapital #PlaceRegeneration #LIFEAI`.
+
+### Length
+Thought leadership 900–1300 chars · Announcement 400–700 · Hot take 200–400 · Long-form native 1200–2000 words.
+
+### Do NOT
+❌ `**bold**` (literal asterisks) · ❌ `# Heading` (literal hash) · ❌ `-`/`•` bullets (use emoticons) · ❌ LaTeX · ❌ >5 hashtags · ❌ tagging people unless asked · ❌ walls of text (max 3 lines/paragraph).
+
+---
+
+## § Twitter / X
+
+### Core Principles
+- 280 characters hard limit per tweet. Hook is everything — first 5 words decide readership.
+- Threads are for depth; single tweets for punchy takes. No markdown renders — plain text only.
+- Minimal hashtags (1-2 max, only if genuinely searchable). End with a provocation/question when possible.
+
+### Character Counting
+- URLs always count as 23 chars (t.co). Media doesn't count. Line breaks = 1 char each. Leave a 10-15 char buffer — aim for 265 max.
+
+### Single Tweet Structure
+**Hot take:** provocative opener (≤10 words) → the turn/evidence (1-2 lines) → the landing.
+**Announcement:** bold claim first → why it matters (1 line) → link/CTA.
+**Regenerative (Dave):** manifesto line → old way vs new way → the invitation.
+
+### Thread Structure
+Tweet 1 = strongest hook (number `(1/7)` or use 🧵) → tweet 2 = context → tweets 3-n = one idea each → last tweet = recap + CTA/question. Each tweet must stand alone. Max 7-10 tweets — longer = blog post.
+
+### Hook Formulas
+Contrarian ("Most investors are wrong about regenerative land.") · Hard number ("We just unlocked $40M in stranded rural capital.") · Open loop ("Something broke in ESG investing. Here's what it missed:") · Bold declaration · Question · List tease ("3 things institutional capital gets wrong about place:").
+
+### Hashtags & Emoji
+Max 2 hashtags, end of tweet only, active communities only. Preferred LIFEAI tags: `#RegenerativeCapital #PlaceRegeneration #ImpactInvesting #RegenFinance`. Emoji 1-2 max as punctuation: 🌱 regen · 💰 capital · 🏗️ development · ⚡ urgency.
+
+### Do NOT
+❌ markdown · ❌ hashtag spam · ❌ "RT if you agree" · ❌ threads >10 tweets · ❌ passive openers ("I wanted to share…") · ❌ tagging without reason · ❌ ever exceed 280 chars (always count).
+
+---
+
+## § Slack / Teams
+
+### Core Principles
+- Brevity is respect (people read on their phone). One message = one thought. Use threads. Emoji are punctuation, not decoration.
+
+### Slack Markdown (actually renders)
+Bold `*bold*` · Italic `_italic_` · Strikethrough `~strike~` · Inline code `` `code` `` · Code block ```` ``` ```` · Blockquote `> text` · Bullets `• item`.
+Note: `**bold**` (double asterisk) does NOT render in Slack — use single `*bold*`.
+
+### Length
+Quick question 1-2 lines · Status update 3-5 lines (bullets if 3+ items) · Decision request 5-8 lines · anything longer → thread or doc link.
+
+### Structure by Type
+**Question:** `Quick question on [topic] — [one-sentence question]?`
+**Status update:** `*[Project]* update:` then `• Done: …` `• In progress: …` `• Blocked on: … — need [thing] from [person]`.
+**Decision needed:** `Need a call on [topic] by [time].` → `Context: …` → `Options: A) … B) …` → `My lean: …` → `[@person] — your call.`
+**Async FYI:** `FYI: [what happened] — no action needed. [link]`
+
+### Emoji as Punctuation
+✅ done/approved · ❌ no/blocked · 🔁 in progress · 👀 reviewing · 🙋 I'll take it · 📌 important · ⚡ urgent · 🤔 needs discussion · 💬 let's talk · 🔗 link follows.
+
+### Do NOT
+❌ walls of text (use a doc) · ❌ `**double asterisk bold**` · ❌ formal greetings ("Hi team, I hope everyone…") · ❌ passive asks ("Would anyone be able to…" → "Can you [name]…") · ❌ emoji overload (max 2-3) · ❌ cross-posting the same message.
+
+---
+
+## § Email — External
+
+### Core Principles
+- Plain prose, no markdown. Subject line determines open rate. First sentence justifies the email. One ask per email. Short paragraphs (2-4 sentences). Formal but human.
+
+### Structure
+`Subject:` → greeting (`Dear [First Name],`) → opening (1 sentence: context/connection) → body (¶1 reason, ¶2 value/evidence, ¶3 the one ask) → forward-looking closing line → sign-off, full name, title, org, 2-3 contact lines.
+
+### Subject Lines
+6-10 words; personalize. Cold: `[hook] — [value]` ("Regenerative capital for [Property]"). Follow-up: `Following up — [topic]`. Intro: `Introduction: [name] — [relevance]`. Request: `[Action] request — [context]`. Never use "Quick question" / "Checking in" / "Hope you're well" as a subject; never all caps.
+
+### Tone by Recipient
+Institutional/Family Office → formal, precise, lead with thesis + data · Foundation → warm, lead with impact · Government → neutral, process-oriented · Legal → exact, every claim qualified · Peer → professional, warmer · Media → newsworthy first.
+
+### Openers (use/adapt)
+"I'm reaching out because [specific reason tied to them]." · "We met at [event] — following up on [topic]." · "[Mutual contact] suggested I reach out regarding [topic]." Never open with "I hope this email finds you well." / "My name is X and I work at Y." / "I wanted to reach out to…".
+
+### Closings & Sign-offs
+"I'd welcome a 20-minute call at your convenience." / "Would you be open to a brief call this week or next?" Sign-offs: Respectfully / Yours sincerely (most formal) · Kind regards / Best regards (standard) · Warm regards (warm) · "In service of place," / "Regeneratively," (LIFEAI/Dave).
+LIFEAI signature: `Dave Ladouceur` / `Founder, LIFEAI | Place Regeneration Trust` / `dave@life.ai | lifeai.com` / `Life before Profits.`
+
+### Length
+Cold outreach 150–250 words · Follow-up 80–150 · Proposal intro 250–400 · Investor update 300–500.
+
+### Do NOT
+❌ markdown · ❌ walls of text · ❌ >1 ask · ❌ passive voice on the ask · ❌ sycophantic openers/closers · ❌ unspecified attachments.
+
+---
+
+## § Email — Internal
+
+### Core Principles
+- Short, direct, action-oriented. Bullets fine and often preferred. Scannable subject. One topic per email. No pleasantries unless warranted.
+
+### Structure
+`Subject: [Action word] — [Topic]` (e.g. "Decision needed — Supabase migration") → optional 1-line context → direct body (2-4 short paragraphs or bullets) → clear next step on its own line → casual sign-off (Thanks / Dave / —D).
+
+### Subject Prefixes (use consistently)
+`ACTION:` recipient must do something · `DECISION:` approval/choice needed · `FYI:` informational · `URGENT:` same-day · `QUESTION:` single question · `UPDATE:` status. Example: `ACTION: Review PRT NAV calc before Friday`.
+
+### Bullets & Tone
+One idea per bullet, max 1 line, lead with the verb (Review… / Confirm… / Send…), no sub-bullets unless necessary. Direct without blunt; no "per my last email" energy; emoji sparingly.
+
+### Length
+Quick update 3-6 lines · Task assignment 6-12 · Internal brief ≤12-20 (longer → a doc).
+
+### Do NOT
+❌ markdown · ❌ long preambles · ❌ CC-ing everyone · ❌ "as per my previous email" · ❌ formal sign-offs internally.
+
+---
+
+## § Pitch Deck
+
+### Core Principles
+- One slide, one job. Headline IS the message (a statement, not a label). 3 bullets max. No prose on slides (sentences → speaker notes). Visual-first language. Investor slides lead with thesis, support with evidence.
+
+### Slide Anatomy
+Headline (full sentence takeaway, 12-15 words) → visual/data area (chart/diagram/table) → ≤3 bullets (fragments, not sentences) → source/footnote if cited (small, bottom-right).
+
+### Headlines Are Assertions, Not Labels
+❌ "Market Opportunity" → ✅ "A $4T regenerative land market with no institutional gateway" · ❌ "Our Solution" → ✅ "PRT converts stranded land assets into regenerative yield" · ❌ "The Team" → ✅ "30 years of place-based development across 3 continents" · ❌ "Financial Returns" → ✅ "8–12% cash yield with embedded ecological appreciation".
+
+### Standard Deck Architecture (PRT/LIFEAI)
+1 Cover · 2 The Problem · 3 The Opportunity (market + gap) · 4 Our Solution · 5 How It Works (process diagram) · 6 Traction/Proof · 7 Market/TAM · 8 Business Model · 9 Financial Projections · 10 Capital Structure (A/B/C sleeves) · 11 The Team · 12 The Ask (amount, use of funds, timeline) · 13 Appendix.
+
+### Visual & Bullet Style
+Describe visuals explicitly, e.g. `[VISUAL: horizontal capital-stack diagram — Lane A Senior Secured $Xm 6% DAF | Lane B Mezz $Xm 9% Family Office | Lane C Equity $Xm carry GP]`. Bullets: fragments, no periods, lead with metric ("8–12% cash yield") or verb ("Converts stranded assets…"), max 8 words.
+Speaker notes: full conversational sentences expanding the slide — `[SPEAKER NOTE: …]`.
+Typography (for JSX/design): Headline 28-36pt bold · Bullets 18-22pt · Data labels 14-16pt accent · Source 10-11pt gray · Section label 11-12pt caps.
+
+### Do NOT
+❌ prose on slides · ❌ >3 bullets · ❌ label headlines · ❌ >2 font sizes in bullet area · ❌ generic stock-photo descriptions · ❌ animations unless requested.
+
+---
+
+## § Word / DOCX
+
+### Core Principles
+- All formatting via **Word Styles** (never raw bold alone). Heading hierarchy is semantic (Heading 1/2/3, not font size). Tables use Word Table Styles, not markdown. Equations via Equation Editor (OMML). Explicit page structure (section breaks, headers/footers, page numbers).
+
+### Style Hierarchy
+`Title` (one, top) · `Subtitle` · `Heading 1/2/3/4` · `Normal` / `Body Text` · `List Bullet` / `List Bullet 2` · `List Number` / `List Number 2` · `Quote`/`Block Text` · `Caption` · `Table Grid` · `Intense Quote` (callouts) · `Header`/`Footer`.
+
+### Document Types
+**Executive Report/White Paper:** Title + Subtitle → page break → H1 Executive Summary → H1 TOC (auto field) → page break → numbered H1/H2 sections with `Table Grid` tables + captions → H1 References (APA) → H1 Appendices.
+**Memo:** Title "MEMORANDUM" → bold-label TO/FROM/DATE/RE → rule → H2 Purpose / Background / Recommendation (List Bullet) → sign-off.
+**Investment/Deal Doc (PRT/RDC):** Title + Subtitle "Confidential | Prepared by LIFEAI | Date" → page break → H1 Executive Summary → H1 Investment Thesis (H2 Market Opportunity, H2 Regenerative Framework + Five Capitals `Table Grid`) → H1 Financial Structure (H2 Capital Stack tranche table, H2 NAV Architecture w/ Equation objects) → H1 Risk Framework (risk matrix) → H1 Governance → H1 Appendices.
+**Letter (formal):** sender block → date → recipient block → `Dear [Name],` → opening (purpose) → body → closing (next steps) → `Sincerely,` → signature.
+
+### Tables, Equations, Page Setup
+Tables: `Table Grid`, bold shaded header (`#F2F2F2`), left-align text / right-align numbers, `Caption` below ("Table X: …"). Equations: specify as Equation Editor objects, e.g. `[EQUATION OBJECT: αPRT = (regen_yield − WACC_conventional) + Σ(stewardship_delta)]` with caption. Page setup: Letter/A4, 1" margins, Calibri 11 / Times 12 body, 1.15–1.5 spacing, header (title left, page# right), footer (org left, date right), numbering from page 2.
+
+### Do NOT
+❌ manual bold instead of a Style for headings · ❌ tabs/spaces for indentation · ❌ `Shift+Enter` between paragraphs (use spacing) · ❌ markdown tables · ❌ inline LaTeX · ❌ >3 heading levels without justification.
+
+---
+
+## § PDF Report
+
+### Core Principles
+- Final, fixed, reader-facing. Structure non-negotiable: executive summary → body → references. All sections numbered; all tables/figures captioned. Formal prose (no bullets as primary structure). Page numbers, headers, footers required.
+
+### Structure
+Cover (title, type, org+logo, date | version | confidentiality) → Executive Summary (≤1 page: what it is, 3-5 findings, recommendations) → TOC (auto, clickable) → numbered body (1 Introduction/Context · 2-4 core · 5 Conclusions) → References (APA 7th, numbered) → Appendices (A, B, C…).
+Section numbering: hierarchical decimal, max 3 levels (1.1.1), never 4.
+
+### Tables, Figures, Equations
+Tables: title above (`Table X: …`), bold shaded header, `Source:` below if external, `Note:` if needed. Figures: caption below (`Figure X: …`), source, bracketed alt-text. Equations: labeled `(Equation 1)` with a `Where:` variable key.
+Typography: Georgia 11 / Garamond 12 body; H1 18 bold, H2 14 bold, H3 12 bold italic; 1.5 body spacing; 1.25" binding margin; page numbers bottom-center from page 2; footer `Org | Confidential | Date`.
+Confidentiality labels: `CONFIDENTIAL` · `CONFIDENTIAL — For Recipient Only` · `FOR DISCUSSION PURPOSES ONLY` · `NOT FOR DISTRIBUTION` · (none = public).
+
+### Do NOT
+❌ markdown in final content · ❌ unnumbered sections · ❌ tables without titles/sources · ❌ figures without captions · ❌ invented data (mark "Illustrative") · ❌ exec summaries over one page · ❌ incomplete citations.
+
+---
+
+## § Web / Landing Page
+
+### Core Principles
+- Scannable first, readable second. Above the fold is everything. One page = one conversion goal. SEO-aware without keyword stuffing. CTA appears at least twice (above fold + bottom). Mobile-first (short paragraphs/sentences).
+
+### Page Structure
+Hero (H1 value prop 6-10 words · subheadline 1-2 sentences · CTA button verb+object · optional hero media) → Social proof/trust bar → Problem (name the pain, 2-3 short paragraphs or 3 cards) → Solution (the shift; icon + headline + 1-2 sentences feature/benefit pairs) → How It Works (3-4 numbered steps, 1 sentence each) → Proof/Results (large number + short label: "340 acres restored") → CTA section (urgency headline + friction-reducer subtext + button) → Footer.
+
+### Headlines & Body
+H1 ≤8 words (benefit, not feature, active voice, power words: transform/unlock/regenerate/built/proven) · H2 ≤12 · H3 ≤6. Body: paragraphs ≤3 sentences/50 words, sentences ≤20 words, second person ("you/your"), grade 8-10 reading level.
+LIFEAI/PRT examples: H1 "The Capital Stack for Regenerative Land" · H2 "How PRT Turns Stranded Assets Into Living Investments" · H3 "Place Readiness" / "Covenant-Protected Yield" / "Verified Impact".
+
+### CTA & SEO
+CTA copy: verb + specific object ("Book Your 20-Minute Call", "See the Capital Structure", "Download the Investment Brief") — never "Submit"/"Click here"/"Learn more". SEO: primary keyword in H1 + first paragraph, secondary in H2s/body naturally, meta title 50-60 chars, meta description 150-160 chars, descriptive alt text on all images.
+
+### Do NOT
+❌ paragraphs >3 sentences above the fold · ❌ passive-voice CTAs · ❌ jargon without translation · ❌ carousels/sliders above the fold · ❌ >2 CTAs per section · ❌ generic headlines ("Welcome to Our Website") · ❌ markdown in final web copy (deliver clean prose with labeled sections).
+
+---
+
+## Provenance
+
+Ported into rdc-skills from the `output-channel-formatter` claude.ai skill (frontend-design-skills pack).
+Originally a multi-file skill (SKILL.md + `references/*.md`); inlined into this single self-contained
+SKILL.md so it works identically across the CLI plugin, the claude.ai web client (via `rdc_skill_get`),
+and Codex — the rdc-skills MCP serves only SKILL.md, so all channel rules must live here.