[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FPRJPMZ640WWGFQZ11TFG":3,"skill-same:01M78FPRJPMZ640WWGFQZ11TFG":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M78FPRJPMZ640WWGFQZ11TFG","officecli-pitch-deck",null,"Use this skill when the user is building a fundraising \u002F investor pitch deck — seed, Series A \u002F B \u002F C, convertible note, SAFE round, strategic raise. Trigger on: 'pitch deck', 'investor deck', 'Series A deck', 'Series B deck', 'Series C deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet presentation'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate). DO NOT invoke for a generic board review, sales deck, all-hands, or product launch — route those to officecli-pptx base.","shixianghua\u002FOfficeCLI-Enhanced","shixianghua","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F185889825?v=4","01M78FMF4JT83THYX5CF50WP85","01M78FMF5Q3AG5XA5A6KS5TQZK",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fshixianghua\u002FOfficeCLI-Enhanced\u002Fblob\u002Fmain\u002Fskills\u002Fofficecli-pitch-deck\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: officecli-pitch-deck\ndescription: \"Use this skill when the user is building a fundraising \u002F investor pitch deck — seed, Series A \u002F B \u002F C, convertible note, SAFE round, strategic raise. Trigger on: 'pitch deck', 'investor deck', 'Series A deck', 'Series B deck', 'Series C deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet presentation'. Output is a single .pptx. This skill is a scene layer on top of officecli-pptx — inherits every pptx v2 rule (visual floor, grid, palettes, connector canon, Delivery Gate). DO NOT invoke for a generic board review, sales deck, all-hands, or product launch — route those to officecli-pptx base.\"\n---\n\n# OfficeCLI Pitch Deck Skill\n\n**This skill is a scene layer on top of `officecli-pptx`.** Every pptx hard rule — visual delivery floor (title ≥ 36pt \u002F body ≥ 18pt \u002F title ≥ 2× body), 12-column grid on 33.87×19.05cm, 4 canonical palettes, chart-choice decision table, connector canon (`shape` \u002F `from` \u002F `to` \u002F `tailEnd=triangle`), shell escape, resident + batch, Delivery Gate 1–5a — is inherited, not re-taught. This file adds only what **fundraising** needs on top: stage diagnosis (A \u002F B \u002F C), 5 赛道 arc templates, 10 key-slide recipes (cover \u002F problem \u002F solution \u002F market \u002F product \u002F model \u002F traction \u002F team \u002F financials \u002F ask), pitch-specific numbers convention, a VC ship-check, and a pitch-specific fresh-eyes Gate 6.\n\nWhen the pptx base rules cover it, the text here says `→ see pptx v2 §X`. Read `skills\u002Fofficecli-pptx\u002FSKILL.md` first if you have not.\n\n## Setup\n\nIf `officecli` is missing:\n\n- **macOS \u002F Linux**: `curl -fsSL https:\u002F\u002Fd.officecli.ai\u002Finstall.sh | bash`\n- **Windows (PowerShell)**: `irm https:\u002F\u002Fd.officecli.ai\u002Finstall.ps1 | iex`\n\nVerify with `officecli --version` (open a new terminal if PATH hasn't picked up). If install fails, download a binary from https:\u002F\u002Fgithub.com\u002FiOfficeAI\u002FOfficeCLI\u002Freleases.\n\n## ⚠️ Help-First Rule\n\n**This skill teaches what a fundraising deck requires, not every command flag.** When a prop name, enum value, or preset is uncertain, consult help BEFORE guessing.\n\n```bash\nofficecli help pptx                          # All pptx elements\nofficecli help pptx \u003Celement>                # Full schema (e.g. chart, shape, connector, picture)\nofficecli help pptx \u003Celement> --json         # Machine-readable\n```\n\nHelp reflects the installed CLI version. When this skill and help disagree, **help wins.** Every `--prop X=` in this file has been grep-verified against `officecli help pptx \u003Celement>` — if help adds \u002F renames a prop in a later version, trust help.\n\n## Mental Model & Inheritance\n\n**Inherits pptx v2.** You should have read `skills\u002Fofficecli-pptx\u002FSKILL.md` first. This skill assumes you know how to: add slides + shapes + charts + connectors; address by `@name=` \u002F `@id=`; quote paths; use `batch` heredocs; write `--prop tailEnd=triangle` on every flow connector; and run the 5-gate Delivery Gate. If any of those are unfamiliar, open a pptx v2 session before continuing.\n\n## Shell & Execution Discipline\n\n**Shell quoting, incremental execution, `$FILE` convention** → see pptx v2 §Shell & Execution Discipline. Same rules verbatim — quote `[N]` paths, single-quote values containing `$` (including `$35M`, `$1.2B TAM` in a cover or ask slide), never hand-write `\\$ \\t \\n` in executable examples, one command at a time. Examples below use `$FILE` (`FILE=\"deck.pptx\"`).\n\n**Single-quote every shape text containing `$`.** `--prop text=\"Series B · $35M\"` (double quotes) is WRONG — zsh expands `$35M` → empty, deck renders `Series B · M` silently. `--prop text='Series B · $35M'` (single quotes) is right. This is the #1 pitch-deck shell-escape failure mode (`$35M`, `$18M ARR`, `$1.2B TAM` appear on cover\u002Fask\u002Ffinancials\u002Fmilestones). Gate 2 cannot detect a stripped `$35M` — no residue. Gate 2b catches common strip patterns; single-quoting PREVENTS them.\n\n## What \"pitch deck\" means here (identity)\n\nA pitch deck is a pptx with a **fundraising layer** on top: VC-oriented narrative arc, verifiable metrics, stage-appropriate data density, founder-credibility surface. Slides are consumed at ~3 seconds per slide in a live room — the pptx v2 rule. Pitch decks add a second constraint on top: **every slide carries one investable proposition**. If a slide is \"interesting background\" that doesn't move the ask forward, cut it. VCs will not. The base pptx rules still apply; pitch decks add six deltas:\n\n1. **Stage determines everything.** Series A \u002F B \u002F C each dictates slide count, narrative weight, which metrics are must-haves, and tolerance for unit-econ sophistication. A Series A deck with 6 pages of CAC\u002FLTV math reads as over-packaged; a Series B deck missing unit econ reads as incomplete. Pick the stage first — everything downstream follows.\n2. **Narrative arc beats feature dump.** 10 essential slides in a fixed order: cover → problem → solution → market → product → model → traction → team → financials → ask. Out of order = VCs disengage.\n3. **Numbers are a contract.** TAM\u002FSAM\u002FSOM must be clean three-layer; CAC\u002FLTV must have a payback line; ARR ≠ revenue; Use-of-Funds must be a four-bucket pie. Sloppy numbers = round dies.\n4. **Team slide carries prior companies.** Avatar grid alone reads as a student project. Add prior-company logos \u002F names + one-line role. Without this, first-time founders look exactly like first-time founders.\n5. **Traction chart y-axis starts at 0.** A \"hockey stick\" starting at `y_min = 80% of current` is a visual lie — VCs who have seen 10,000 decks spot it in \u003C 2 seconds.\n6. **The ask is a slide, not a footnote.** `$XX M` hero + four-bucket Use-of-Funds + runway length. \"We're raising some money\" is not an ask.\n\n### Reverse handoff — when to go BACK to pptx base\n\nStay in **pptx v2 base** for board reviews, all-hands, sales decks, product launches, training decks — anything not tied to raising capital. Use **this skill** only when: (a) the user mentions a specific round (seed \u002F Series A \u002F B \u002F C) or a VC meeting, AND (b) the deck needs at least 4 of {problem, traction, team with credentials, Use-of-Funds, stage-appropriate unit econ, financial projections}.\n\nIf the user says \"fundraising deck\" but the context is a corporate BU quarterly ask, that is a board review. Route to pptx v2 Recipe (d) 10-slide blueprint. If the user says \"board review\" but the context is a small company raising a bridge round, route here.\n\n## Series A \u002F B \u002F C stage diagnosis (decision tool)\n\n**Read this before writing a single command.** Pick the row that matches the user's description — everything downstream (slide count, which metrics, which recipes, what the team slide must show) derives from this one call.\n\n| Stage | Revenue band | Team | Slide count | Dominant narrative (weight) | Must-have data | Common red flag |\n|---|---|---|---|---|---|---|\n| **Seed** | $0 – $1M ARR (often pre-rev) | 2 – 8 FTE | 10 – 12 | Problem (30%) + Solution (25%) + Team (15%) + Market (15%) + Traction (15%) | Founder-market fit story; 1 – 2 design-partner \u002F pilot logos; top-down TAM ok | Over-claiming traction (10 customers = \"market proven\") |\n| **Series A** | $1 – $5M ARR | 10 – 25 FTE | 12 – 16 | Problem (20%) + Solution (20%) + **Market \"why now\"** (15%) + Product (15%) + Traction (20%) + Team (10%) | PMF proof (NRR > 110%, low churn), bottom-up TAM\u002FSAM, pipeline \u002F pilots converted | Bottom-up TAM feels fabricated; CAC not yet meaningful but shown anyway |\n| **Series B** | $5 – $30M ARR | 30 – 100 FTE | 18 – 22 | **Traction + Unit econ (30%)** + Market + Product + Team + Financials (ask) | ARR curve starting at 0; NRR, CAC, LTV, payback (\u003C 18 mo ideal); cohort retention; logo wall | No unit-econ slide; CAC payback > 24mo without explanation; Use-of-Funds missing % |\n| **Series C** | $30M+ ARR | 100+ FTE | 20 – 24 | **Financials + Scale + Moat (40%)** + Market expansion + Team depth | Multi-year GAAP, rule-of-40, GM trajectory, international expansion plan, defensibility | No moat slide; revenue growth without margin story; team slide has no prior CEO \u002F CFO |\n| **Bridge \u002F SAFE** | any | any | 8 – 10 | **Specific bridge reason** + runway math + commitments | Prior round context; specific milestone the bridge funds; committed investor amount | Treating a bridge like a Series A — too many slides dilutes the ask |\n\n**Decision procedure.** From one or two user sentences (\"Series B, $18M ARR, 120 customers, $35M raise\"), pick exactly one stage row. All later choices in this skill reference your stage: which 赛道 template to pull, which recipes are mandatory vs optional, and which Delivery Gate 6 checks fire.\n\n**Corner cases.** Bridge rounds & convertibles between A → B are closer to A or B depending on whether the bridge milestone is \"finish PMF\" (A shape) or \"hit unit-econ target\" (B shape). \"Extension\" rounds at the same stage reuse the earlier stage's skeleton and add a one-slide \"progress since last round\" update.\n\n**Non-SaaS stage overrides.** The ARR \u002F unit-econ shape of Series B fits SaaS. For other verticals, substitute revenue band + unit-econ equivalent + Gate 6.3 grep:\n\n| Vertical | Revenue \"band\" at Series B | \"Unit econ\" equivalent | Gate 6.3 substitute |\n|---|---|---|---|\n| **Bio \u002F Clinical-stage** | pre-rev, 20–60 FTE | burn rate + runway to next milestone (IND \u002F Ph1 readout \u002F BLA) | `shape:contains(\"ORR\")` OR `contains(\"Pipeline\")` OR `contains(\"BLA\")` OR `contains(\"runway\")` ≥ 1 |\n| **Deep Tech \u002F Frontier** | pre-rev or early pilot rev | technical milestones + TRL level + benchmark vs SoTA | `shape:contains(\"TRL\")` OR `contains(\"benchmark\")` ≥ 1 |\n| **Marketplace \u002F Network** | GMV $10–100M | take rate + cohort retention + liquidity | `shape:contains(\"GMV\")` + `contains(\"take rate\")` ≥ 1 |\n| **Consumer hardware** | $2–15M revenue (shipped units) | contribution margin + repeat rate + blended CAC | `shape:contains(\"repeat\")` OR `contains(\"contribution\")` ≥ 1 |\n\nSubstitute the analogue grep when running Gate 6.3 on these verticals. False WARN on SaaS CAC\u002FLTV = expected; real concern = vertical-specific analogue present. Bio Series B decks especially: burn + runway-to-milestone IS the \"unit econ\" story.\n\n## 赛道 arc templates (5 families)\n\n5 mainstream verticals. Each one has different slide weights because what VCs require as proof-of-concept differs. Pick the vertical row; the slide skeleton is a copy-able starting point. Slide counts assume the matching stage row above.\n\n### (1) B2B SaaS \u002F Enterprise software\n\nCanonical arc — the template most of VC muscle memory is built on. Series B example (20 slides): cover · TL;DR · problem · problem evidence · solution · product loop · market TAM\u002FSAM\u002FSOM · **unit economics (CAC \u002F LTV \u002F payback \u002F GM)** · ARR trajectory · retention cohort · logo wall · team · competitors · financials 4-year · ask. Must-have: unit-econ slide from Series A onward; logo wall from Series B onward.\n\n### (2) Consumer (B2C app \u002F consumer hardware \u002F D2C)\n\nNarrative-driven. Early-stage decks lean on **product-experience screenshots + founding story + \"why now\"** market timing; lighter on unit econ (which are usually weaker than SaaS). Series A example (14 slides): cover · hook (30-second product demo or 1-line vision) · problem (lived experience) · solution (product shots) · product-experience flow · \"why now\" market window · pre-order \u002F crowdfunding \u002F early-sales evidence · retention \u002F engagement (DAU, D30) · market (top-down ok if bottom-up unreliable) · competitive positioning · founder story + team · press \u002F endorsements · financials · ask. Must-have: product visuals on ≥ 3 slides; \"why now\" slide (window justification); engagement metric not just revenue.\n\n### (3) Deep Tech \u002F Frontier tech (AI foundation models, quantum, climate hardware, robotics)\n\nTechnology credibility is the sell. Pre-revenue deep tech replaces \"traction\" with **technical milestones + defensibility**. Series B example (22 slides): cover · thesis (one-line \"what changes if this works\") · problem (current state of art) · solution (technical approach) · **technology architecture** · benchmarks vs SoTA · pipeline \u002F TRL levels · market (long-tail) · business model · early commercial traction (pilots, LOIs) · IP \u002F patents · team (usually PhD \u002F ex-FAANG-research) · partners · financials · ask. Must-have: benchmark slide; IP slide; team slide dense with PhDs \u002F prior-lab names.\n\n### (4) Marketplace \u002F Network business (two-sided platform, social, commerce)\n\nLiquidity is the metric. Replace \"unit econ\" with **GMV + take rate + cohort retention + supply \u002F demand balance**. Series A example (15 slides): cover · problem (friction in current supply-demand) · solution · product demo (both sides) · network effects diagram · early liquidity (first-week GMV, time-to-match) · cohort retention · geographic \u002F category expansion plan · competitive positioning vs incumbents · take-rate model · team · financials · ask. Must-have: liquidity metric slide; cohort retention chart; network-effect diagram.\n\n### (5) Bio \u002F Life sciences \u002F Healthtech\n\nRegulatory pipeline IS the business. Replace \"product roadmap\" with **clinical pipeline + regulatory path + scientific evidence**. Series B example (22 slides): cover · unmet medical need · scientific rationale (mechanism of action) · preclinical \u002F clinical data (ORR, safety, endpoints) · **pipeline chart** (candidates × stages × dates) · differentiation vs standard of care · IP \u002F exclusivity · regulatory strategy (IND, BTD, fast-track) · market (prevalence × pricing) · commercial strategy (orphan \u002F specialty \u002F biosimilar) · partnerships \u002F collaborations · team (CSO \u002F CMO with prior FDA wins) · financials (burn to next milestone) · ask. Must-have: pipeline chart; clinical data slide; team slide with prior regulatory wins.\n\n**Cross-vertical rule.** You can mix elements across templates, but never drop a must-have from your primary vertical. A SaaS deck missing unit econ, a bio deck missing a pipeline chart, a marketplace deck missing a liquidity metric — each is an instant VC disqualification.\n\n## Slide Patterns (layout canon)\n\nPatterns are **layout geometry**; recipes below are **narrative intent**. A slide picks one pattern for its visual shape (6 canonical ones below) and one recipe for what it argues (cover \u002F problem \u002F traction \u002F ...). Multiple recipes can share one pattern — Problem \u002F Why-Now \u002F Traction-callout all lean on the 3-stat row (C.2). Pick the pattern first, then fill it with recipe content.\n\n**Speaker notes rule.** Every content slide (non-cover, non-closing) MUST carry speaker notes via `officecli add \"$FILE\" \u002Fslide[N] --type notes --prop text='…'`. Missing notes = not shippable — inherits pptx v2 §Hard rules (H7). Run `officecli help pptx notes` to confirm prop names before building.\n\n**Pattern reuse discipline.** Never run the same pattern on two consecutive slides — even with different data, two identical geometries in a row read as a template loop. Alternate C.2 with C.4 or C.5b to break rhythm.\n\n**Vertical centering.** When a slide carries fewer elements than the pattern's maximum, nudge y-positions down 2–3cm to center the visual weight. Tables below assume full content.\n\n### C.1 Title \u002F Cover (dark gradient)\n\n3–4 text shapes on a gradient fill. Slide 1 in every deck.\n\n```\n+----------------------------------+\n|                                  |\n|          TITLE (centered)        |\n|          tagline                 |\n|                                  |\n|   round · amount · date          |\n|  ________________________        |  \u003C- thin brand band\n+----------------------------------+\n```\n\n| Element | X | Y | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Title | 2cm | 5cm | 29.87cm | 4cm | serif bold, ≥ 36pt (44 typical) |\n| Tagline | 2cm | 10cm | 29.87cm | 2cm | sans 18–22pt |\n| Meta (round · $ · date) | 2cm | 13cm | 29.87cm | 1.5cm | sans 12–16pt |\n\n**Use this when** the slide is the first one (Cover recipe 1) — 3-second identity grab. Background is a 180° linear gradient between two dark palette shades (e.g. Professional Navy `1E2761 → 0D1F35`). If the title wraps to 2 lines, **add height (4cm → 5cm), never drop font below 36pt** — sub-36pt on a pitch cover reads as timid regardless of content. Transition: fade.\n\n### C.2 3-Stat callout row\n\nTitle + 3 big-number \u002F label pairs across. The default for Problem \u002F Why-Now \u002F Traction-callout slides.\n\n```\n+----------------------------------+\n|  Title                           |\n|                                  |\n|   73%      12hr      $4.2B       |\n|   label    label     label       |\n|   source   source    source      |\n+----------------------------------+\n```\n\n| Element | X | Y | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Title | 1.5cm | 1cm | 30.87cm | 3cm | serif bold ≥ 36pt |\n| Stat 1 number | 2cm | 5cm | 9cm | 4cm | serif bold 60–64pt |\n| Stat 1 label | 2cm | 9.5cm | 9cm | 2cm | sans ≥ 16pt (H4 floor) |\n| Stat 2 number \u002F label | 12.5cm | (same) | 9cm | (same) | (same) |\n| Stat 3 number \u002F label | 23cm | (same) | 9cm | (same) | (same) |\n\n**Use this when** you have 2–3 anchoring numbers and the story is \"three facts argue the point\" — Problem, Why-Now, Market-callout, single-row Traction. Labels ≥ 16pt is the H4 floor (sub-label exception); a number without a label reads as bravado, so never drop labels to 12–14pt to fit more text.\n\n### C.3 4-Stat callout row\n\nSame geometry as C.2 but 4 columns. Numbers 60pt, width 7cm each.\n\n```\n+-------------------------------------+\n|  Title                              |\n|                                     |\n|  73%   12hr   $9M   4.2x            |\n|  lbl   lbl    lbl   lbl             |\n+-------------------------------------+\n```\n\n| Element | X positions | Y | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Title | 1.5cm | 1cm | 30.87cm | 3cm | serif bold 36pt |\n| Stat numbers | 1.5 \u002F 9.5 \u002F 17.5 \u002F 25.5cm | 5cm | 7cm | 4cm | serif bold 60pt |\n| Stat labels | (same X) | 9.5cm | 7cm | 2cm | sans ≥ 16pt |\n\n**Use this when** exactly 4 parallel metrics tell the story and 3 feels under-counted. Prefer C.2 if in doubt — 4 always feels tighter than 3, and wrap risk is real.\n\n> **Wrap warning.** At 60pt in 7cm width, dollar patterns with both `$` and `.` fail: `$9.4M` is 5 glyphs but the wide `$` and `.` in a serif bold make it wrap to 2 lines and destroy the callout. Safe dollar shapes at 60pt\u002F7cm: `$9M`, `$96B`, `$4K` (3–4 chars). Non-dollar shapes: `340%`, `4.2x`, `12.3` safe up to 5 chars. Values ≥ 6 chars (`197min`, `3 Days`) will wrap — either (a) drop font to 44–48pt, (b) abbreviate (`197m`, `$9M`), or (c) shift to C.2 (9cm per stat). Single tokens only, no internal spaces.\n\n### C.4 Chart + Context (chart left, stats right)\n\nChart takes left 55%, 2–3 stacked callouts on the right. The default for Traction \u002F Financials \u002F Market-sizing-with-context.\n\n```\n+-------------------------------------+\n|  Title                              |\n|                                     |\n|  +---------------+   +--------+     |\n|  |               |   | Stat 1 |     |\n|  |    chart      |   +--------+     |\n|  |               |   | Stat 2 |     |\n|  +---------------+   +--------+     |\n+-------------------------------------+\n```\n\n| Element | X | Y | Width | Height |\n|---|---|---|---|---|\n| Title | 2cm | 1cm | 29.87cm | 3cm |\n| Chart | 2cm | 4cm | 17cm | 13cm |\n| Stats column | 21cm | 4cm+ | 11cm | 2.5cm number + 1.5cm label (~3.7cm per pair) |\n\nSub-labels ≥ 16pt (H4 floor). For 5 stats stacked, drop number size to 44pt; 6+ stats means pick a different pattern. Post-batch for column\u002Fbar charts: `officecli set \"$FILE\" \"\u002Fslide[N]\u002Fchart[1]\" --prop gap=80` to tighten bar spacing.\n\n**Use this when** one primary chart drives the story and 2–3 numeric anchors reinforce it — Traction (ARR curve + current ARR + YoY + NRR), Financials (4-year column chart + assumption callouts), Market (bar chart + SOM \u002F CAGR \u002F methodology).\n\n### C.5 Icon-in-circle grid (3-row vertical)\n\n3 vertical rows, each = circle icon on the left + title + 1-line description.\n\n```\n+---------------------------------------+\n|  Title                                |\n|                                       |\n|  (o)  Label one                       |\n|       description one                 |\n|                                       |\n|  (o)  Label two                       |\n|       description two                 |\n|                                       |\n|  (o)  Label three                     |\n|       description three               |\n+---------------------------------------+\n```\n\n| Element | X | Y positions | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Icon circle | 2cm | 4.5 \u002F 8.5 \u002F 12.5cm | 2.5cm | 2.5cm | ellipse, accent fill |\n| Label | 5.5cm | (icon Y + 0) | 25cm | 1.2cm | sans bold 18pt |\n| Description | 5.5cm | (icon Y + 1.3cm) | 25cm | 1.8cm | sans ≥ 16pt (H4 floor), muted |\n\n**Use this when** you have 3 short vertical points that benefit from a visual anchor per row — Solution mechanism, Value pillars, Product loop. Choose C.5b (2×2 grid) when items are parallel and you have exactly 4; choose a horizontal 5-across variant when icons should read side-by-side (e.g. 5-step process).\n\n### C.5b 2×2 Feature grid (4 parallel items)\n\n4 rounded cards, 2 columns × 2 rows. Use when you have exactly 4 parallel items (product pillars, service types, feature quadrants).\n\n```\n+-----------------------------+\n|  Title                      |\n|                             |\n|  +---------+  +---------+   |\n|  | (o) T1  |  | (o) T2  |   |\n|  | body    |  | body    |   |\n|  +---------+  +---------+   |\n|  +---------+  +---------+   |\n|  | (o) T3  |  | (o) T4  |   |\n|  | body    |  | body    |   |\n|  +---------+  +---------+   |\n+-----------------------------+\n```\n\n| Element | X | Y | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Slide title | 2cm | 1cm | 29.87cm | 2.5cm | serif bold 32pt |\n| Card 1 bg (top-left) | 1.5cm | 4cm | 14.5cm | 7cm | roundRect |\n| Card 2 bg (top-right) | 17.5cm | 4cm | 14.5cm | 7cm | roundRect |\n| Card 3 bg (bottom-left) | 1.5cm | 12cm | 14.5cm | 7cm | roundRect |\n| Card 4 bg (bottom-right) | 17.5cm | 12cm | 14.5cm | 7cm | roundRect |\n| Icon ellipse (each card) | card_x + 0.5cm | card_y + 0.5cm | 2cm | 2cm | — |\n| Card title (each) | card_x + 3.2cm | card_y + 0.6cm | 10.5cm | 1.8cm | sans bold 16pt |\n| Card body (each) | card_x + 0.5cm | card_y + 3cm | 13cm | 3.5cm | sans ≥ 16pt (H4 floor) |\n\n**Use this when** you have exactly 4 parallel items and the eye should land on each equally — 4 product pillars, 4 service tiers, 4 stakeholder types. 3 items feel lonely in a 2×2; 5+ items break the grid — go to a 3×2 (see pptx v2 §(d) grid math) or C.5 row pattern.\n\n> **Z-order canon (critical).** Each card's `roundRect` background must be added immediately before that card's icon \u002F title \u002F body shapes in the batch JSON — pptx paints in insertion order, so a background added after its text paints over and hides the text. When building with `officecli batch`, follow the per-card sequence `bg → ellipse → title → body` strictly. Pattern and z-order details → see pptx v2 §Recipe (c) z-order canon; reuse grid math from pptx v2 §(d) for non-2×2 counts.\n\n**Dark-background variant.** Change card fill from `F0F4F8` (light) to a lighter-dark shade like `1A2540` and bump body text to `FFFFFF` \u002F `E8E8E8`. Palette variables (e.g. `$MUTED`) do NOT expand inside single-quoted heredocs — write the literal hex (`64748B`) in the JSON.\n\n---\n\n## Key-slide recipes (10 essentials)\n\nThe 10 slides every pitch deck carries. Each recipe below gives: **visual outcome** (what the slide looks like from 3m away) + **runnable block** (≤ 18 lines) + **QA one-liner**. All recipes inherit pptx v2 palettes, grid math, type hierarchy, and `--prop tailEnd=triangle` on every connector. Recipes reference the Slide Patterns above: Cover reuses C.1; Problem \u002F Why-Now reuse C.2; Traction \u002F Financials reuse C.4; Feature \u002F pillar slides reuse C.5b. `$FILE` is your deck file.\n\n**Long-title wrap rule.** A 36pt+ title that wraps to 2 lines: add `height` (e.g. 2cm → 3.5cm) — never drop the font below 36pt. Titles \u003C 36pt on a pitch deck read as timid regardless of content.\n\n> **Chart `series1.color=` on `add` works** (applies to every chart recipe below). Passing `--prop series1.color=` (or `series2.color=`, …) on chart `add` applies the series color and exits 0. Verify with a readback if you like: `officecli get \"$FILE\" \"\u002Fslide[N]\u002Fchart[1]\u002Fseries[1]\" --json | jq '.data.results[0].format.color'`.\n\n### (1) Cover slide — company · tagline · round · date\n\n**Visual outcome.** Dark navy fill, centered 44pt company name, 20pt one-line tagline underneath, small 16pt meta line at the bottom with round + amount + date. Thin brand band at the very bottom (0.5cm high) in the accent color.\n\n```bash\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=1E2761\nofficecli add \"$FILE\" \"\u002Fslide[1]\" --type shape --prop name=BrandBand \\\n  --prop geometry=rect --prop fill=CADCFC \\\n  --prop x=0cm --prop y=18.5cm --prop width=33.87cm --prop height=0.55cm\nofficecli add \"$FILE\" \"\u002Fslide[1]\" --type shape --prop name=CoverTitle --prop text=\"Acme DevOps\" \\\n  --prop x=2cm --prop y=7cm --prop width=29.87cm --prop height=3cm \\\n  --prop font=Georgia --prop size=44 --prop bold=true --prop color=FFFFFF --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[1]\" --type shape --prop name=Tagline --prop text=\"Kubernetes observability, built for production at scale\" \\\n  --prop x=2cm --prop y=10.5cm --prop width=29.87cm --prop height=1.5cm \\\n  --prop font=Calibri --prop size=20 --prop color=CADCFC --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[1]\" --type shape --prop name=CoverMeta --prop text='Series B · $35M · April 2026' \\\n  --prop x=2cm --prop y=15cm --prop width=29.87cm --prop height=1.2cm \\\n  --prop font=Calibri --prop size=16 --prop color=FFFFFF --prop align=center --prop fill=none\n```\n\n**QA.** Cover has 4 discrete elements (brand band + title + tagline + meta). 80%-whitespace covers fail the pptx \"cover ≥ 60% filled\" floor.\n\n**Consumer variant (3-second grab).** Consumer decks (B2C app \u002F hardware \u002F D2C) should add a single dominant motif — hero product shot, oversized company name (60–96pt), or symbolic mark (crescent moon \u002F abstract geometric). Replace the 44pt title with an 80–96pt name + one motif shape (`--type shape --prop geometry=ellipse --prop fill=\u003Caccent>` for an abstract mark, or `picture` at ~40% of slide for a product hero). Keep tagline + round + date identical. SaaS \u002F B2B may skip — the typographic-only cover is sufficient.\n\n### (2) Problem slide — industry pain in 1 sentence + 3 data cards\n\n**Visual outcome.** 36pt title stating the pain (not \"The Problem\"). Below, three equal-width data cards across the slide: each a giant number (40pt) + one-line qualifier (16pt) + source footnote (12pt gray).\n\nGrid math for 3 cards, 1.5cm margins, 0.76cm gap: `usable = 33.87 − 3 − 2·0.76 = 29.35`, `col_width = 29.35 \u002F 3 = 9.78cm`. x-positions: `1.5 \u002F 12.04 \u002F 22.58`.\n\n```bash\nSLIDE=2  # second slide, after cover. Adjust from your build order.\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Kubernetes debugging burns 12 engineering hours \u002F incident\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2.5cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\ncat \u003C\u003CEOF | officecli batch \"$FILE\"\n[\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"name\":\"PC1\",\"geometry\":\"roundRect\",\"fill\":\"F5F7FA\",\"x\":\"1.5cm\",\"y\":\"5cm\",\"width\":\"9.78cm\",\"height\":\"10cm\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"73%\",\"x\":\"1.5cm\",\"y\":\"6cm\",\"width\":\"9.78cm\",\"height\":\"3cm\",\"font\":\"Georgia\",\"size\":\"60\",\"bold\":\"true\",\"color\":\"1E2761\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"of incidents take > 1 hour to diagnose\",\"x\":\"1.5cm\",\"y\":\"9.5cm\",\"width\":\"9.78cm\",\"height\":\"3cm\",\"font\":\"Calibri\",\"size\":\"18\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Source: 2025 DORA Report\",\"x\":\"1.5cm\",\"y\":\"13cm\",\"width\":\"9.78cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"12\",\"italic\":\"true\",\"color\":\"666666\",\"align\":\"center\",\"fill\":\"none\"}}\n]\nEOF\n# Repeat the 4-block pattern at x=12.04cm and x=22.58cm for cards 2 and 3.\n```\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"Source\")'` returns ≥ 3 (every claim carries a source). If zero sources, VCs will not trust a single number.\n\n### (2b) Why Now slide — Consumer \u002F Seed \u002F early A must-have\n\n**Visual outcome.** 3 cards across: each = **trigger headline** (24pt bold) + **data point** (60pt number or date) + **one-line implication** (16pt) + **source footnote** (12pt gray). Reuse Problem grid math (`col=9.78cm`, x = `1.5 \u002F 12.04 \u002F 22.58`). §赛道 Consumer row 2 must-have; Seed \u002F early A in any vertical benefits when \"market window\" IS the thesis.\n\n```bash\nSLIDE=3\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Why now: three converging triggers\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2.5cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\n# Card 1 (x=1.5cm) — trigger \u002F data \u002F implication \u002F source. Repeat at x=12.04cm and x=22.58cm.\ncat \u003C\u003CEOF | officecli batch \"$FILE\"\n[\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"geometry\":\"roundRect\",\"fill\":\"F5F7FA\",\"x\":\"1.5cm\",\"y\":\"5cm\",\"width\":\"9.78cm\",\"height\":\"10cm\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"BOM cost\",\"x\":\"1.5cm\",\"y\":\"5.5cm\",\"width\":\"9.78cm\",\"height\":\"1.2cm\",\"font\":\"Calibri\",\"size\":\"24\",\"bold\":\"true\",\"color\":\"1E2761\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"−90%\",\"x\":\"1.5cm\",\"y\":\"7cm\",\"width\":\"9.78cm\",\"height\":\"3cm\",\"font\":\"Georgia\",\"size\":\"60\",\"bold\":\"true\",\"color\":\"B85042\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Wearable BOM fell 90% since 2021; sub-$40 retail now viable\",\"x\":\"1.5cm\",\"y\":\"11cm\",\"width\":\"9.78cm\",\"height\":\"2cm\",\"font\":\"Calibri\",\"size\":\"16\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Source: IDC Wearables Teardown 2025\",\"x\":\"1.5cm\",\"y\":\"13.5cm\",\"width\":\"9.78cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"12\",\"italic\":\"true\",\"color\":\"666666\",\"align\":\"center\",\"fill\":\"none\"}}\n]\nEOF\n# Card 2 pattern: Oura IPO 2024 \u002F +$2.4B valuation \u002F category proven. Card 3: On-device LLM (Llama 3.2) \u002F Q4-24 \u002F privacy moat viable.\n```\n\n**QA.** 3 cards, each with a date\u002Fyear citation in the source footnote, each card ≤ 30 words. `officecli query \"$FILE\" 'shape:contains(\"2024\")'` + `'shape:contains(\"2025\")'` ≥ 2 combined (timing anchors visible).\n\n### (3) Solution slide — product in one sentence + 3-step \"how it works\"\n\n**Visual outcome.** 36pt title naming the product pattern (not \"Our Solution\"). Below: 3 or 4 rounded boxes horizontally at y=7cm with elbow connectors + triangle arrowheads. Each box = one verb (observe \u002F correlate \u002F resolve). Reuse pptx Recipe (c) flowchart — orchestration, not a new primitive.\n\n```bash\n# Title — \"a product pattern, not a brand slogan\".\n# Good: \"Auto-correlate K8s events across 3 data planes in 90 seconds\"\n# Bad:  \"The future of observability\"\nSLIDE=4\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop name=SolTitle \\\n  --prop text=\"Correlate K8s events across 3 data planes in 90 seconds\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2.2cm \\\n  --prop font=Georgia --prop size=32 --prop bold=true --prop color=1E2761 --prop fill=none\n# 3 boxes across: gap = (33.87 − 3 − 3·7) \u002F 2 = 4.93cm; x = 1.5, 13.43, 25.36\n# Connectors + arrowheads: --prop tailEnd=triangle ALWAYS (pptx Known Issues C-P-5..6).\n# Full batch block → see pptx v2 §Creating and Editing (c) 4-step flowchart; swap N from 4 boxes to 3.\n```\n\n**Product-pattern title rule.** The solution title is a verb + differentiated mechanism + metric. \"Observe \u002F Correlate \u002F Resolve\" is generic; VCs read it as any APM vendor. \"Correlate K8s events across 3 data planes in 90 seconds\" is specific; VCs read it as an insight.\n\n**QA.** Count connectors: `officecli query \"$FILE\" 'connector' --json | jq '.data.results | length'` ≥ (step_count − 1). Every connector must have `tailEnd=triangle` — `view annotated` confirms arrowhead direction. Title must be ≤ 12 words (one breath).\n\n### (4) Market slide — TAM \u002F SAM \u002F SOM nested columns\n\n**Visual outcome.** 36pt title \"Market: $X.YB growing Z% CAGR\". Below: three horizontal bars (or three stacked nested rectangles), labeled TAM \u002F SAM \u002F SOM with dollar values + growth rate. Bottom footnote cites **top-down vs bottom-up source** — pick one methodology per deck, don't mix.\n\n```bash\n# Use a pptx column chart with 3 values. Categories = TAM,SAM,SOM. Source annotation is a separate shape.\nSLIDE=5\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"$42B observability market, 18% CAGR\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type chart --prop chartType=bar \\\n  --prop series1.name=\"USD (billions)\" --prop series1.values=\"42,8.4,0.62\" --prop series1.color=1E2761 \\\n  --prop categories=\"TAM,SAM,SOM (5-yr)\" \\\n  --prop x=2cm --prop y=4cm --prop width=22cm --prop height=12cm \\\n  --prop title='Market sizing — bottom-up by enterprise count × ACV'\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='Source: Gartner 2025 APM Magic Quadrant; SAM = 20% of TAM (K8s-first shops); SOM = 7.4% of SAM over 5 years at 18-24% share.' \\\n  --prop x=2cm --prop y=16.5cm --prop width=29.87cm --prop height=2cm \\\n  --prop font=Calibri --prop size=12 --prop italic=true --prop color=666666 --prop fill=none\n```\n\n**QA.** Top-down vs bottom-up MUST be declared in the source footnote. A TAM without methodology reads as fabricated.\n\n### (5) Product slide — screenshot + 3 bullets OR 3-card feature grid\n\n**Visual outcome.** Two layout options: (a) hero product screenshot on the left (60% of slide), 3 one-line feature bullets on the right (each ≥ 18pt body, no bullets under bullets). (b) 3 feature cards with one icon \u002F screenshot thumbnail each. Pick (a) for consumer \u002F app products, (b) for B2B \u002F infrastructure.\n\n```bash\n# (a) screenshot + bullets — consumer pattern\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type picture --prop src=product_hero.png \\\n  --prop x=1cm --prop y=4cm --prop width=18cm --prop height=13cm\nofficecli set \"$FILE\" \"\u002Fslide[$SLIDE]\u002Fpicture[1]\" --prop alt=\"Product UI: dashboard with 12 K8s clusters, live correlation graph\"\n# Right column bullets (each as a separate shape so sizes stay explicit)\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Auto-correlate across 3 data planes\" \\\n  --prop x=20cm --prop y=5cm --prop width=12cm --prop height=1.5cm \\\n  --prop font=Calibri --prop size=20 --prop bold=true --prop color=1E2761 --prop fill=none\n# Repeat for bullets 2 and 3 at y=7.5cm \u002F y=10cm.\n```\n\n**QA.** Picture alt text present (`query 'picture:no-alt'` = empty). Bullets each ≥ 18pt. No \"Lorem\"\u002F\"product name here\"\u002F`{{...}}` tokens.\n\n### (6) Business model slide — unit econ or revenue model\n\n**Visual outcome.** Decision tree by vertical:\n- **SaaS \u002F Enterprise (Series A+)** — 4 KPI callouts: CAC \u002F LTV \u002F Payback \u002F GM (reuse pptx Recipe (e)).\n- **Consumer \u002F D2C** — AOV · repeat-purchase rate · contribution margin · blended CAC.\n- **Marketplace** — GMV \u002F take-rate \u002F liquidity metric \u002F cohort retention.\n- **Bio \u002F Deep tech** — revenue model (license \u002F milestone \u002F royalty split) with assumed ranges.\n\nTitle names the dominant metric (e.g. \"LTV:CAC 4.7x · 14-month payback · 78% gross margin\"), not \"Business Model\". Full 4-card batch block → see pptx v2 §(e) KPI callouts.\n\n```bash\n# SaaS pattern: KPI card values + sub-label + gray VC-floor context under each.\n# Card 1 (LTV): big number \"$420K\", sub \"Lifetime value\", context \"floor: ARPU × GM \u002F churn\"\n# Card 2 (CAC): big number \"$90K\",  sub \"Acquisition cost\", context \"fully-loaded S&M spend\"\n# Card 3 (Payback): big number \"14 mo\", sub \"CAC payback\", context \"VC floor: \u003C 18 mo\"\n# Card 4 (GM): big number \"78%\", sub \"Gross margin\", context \"SaaS floor: 70%+\"\n# Grid math for 4 cards across: usable = 33.87 − 3 − 3·0.76 = 28.59, col = 7.15cm\n# → Full batch template → pptx v2 §(e). Adapt card count 3→4 and card width 9.78cm→7.15cm.\n```\n\n**QA.** For Series B+, all four of {CAC, LTV, payback, GM} present: `officecli query \"$FILE\" 'shape:contains(\"CAC\")'` ≥ 1 AND `shape:contains(\"LTV\")'` ≥ 1 AND `shape:contains(\"payback\")'` ≥ 1 AND `shape:contains(\"gross margin\")'` ≥ 1.\n\n### (7) Traction slide — ARR curve that starts at 0\n\n**Visual outcome.** Line chart taking 60% of slide width; ARR on y-axis **starting at 0** (not at 80% of current value — the VC hockey-stick lie). Right-side commentary card: single giant number (current ARR) + growth rate + 2-3 milestones. If Series B+, second row: cohort retention snippet or logo wall.\n\n```bash\nSLIDE=7\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='ARR: $0 → $18M in 24 months' \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type chart --prop chartType=line \\\n  --prop series1.name=ARR --prop series1.values=\"0.2,0.6,1.4,3.2,6.1,11.3,15.8,18.0\" --prop series1.color=1E2761 \\\n  --prop categories=\"Q1-24,Q2-24,Q3-24,Q4-24,Q1-25,Q2-25,Q3-25,Q4-25\" \\\n  --prop x=1.5cm --prop y=4cm --prop width=21cm --prop height=13cm \\\n  --prop title='Quarterly ARR ($M) — y-axis anchored at 0' \\\n  --prop axismin=0\n# Right callout\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop geometry=roundRect --prop fill=1E2761 --prop line=none \\\n  --prop x=23.5cm --prop y=4cm --prop width=8.8cm --prop height=13cm\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='$18M' \\\n  --prop x=23.5cm --prop y=5cm --prop width=8.8cm --prop height=3cm \\\n  --prop font=Georgia --prop size=64 --prop bold=true --prop color=FFFFFF --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"ARR · +312% YoY · NRR 128%\" \\\n  --prop x=23.5cm --prop y=9cm --prop width=8.8cm --prop height=3cm \\\n  --prop font=Calibri --prop size=18 --prop color=CADCFC --prop align=center --prop fill=none\n```\n\n**`--prop axismin=0` is load-bearing** — without it, pptx auto-scales the y-axis to start near the lowest value. That is the hockey-stick lie. Gate 6 greps this below.\n\n**QA.** ARR curve chart must carry `axismin=0`. `officecli get \"$FILE\" \"\u002Fslide[$SLIDE]\u002Fchart[1]\" --json | jq .format.axisMin` returns `0` (CLI emits camelCase `axisMin` in readback even though input prop is lowercase `axismin`).\n\n### (8) Team slide — avatars + names + prior companies (not just a wall)\n\n**Visual outcome.** 3- or 4-card row across the middle of the slide. Each card: picture (6×6cm) on top; name (20pt bold); role (16pt); **prior company + title** (16pt italic, 1 key line); optional LinkedIn URL footer (12pt). Team slide with just headshots and names reads as amateur.\n\n```bash\nSLIDE=11\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Team: 3 prior exits, 42 years combined K8s\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\n# Card 1 — CEO\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type picture --prop src=alice.jpg \\\n  --prop x=2cm --prop y=5cm --prop width=6cm --prop height=6cm\nofficecli set \"$FILE\" \"\u002Fslide[$SLIDE]\u002Fpicture[1]\" --prop alt=\"Alice Chen, CEO — portrait\"\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Alice Chen\" \\\n  --prop x=2cm --prop y=11.5cm --prop width=6cm --prop height=1cm \\\n  --prop font=Georgia --prop size=20 --prop bold=true --prop color=1E2761 --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"CEO\" \\\n  --prop x=2cm --prop y=12.8cm --prop width=6cm --prop height=0.8cm \\\n  --prop font=Calibri --prop size=16 --prop color=333333 --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"ex-Datadog Director (Series C → IPO); led K8s observability GTM $40M → $200M ARR\" \\\n  --prop x=2cm --prop y=13.8cm --prop width=6cm --prop height=2.5cm \\\n  --prop font=Calibri --prop size=14 --prop italic=true --prop color=333333 --prop align=center --prop fill=none\n# Repeat for Card 2 (CTO, x=10cm) and Card 3 (VP Eng, x=18cm) — 3 cards × 5-6 shapes each.\n```\n\nPrior companies carry **credibility density**. VCs read \"ex-Datadog Director + led $40M → $200M\" in 2 seconds; they read \"co-founder, passionate\" in 0 seconds (because they skip it). Advisors, if shown, go in a smaller row below with a single logo each.\n\n**Arrangement helper.** 3 cards: `col=9.78cm, x=1.5\u002F12.04\u002F22.58`. 4 cards: `col=7.15cm, x=1.5\u002F9.41\u002F17.32\u002F25.23`. 5 cards: `col=5.85cm, x=1.5\u002F7.75\u002F14.0\u002F20.25\u002F26.5` (0.4cm gap, tighter). 6+ or asymmetric → 2-row grid (3×2 \u002F 3×3); see pptx v2 §(d) grid math.\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"ex-\")'` + `'shape:contains(\"prior\")'` + `'shape:contains(\"former\")'` ≥ 1 per team member. If zero, you have a portfolio, not a team.\n\n### (9) Financials slide — 4-year plan + honest assumptions\n\n**Visual outcome.** Column chart: 4 years × (revenue, gross margin $, EBITDA). Right-side card: 3-bullet assumption panel (ARPU assumption, win-rate assumption, churn assumption). Title names the trajectory (\"$18M → $85M by FY29\"), not \"Financial Projections\".\n\nReuse pptx Recipe (b) chart + commentary. Pitch-specific: ASSUMPTIONS column on the right is **load-bearing** — a 4-year plan without visible assumptions reads as aspirational. VCs will ask what's behind every number anyway; surface it.\n\nLeft 2\u002F3 — slide + title + 3-series column chart:\n\n```bash\nSLIDE=17\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='$18M → $85M ARR by FY29' \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type chart --prop chartType=column \\\n  --prop series1.name=\"Revenue ($M)\"  --prop series1.values=\"18,34,58,85\" --prop series1.color=1E2761 \\\n  --prop series2.name=\"Gross Margin ($M)\" --prop series2.values=\"14,26,45,68\" --prop series2.color=CADCFC \\\n  --prop series3.name=\"EBITDA ($M)\"   --prop series3.values=\"-6,-2,8,22\" --prop series3.color=B85042 \\\n  --prop categories=\"FY26,FY27,FY28,FY29\" \\\n  --prop x=1.5cm --prop y=4cm --prop width=20cm --prop height=13cm \\\n  --prop title='4-year plan — revenue, GM, EBITDA ($M)'\n```\n\nRight 1\u002F3 — assumptions commentary card:\n\n```bash\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop geometry=roundRect --prop fill=F5F7FA --prop line=none \\\n  --prop x=22.5cm --prop y=4cm --prop width=9.8cm --prop height=13cm\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Key Assumptions\" \\\n  --prop x=23cm --prop y=4.5cm --prop width=8.8cm --prop height=1.2cm \\\n  --prop font=Georgia --prop size=20 --prop bold=true --prop color=1E2761 --prop fill=none\n# 5 assumption bullets as 5 separate paragraph shapes at y=6, 7.5, 9, 10.5, 12cm — size=14, italic=true.\n# Keep each bullet ≤ 14 words so 8.8cm width fits without wrap.\n```\n\n**Assumptions panel is load-bearing.** A 4-year plan without visible assumptions reads as aspirational. VCs ask what's behind every number anyway — surface the three or four assumptions that drive the curve.\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"assumption\")'` OR `'shape:contains(\"Assumes\")'` ≥ 1. If zero, add the panel.\n\n### (10) The Ask — hero number + 4-bucket Use-of-Funds + runway\n\n**Visual outcome.** Dark fill (match cover). Hero number in the center top: `$35M` at 96pt white. Below, a 4-bucket pie OR a 4-card row listing **Engineering 40% \u002F GTM 35% \u002F G&A 15% \u002F Reserve 10%**. Bottom line: \"18-month runway to $40M ARR\" (next milestone, not \"until next round\").\n\n```bash\nSLIDE=20\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=1E2761\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='$35M Series B' \\\n  --prop x=2cm --prop y=2cm --prop width=29.87cm --prop height=4cm \\\n  --prop font=Georgia --prop size=88 --prop bold=true --prop color=FFFFFF --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type chart --prop chartType=pie \\\n  --prop series1.name=\"Use of Funds\" --prop series1.values=\"40,35,15,10\" \\\n  --prop categories=\"Engineering,Go-to-Market,G&A,Reserve\" \\\n  --prop colors=\"CADCFC,B85042,97BC62,FFFFFF\" \\\n  --prop x=6cm --prop y=7cm --prop width=12cm --prop height=10cm \\\n  --prop title=\"Use of Funds — 4 buckets\"\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='18 months runway to $40M ARR and Series C' \\\n  --prop x=2cm --prop y=17cm --prop width=29.87cm --prop height=1.5cm \\\n  --prop font=Calibri --prop size=22 --prop color=CADCFC --prop align=center --prop fill=none\n```\n\n**4-bucket convention.** Engineering \u002F GTM \u002F G&A \u002F Reserve is the canonical breakdown. Typical Series A ranges: Eng 40-50%, GTM 30-40%, G&A 10-15%, Reserve 5-10%. Series B shifts 5-10 points from Eng to GTM.\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"Use of Funds\")'` ≥ 1. Pie chart present on ask slide. Runway + milestone on ask slide.\n\n### (11) Pipeline chart — Bio \u002F Deep Tech must-have\n\n**Visual outcome.** Horizontal swimlane. Left column = candidate name; 4 stage columns to the right (Preclinical \u002F Ph1 \u002F Ph2 \u002F Ph3 for bio — or TRL1-3 \u002F TRL4-6 \u002F TRL7-8 \u002F TRL9 for deep tech). Each row's bar extends to its current stage; darker fill for later stages. NCT \u002F trial-ID footer below. §赛道 row 5 Bio must-have; SaaS \u002F Consumer skip.\n\nGrid math: usable `= 30.87cm`, candidate col `= 7cm`, stage cols `= (30.87 − 7) \u002F 4 = 5.97cm` each, row height `= 2.3cm`. Stage col x: `8.5 \u002F 14.47 \u002F 20.44 \u002F 26.41`.\n\n```bash\nSLIDE=6\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Pipeline: 3 candidates across Ph1–Ph3\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\n# 4 stage headers + candidate row 1 (HLX-201 at Ph2, bar width = 3·5.97 = 17.91cm) in one batch.\ncat \u003C\u003CEOF | officecli batch \"$FILE\"\n[\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Preclinical\",\"x\":\"8.5cm\",\"y\":\"4cm\",\"width\":\"5.97cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"16\",\"bold\":\"true\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"F5F7FA\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Phase 1\",\"x\":\"14.47cm\",\"y\":\"4cm\",\"width\":\"5.97cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"16\",\"bold\":\"true\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"F5F7FA\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Phase 2\",\"x\":\"20.44cm\",\"y\":\"4cm\",\"width\":\"5.97cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"16\",\"bold\":\"true\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"F5F7FA\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Phase 3\",\"x\":\"26.41cm\",\"y\":\"4cm\",\"width\":\"5.97cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"16\",\"bold\":\"true\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"F5F7FA\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"HLX-201 (lead)\",\"x\":\"1.5cm\",\"y\":\"5.5cm\",\"width\":\"7cm\",\"height\":\"1.5cm\",\"font\":\"Calibri\",\"size\":\"18\",\"bold\":\"true\",\"color\":\"1E2761\",\"align\":\"left\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"geometry\":\"roundRect\",\"fill\":\"1E2761\",\"x\":\"8.5cm\",\"y\":\"5.7cm\",\"width\":\"17.91cm\",\"height\":\"1.1cm\",\"line\":\"none\"}}\n]\nEOF\n# Repeat rows 2 & 3 at y=7.8cm \u002F y=10.1cm with bar widths per stage (Ph1=5.97cm, Ph1-Ph2=11.94cm, Ph1-Ph3=17.91cm).\n# NCT footer full-width at y=16.8cm.\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='NCT05021323 (HLX-201, Ph2, n=48) · NCT06142091 (HLX-304, Ph1, n=24) · IND-filed Q1-26 for HLX-412' \\\n  --prop x=1.5cm --prop y=16.8cm --prop width=30.87cm --prop height=1.2cm \\\n  --prop font=Calibri --prop size=12 --prop italic=true --prop color=666666 --prop fill=none\n```\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"NCT\")' --json | jq '.data.results | length'` ≥ 1. Bar colors darken across stages (`CADCFC` preclinical-only, `1E2761` Ph2-reached).\n\n### (12) Competitive comparison table — Series B+ essential\n\n**Visual outcome.** 5–7 rows × 4–6 cols. Column 1 = competitor name (optional logo shape beside); rest = differentiators (speed \u002F price \u002F integrations \u002F margin \u002F coverage). **Last row = your company, fill highlighted** in an accent color (CADCFC \u002F 97BC62); competitor rows gray. Every Series B+ deck needs this (SaaS: Datadog \u002F New Relic \u002F Splunk; Bio: Kite \u002F Novartis \u002F BMS).\n\n```bash\nSLIDE=13\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Competitive landscape\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\n# Inline table via --prop data= (per-cell r#c# is silently ignored \u002F not honored — use data=). Single-quote the data value — '$15\u002Fhost' would strip.\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type table \\\n  --prop data='Competitor,Speed,Price,Integrations,Margin;Datadog,12 min,$15\u002Fhost,680,75%;New Relic,18 min,$25\u002Fhost,520,68%;Splunk,45 min,$45\u002FGB,310,62%;You (Acme DevOps),90 sec,$8\u002Fhost,1200,82%' \\\n  --prop style=medium1 --prop headerFill=1E2761 \\\n  --prop x=1.5cm --prop y=4cm --prop width=30.87cm --prop height=12cm\n# Highlight your row: loop over \u002Fslide[$SLIDE]\u002Ftable[1]\u002Ftr[5]\u002Ftc[1..5] and set cell fill to CADCFC.\n```\n\n**QA.** `officecli query \"$FILE\" 'table' --json | jq '.data.results | length'` ≥ 1. Row count ≥ 4 (you + ≥ 3 named competitors). Your row visually distinct via cell fill (Gate 5b visual check — table style alone does not highlight one row).\n\n## Numbers convention (pitch-specific)\n\nA terse convention table — **not a finance tutorial**. If you don't already know what these mean, pause the deck and ask the user for the values; don't guess.\n\n| Metric | Shape | Floor \u002F convention |\n|---|---|---|\n| **TAM** | `$X.YB`, one methodology | Either top-down (analyst report) or bottom-up (count × ACV). Never both; never neither. |\n| **SAM** | `$X.YB`, fraction of TAM you serve | Typically 15 – 30% of TAM for verticalized SaaS; higher for horizontal |\n| **SOM** | `$X.YB` at year N | Realistic 5-yr share: 5 – 15% of SAM for early stage |\n| **ARR** | MRR × 12. NOT revenue. | SaaS only; contracts on books, net of churn |\n| **MRR** | Monthly recurring | ARR \u002F 12; do not confuse with monthly revenue |\n| **NRR (Net Revenue Retention)** | %, trailing 12 mo | VC floor: > 100% acceptable, > 115% strong, > 130% exceptional |\n| **CAC** | $ fully-loaded | Sales + marketing spend \u002F new logos acquired |\n| **LTV** | $ | ARPU × gross margin × (1 \u002F churn rate) |\n| **LTV:CAC** | ratio | VC floor: 3x OK, > 4x strong, > 5x exceptional |\n| **CAC payback** | months | VC floor: \u003C 18 mo OK, \u003C 12 mo strong |\n| **Gross margin** | % | SaaS floor 70%, strong 80%+; marketplace 15-40%; hardware 30-50% |\n| **Burn \u002F runway** | $\u002Fmonth + months | Gross burn vs net burn — label which; runway to specific milestone |\n| **Use of Funds** | 4-bucket pie | Engineering \u002F Go-to-Market \u002F G&A \u002F Reserve — see Ask slide recipe |\n\n**Rule.** Every number on a deck carries a unit. `18%` or `18M` alone is ambiguous — write `$18M ARR` \u002F `18% NRR growth`. `TBD`, `coming soon`, `(fill in)`, `lorem`, `xxxx` in numeric slots = immediate VC disqualification. Gate 6 greps these below.\n\n## VC ship-check (6 red flags \u002F positive signals)\n\nWhat the VC reads in the first 30 seconds. Six one-line conditions — every \"FAIL\" below is an instant round-killer; fix before delivering.\n\n| # | Red flag (FAIL if present) | Positive signal (shipwise) |\n|---|---|---|\n| 1 | Cover without round + amount + date | `Company · tagline · Series X · $YM · Date` in 4 lines |\n| 2 | TAM > $100B without a cited source \u002F methodology | TAM clearly labeled bottom-up OR top-down with a visible 2024+ source |\n| 3 | Traction chart y-axis does not start at 0 (hockey-stick lie) | Line chart `axismin=0`; growth shape honest |\n| 4 | Team slide: headshots + names only, no prior companies | Every member: prior company + role + 1 achievement metric |\n| 5 | Ask slide missing Use-of-Funds breakdown | `$XM` hero + 4-bucket pie (Eng \u002F GTM \u002F G&A \u002F Reserve) + runway + next milestone |\n| 6 | `TBD` \u002F `lorem` \u002F `xxxx` \u002F `{{...}}` \u002F `(fill in)` anywhere | `view text` clean — zero placeholder tokens |\n\n**Common Series-specific failures.**\n- **Series A specific** — bottom-up TAM calculated from a fictional enterprise-count × ACV (no reference customers to anchor the count); `CAC \u002F LTV` shown with \u003C 12 months of data (statistically meaningless).\n- **Series B specific** — no unit-econ slide at all; CAC payback > 24 months without a \"we're pre-scale, here's the plan\" narrative; logo wall \u003C 8 customers.\n- **Series C specific** — no moat \u002F defensibility slide; revenue growth shown without margin trajectory; international expansion stated but no specific launch plan \u002F hires.\n\nThe Delivery Gate 6 block below executes checks 1–6 above via grep + query. Gate 5b fresh-eyes covers the visual judgments (hockey stick, team credibility) that grep can't see.\n\n## Traction triple-pattern (ARR + milestones + logos)\n\nFor Series B+, traction often spans 2 slides: one for the chart + callout (recipe 7 above), one for **milestone timeline + logo wall**. Timeline = 4-6 horizontal dates with one-line events. Logo wall = 12-20 customer logos in a 4×N or 5×N grid, muted monochrome so no single brand dominates.\n\n```bash\n# Milestone timeline: 5 dates as circles on a horizontal line at y=8cm.\n# Use pptx shapes (ellipse preset) + connectors (shape=straight) between them.\n# Each milestone = ellipse at y=8cm + date label above + event description below.\n# → See pptx v2 Recipe (d) row 9 (Roadmap timeline) for the canonical pattern.\n\n# Logo wall: pictures in a 5×N grid. Typical spacing: logo width = 5cm, height = 2cm, gap = 0.4cm.\n# grid math for 5 logos across, 1.5cm edge margin: usable = 33.87 − 3 − 4·0.4 = 29.27, col = 5.85cm\n# (use 5cm logo width centered in each 5.85cm column)\n```\n\n**QA.** Logo wall should have ≥ 8 logos for Series B+, ≥ 4 for Series A. Fewer = \"lighter than it looks\"; more than 20 = pixel noise.\n\n## QA — Delivery Gate (executable)\n\n**Assume there are problems.** First render is almost never correct. Pitch decks fail at two layers: **structural** (schema, token leaks — caught by pptx v2 Gates 1–3) and **narrative** (wrong stage, missing unit econ, TAM unsourced — the checks that make pptx v2 Gate 5b + Gate 6 indispensable). Every check must print its success message.\n\n### Gates 1–5a — inherited from pptx v2 verbatim\n\n→ see pptx v2 §Delivery Gate L637-679. Copy-paste the full block:\n\n- **Gate 1** — `validate` schema check (whitelist `ChartShapeProperties` warnings per C-P-2).\n- **Gate 2** — token leak via `view text` grep (`$xxx$`, `{{...}}`, `\u003CTODO>`, `lorem`, `xxxx`, empty `()`\u002F`[]`, `\\$`\u002F`\\t`\u002F`\\n` literals).\n- **Gate 3** — hyperlink `rPr` schema trap (C-P-1) — zero `\u003Ca:rPr>\u003Ca:hlinkClick>`.\n- **Gate 4** — slide-order sanity — cover first, dividers before sections, closing last.\n- **Gate 5a** — dark-on-dark contrast — every fill in `{1E2761, 0A1628, 8B1A1A, 2C5F2D, 36454F}` must declare near-white textColor. **This includes charts rendered on that fill**: chart `title.textColor`, `legend.textColor`, axis text default to dark and read as invisible on dark backgrounds — set them explicitly, or place the chart on a light card inside the dark slide.\n\nDo not skip or reorder these five. Every pptx-layer defect caught by Gates 1–5a also fires on pitch decks.\n\n**Gate 2b — pitch-specific shell-strip signatures (MANDATORY).** Gate 2 misses `$35M` that zsh silently stripped to empty (no residue to grep). Run this after Gate 2:\n\n```bash\n# $XXM stripped by zsh leaves bare \" M ARR\" \u002F \" M raised\" \u002F \"Series [A-C] · M\" patterns.\nSTRIP=$(officecli view \"$FILE\" text | grep -niE '(^|[^A-Za-z0-9])M (ARR|raised|Series|runway|round|raise)|Series [A-C] · M( |$)|runway · M|raised · M|raising ·? M')\n[ -z \"$STRIP\" ] && echo \"Gate 2b OK (no \\$-strip signatures)\" || { echo \"REJECT Gate 2b (likely zsh \\$-strip — re-issue with single quotes):\"; echo \"$STRIP\"; exit 1; }\n```\n\nFix: re-issue the offending `add`\u002F`set` with single quotes around the text value (`--prop text='Series B · $35M'`, not double quotes). The same strip hits **chart series names \u002F axis titles** (`--prop name=\"营收 ($M)\"` → legend shows `营收 ()`): single-quote every chart prop carrying `$`.\n\n### Gate 5b — Visual audit via HTML preview (MANDATORY, NOT optional)\n\nGates 1–5a are token-grep defenses. **They cannot see a rendered slide.** This step is the only visual-assembly check. Do not skip.\n\nRun `officecli view \"$FILE\" html` and Read the returned HTML. Walk every slide and answer, for EACH (inherits pptx v2 Gate 5b checklist; pitch-specific additions marked ⭐):\n\n- **overlap**: do any text shapes overlap each other or a chart?\n- **dark-on-dark**: is any text on a fill where fill brightness \u003C 30% AND text brightness \u003C 80%?\n- **divider overlap**: any giant decorative number (01\u002F02\u002F03 at 100pt+) colliding with the divider title text?\n- **order sanity**: does the slide sequence match your stage-appropriate narrative outline?\n- **missing arrowheads**: do flowchart\u002Fdecision-tree connectors show direction, or plain lines?\n- ⭐ **traction y-axis**: does every ARR \u002F revenue \u002F growth line chart start at 0 on the y-axis? (Not 80% of current — that is the hockey-stick lie.)\n- ⭐ **team credibility**: does every team-slide card show a prior company or prior title? (Cards with just headshot + name = reject.)\n- ⭐ **TAM \u002F market number credibility**: is the TAM under $100B for a niche market, or if ≥ $100B, is a methodology source cited? (A claimed `$500B TAM` with no source is an auto-reject red flag.)\n- ⭐ **Use-of-Funds pie**: does the ask slide carry a 4-bucket pie (Engineering \u002F GTM \u002F G&A \u002F Reserve) or a 4-card row with %s?\n- ⭐ **narrative completeness**: is the order cover → problem → solution → market → product → model → traction → team → financials → ask, or your stage-appropriate permutation from §Stage diagnosis?\n\n**Instruction.** Run `officecli view \"$FILE\" html` and Read the HTML. Walk every slide against the questions below. If rendering chart colors, animations, or zoom — those only show in the target viewer (PowerPoint \u002F Keynote \u002F WPS); ask the user to open `.pptx` directly for those runtime features.\n\n> For every slide:\n> (a) Are slides in VC narrative order (cover → problem → solution → market → product → model → traction → team → financials → ask, with your stage's adjustments)? Flag any out-of-sequence.\n> (b) Is every ARR \u002F revenue \u002F growth line chart y-axis anchored at 0? Flag hockey-stick visual lies.\n> (c) Does the team slide carry prior-company credentials for each person? (Not just headshot + name.)\n> (d) Does every TAM \u002F SAM \u002F SOM claim have a visible source or methodology?\n> (e) Does the ask slide have a 4-bucket Use of Funds (Engineering \u002F GTM \u002F G&A \u002F Reserve) and a specific next milestone + runway length?\n> (f) Any text overlap, dark-on-dark, off-slide geometry, missing arrowheads, placeholder tokens (`TBD` \u002F `lorem` \u002F `{{...}}` \u002F `xxxx` \u002F empty `()`)?\n\nReport every instance with slide number. If ANY defect — REJECT; do not deliver until fixed.\n\n**Human preview (optional).** If you want the user to visually preview the deck, run `officecli watch \"$FILE\"` for a live preview the user can open at their own discretion, or have them open the `.pptx` directly in PowerPoint \u002F WPS \u002F Keynote. For final visual verification, open the file in the target presentation viewer.\n\n### Gate 6 — Pitch narrative sanity (executable)\n\nPitch-specific checks that grep the deck for VC red flags. Every one is a token check — combine with Gate 5b's human read for full coverage.\n\n```bash\nFILE=\"deck.pptx\"\n\n# 6.1 — no TBD \u002F lorem \u002F placeholder tokens (stronger than Gate 2 — pitch-specific scope)\nLEAK=$(officecli view \"$FILE\" text | grep -niE 'TBD|lorem|\\(fill in\\)|xxxx|coming soon|placeholder')\n[ -z \"$LEAK\" ] && echo \"Gate 6.1 OK (no placeholder tokens)\" || { echo \"REJECT Gate 6.1:\"; echo \"$LEAK\"; exit 1; }\n\n# 6.2 — TAM \u002F SAM \u002F SOM presence (Series A+)\nTAM_HIT=$(officecli query \"$FILE\" 'shape:contains(\"TAM\")' --json | jq '.data.results | length')\n[ \"$TAM_HIT\" -ge 1 ] && echo \"Gate 6.2 OK (TAM slide present)\" || echo \"WARN Gate 6.2: no TAM mention — confirm stage is Seed \u002F Bridge if intentional\"\n\n# 6.3 — Unit econ presence (Series B+): CAC OR LTV OR payback\nCAC_HIT=$(officecli query \"$FILE\" 'shape:contains(\"CAC\")' --json | jq '.data.results | length')\nLTV_HIT=$(officecli query \"$FILE\" 'shape:contains(\"LTV\")' --json | jq '.data.results | length')\nif [ \"$CAC_HIT\" -ge 1 ] || [ \"$LTV_HIT\" -ge 1 ]; then\n  echo \"Gate 6.3 OK (unit econ surface)\"\nelse\n  echo \"WARN Gate 6.3: no CAC \u002F LTV — confirm stage Seed\u002FA if intentional, REJECT if Series B+\"\nfi\n\n# 6.4 — Use of Funds present on ask slide\nUOF_HIT=$(officecli query \"$FILE\" 'shape:contains(\"Use of Funds\")' --json | jq '.data.results | length')\n[ \"$UOF_HIT\" -ge 1 ] && echo \"Gate 6.4 OK (Use of Funds)\" || { echo \"REJECT Gate 6.4: ask slide missing Use of Funds\"; exit 1; }\n\n# 6.5 — Team prior-company signal (at least one of ex- \u002F former \u002F prior \u002F previously)\nPRIOR_HIT=$(officecli view \"$FILE\" text | grep -ciE '\\b(ex-|former|prior|previously)\\b')\n[ \"$PRIOR_HIT\" -ge 1 ] && echo \"Gate 6.5 OK (team prior-company)\" || { echo \"REJECT Gate 6.5: team slide has no prior-company credentials\"; exit 1; }\n\n# 6.6 — Traction chart y-axis anchored at 0 (at least one chart must set axismin=0, Series A+)\nAXISMIN_HIT=$(officecli query \"$FILE\" 'chart' --json | jq '[.data.results[]? | select(.format.axisMin == \"0\" or .format.axisMin == 0 or .format.axismin == \"0\" or .format.axismin == 0)] | length')\n[ \"$AXISMIN_HIT\" -ge 1 ] && echo \"Gate 6.6 OK (traction chart axisMin=0)\" || echo \"WARN Gate 6.6: no chart sets axisMin=0 — confirm no ARR\u002Frevenue line chart, or add --prop axismin=0\"\n\necho \"Delivery Gate 6 PASS (token + narrative checks) — proceed to Gate 5b fresh-eyes (MANDATORY)\"\n```\n\n**Readback key note.** CLI accepts lowercase `axismin` as input (on `--prop axismin=0`) but emits camelCase `axisMin` in `query --json` readback. The jq above accepts both for forward-compat.\n\nGate 6 is a grep floor. Gate 5b is the visual ceiling. Ship only when both print PASS.\n\n### Honest limit\n\n`validate` catches schema errors, not fundraising errors. A deck passes `validate` with a `$500B TAM` on a $10M market, a team slide of four co-founders with no prior companies, a hockey stick y-axis at 80%, a pitch for a Series B round without unit econ, and an ask slide saying \"we're raising some money\". Gates 5b + 6 above exist because `validate` cannot catch any of this.\n\n## Known Issues & Pitfalls\n\n→ Base pitfalls (shell escape, `[last()]` in resident, connector `@name=` rejection C-P-6, picture alt two-step C-P-7, animation remove C-P-4, chart color normalization C-P-7): see pptx v2 §Known Issues & Pitfalls C-P-1..7.\n\nPitch-specific:\n\n- **Stage misidentified.** Series A deck with 6 pages of CAC\u002FLTV math = over-packaged. Series B deck missing unit econ = incomplete. If unsure, re-read §Stage diagnosis before building.\n- **Hockey-stick y-axis.** If the line chart's y-axis doesn't start at 0, VCs read it as a visual lie within 2 seconds. Always `--prop axismin=0` on ARR \u002F revenue \u002F growth charts. Gate 6.6 checks this.\n- **Team slide = portfolio.** Cards showing only {headshot + name + role} fail VC credibility. Every card needs a prior-company or prior-achievement line. Gate 6.5 checks this.\n- **TAM without methodology.** A claimed number with no \"top-down\" or \"bottom-up\" source footnote = fabricated. Pick one methodology per deck; don't mix.\n- **Use-of-Funds as 3-bucket or 5-bucket.** 4-bucket (Eng \u002F GTM \u002F G&A \u002F Reserve) is convention; departing from it reads as sloppy. Gate 6.4 checks presence.\n- **Pitch deck used for a board review \u002F sales deck.** Narrative arc (problem → ask) makes board reviews awkward — route to pptx v2 Recipe (d) 10-slide instead. See §Reverse handoff above.\n- **pptx v2 Recipe (d′) 20-slide is a starting point, not a formula.** It is stage-agnostic SaaS. Adjust for your stage + 赛道 via §Stage diagnosis and §赛道 arc templates — never ship (d′) unchanged for a non-SaaS Series A.\n\n## Help pointer\n\nWhen in doubt: `officecli help pptx`, `officecli help pptx \u003Celement>`, `officecli help pptx \u003Celement> --json`. Help is the authoritative schema; this skill is the decision guide for fundraising deltas on top of pptx v2.\n","# OfficeCLI Pitch Deck Skill\n\n**This skill is a scene layer on top of `officecli-pptx`.** Every pptx hard rule — visual delivery floor (title ≥ 36pt \u002F body ≥ 18pt \u002F title ≥ 2× body), 12-column grid on 33.87×19.05cm, 4 canonical palettes, chart-choice decision table, connector canon (`shape` \u002F `from` \u002F `to` \u002F `tailEnd=triangle`), shell escape, resident + batch, Delivery Gate 1–5a — is inherited, not re-taught. This file adds only what **fundraising** needs on top: stage diagnosis (A \u002F B \u002F C), 5 赛道 arc templates, 10 key-slide recipes (cover \u002F problem \u002F solution \u002F market \u002F product \u002F model \u002F traction \u002F team \u002F financials \u002F ask), pitch-specific numbers convention, a VC ship-check, and a pitch-specific fresh-eyes Gate 6.\n\nWhen the pptx base rules cover it, the text here says `→ see pptx v2 §X`. Read `skills\u002Fofficecli-pptx\u002FSKILL.md` first if you have not.\n\n## Setup\n\nIf `officecli` is missing:\n\n- **macOS \u002F Linux**: `curl -fsSL https:\u002F\u002Fd.officecli.ai\u002Finstall.sh | bash`\n- **Windows (PowerShell)**: `irm https:\u002F\u002Fd.officecli.ai\u002Finstall.ps1 | iex`\n\nVerify with `officecli --version` (open a new terminal if PATH hasn't picked up). If install fails, download a binary from https:\u002F\u002Fgithub.com\u002FiOfficeAI\u002FOfficeCLI\u002Freleases.\n\n## ⚠️ Help-First Rule\n\n**This skill teaches what a fundraising deck requires, not every command flag.** When a prop name, enum value, or preset is uncertain, consult help BEFORE guessing.\n\n```bash\nofficecli help pptx                          # All pptx elements\nofficecli help pptx \u003Celement>                # Full schema (e.g. chart, shape, connector, picture)\nofficecli help pptx \u003Celement> --json         # Machine-readable\n```\n\nHelp reflects the installed CLI version. When this skill and help disagree, **help wins.** Every `--prop X=` in this file has been grep-verified against `officecli help pptx \u003Celement>` — if help adds \u002F renames a prop in a later version, trust help.\n\n## Mental Model & Inheritance\n\n**Inherits pptx v2.** You should have read `skills\u002Fofficecli-pptx\u002FSKILL.md` first. This skill assumes you know how to: add slides + shapes + charts + connectors; address by `@name=` \u002F `@id=`; quote paths; use `batch` heredocs; write `--prop tailEnd=triangle` on every flow connector; and run the 5-gate Delivery Gate. If any of those are unfamiliar, open a pptx v2 session before continuing.\n\n## Shell & Execution Discipline\n\n**Shell quoting, incremental execution, `$FILE` convention** → see pptx v2 §Shell & Execution Discipline. Same rules verbatim — quote `[N]` paths, single-quote values containing `$` (including `$35M`, `$1.2B TAM` in a cover or ask slide), never hand-write `\\$ \\t \\n` in executable examples, one command at a time. Examples below use `$FILE` (`FILE=\"deck.pptx\"`).\n\n**Single-quote every shape text containing `$`.** `--prop text=\"Series B · $35M\"` (double quotes) is WRONG — zsh expands `$35M` → empty, deck renders `Series B · M` silently. `--prop text='Series B · $35M'` (single quotes) is right. This is the #1 pitch-deck shell-escape failure mode (`$35M`, `$18M ARR`, `$1.2B TAM` appear on cover\u002Fask\u002Ffinancials\u002Fmilestones). Gate 2 cannot detect a stripped `$35M` — no residue. Gate 2b catches common strip patterns; single-quoting PREVENTS them.\n\n## What \"pitch deck\" means here (identity)\n\nA pitch deck is a pptx with a **fundraising layer** on top: VC-oriented narrative arc, verifiable metrics, stage-appropriate data density, founder-credibility surface. Slides are consumed at ~3 seconds per slide in a live room — the pptx v2 rule. Pitch decks add a second constraint on top: **every slide carries one investable proposition**. If a slide is \"interesting background\" that doesn't move the ask forward, cut it. VCs will not. The base pptx rules still apply; pitch decks add six deltas:\n\n1. **Stage determines everything.** Series A \u002F B \u002F C each dictates slide count, narrative weight, which metrics are must-haves, and tolerance for unit-econ sophistication. A Series A deck with 6 pages of CAC\u002FLTV math reads as over-packaged; a Series B deck missing unit econ reads as incomplete. Pick the stage first — everything downstream follows.\n2. **Narrative arc beats feature dump.** 10 essential slides in a fixed order: cover → problem → solution → market → product → model → traction → team → financials → ask. Out of order = VCs disengage.\n3. **Numbers are a contract.** TAM\u002FSAM\u002FSOM must be clean three-layer; CAC\u002FLTV must have a payback line; ARR ≠ revenue; Use-of-Funds must be a four-bucket pie. Sloppy numbers = round dies.\n4. **Team slide carries prior companies.** Avatar grid alone reads as a student project. Add prior-company logos \u002F names + one-line role. Without this, first-time founders look exactly like first-time founders.\n5. **Traction chart y-axis starts at 0.** A \"hockey stick\" starting at `y_min = 80% of current` is a visual lie — VCs who have seen 10,000 decks spot it in \u003C 2 seconds.\n6. **The ask is a slide, not a footnote.** `$XX M` hero + four-bucket Use-of-Funds + runway length. \"We're raising some money\" is not an ask.\n\n### Reverse handoff — when to go BACK to pptx base\n\nStay in **pptx v2 base** for board reviews, all-hands, sales decks, product launches, training decks — anything not tied to raising capital. Use **this skill** only when: (a) the user mentions a specific round (seed \u002F Series A \u002F B \u002F C) or a VC meeting, AND (b) the deck needs at least 4 of {problem, traction, team with credentials, Use-of-Funds, stage-appropriate unit econ, financial projections}.\n\nIf the user says \"fundraising deck\" but the context is a corporate BU quarterly ask, that is a board review. Route to pptx v2 Recipe (d) 10-slide blueprint. If the user says \"board review\" but the context is a small company raising a bridge round, route here.\n\n## Series A \u002F B \u002F C stage diagnosis (decision tool)\n\n**Read this before writing a single command.** Pick the row that matches the user's description — everything downstream (slide count, which metrics, which recipes, what the team slide must show) derives from this one call.\n\n| Stage | Revenue band | Team | Slide count | Dominant narrative (weight) | Must-have data | Common red flag |\n|---|---|---|---|---|---|---|\n| **Seed** | $0 – $1M ARR (often pre-rev) | 2 – 8 FTE | 10 – 12 | Problem (30%) + Solution (25%) + Team (15%) + Market (15%) + Traction (15%) | Founder-market fit story; 1 – 2 design-partner \u002F pilot logos; top-down TAM ok | Over-claiming traction (10 customers = \"market proven\") |\n| **Series A** | $1 – $5M ARR | 10 – 25 FTE | 12 – 16 | Problem (20%) + Solution (20%) + **Market \"why now\"** (15%) + Product (15%) + Traction (20%) + Team (10%) | PMF proof (NRR > 110%, low churn), bottom-up TAM\u002FSAM, pipeline \u002F pilots converted | Bottom-up TAM feels fabricated; CAC not yet meaningful but shown anyway |\n| **Series B** | $5 – $30M ARR | 30 – 100 FTE | 18 – 22 | **Traction + Unit econ (30%)** + Market + Product + Team + Financials (ask) | ARR curve starting at 0; NRR, CAC, LTV, payback (\u003C 18 mo ideal); cohort retention; logo wall | No unit-econ slide; CAC payback > 24mo without explanation; Use-of-Funds missing % |\n| **Series C** | $30M+ ARR | 100+ FTE | 20 – 24 | **Financials + Scale + Moat (40%)** + Market expansion + Team depth | Multi-year GAAP, rule-of-40, GM trajectory, international expansion plan, defensibility | No moat slide; revenue growth without margin story; team slide has no prior CEO \u002F CFO |\n| **Bridge \u002F SAFE** | any | any | 8 – 10 | **Specific bridge reason** + runway math + commitments | Prior round context; specific milestone the bridge funds; committed investor amount | Treating a bridge like a Series A — too many slides dilutes the ask |\n\n**Decision procedure.** From one or two user sentences (\"Series B, $18M ARR, 120 customers, $35M raise\"), pick exactly one stage row. All later choices in this skill reference your stage: which 赛道 template to pull, which recipes are mandatory vs optional, and which Delivery Gate 6 checks fire.\n\n**Corner cases.** Bridge rounds & convertibles between A → B are closer to A or B depending on whether the bridge milestone is \"finish PMF\" (A shape) or \"hit unit-econ target\" (B shape). \"Extension\" rounds at the same stage reuse the earlier stage's skeleton and add a one-slide \"progress since last round\" update.\n\n**Non-SaaS stage overrides.** The ARR \u002F unit-econ shape of Series B fits SaaS. For other verticals, substitute revenue band + unit-econ equivalent + Gate 6.3 grep:\n\n| Vertical | Revenue \"band\" at Series B | \"Unit econ\" equivalent | Gate 6.3 substitute |\n|---|---|---|---|\n| **Bio \u002F Clinical-stage** | pre-rev, 20–60 FTE | burn rate + runway to next milestone (IND \u002F Ph1 readout \u002F BLA) | `shape:contains(\"ORR\")` OR `contains(\"Pipeline\")` OR `contains(\"BLA\")` OR `contains(\"runway\")` ≥ 1 |\n| **Deep Tech \u002F Frontier** | pre-rev or early pilot rev | technical milestones + TRL level + benchmark vs SoTA | `shape:contains(\"TRL\")` OR `contains(\"benchmark\")` ≥ 1 |\n| **Marketplace \u002F Network** | GMV $10–100M | take rate + cohort retention + liquidity | `shape:contains(\"GMV\")` + `contains(\"take rate\")` ≥ 1 |\n| **Consumer hardware** | $2–15M revenue (shipped units) | contribution margin + repeat rate + blended CAC | `shape:contains(\"repeat\")` OR `contains(\"contribution\")` ≥ 1 |\n\nSubstitute the analogue grep when running Gate 6.3 on these verticals. False WARN on SaaS CAC\u002FLTV = expected; real concern = vertical-specific analogue present. Bio Series B decks especially: burn + runway-to-milestone IS the \"unit econ\" story.\n\n## 赛道 arc templates (5 families)\n\n5 mainstream verticals. Each one has different slide weights because what VCs require as proof-of-concept differs. Pick the vertical row; the slide skeleton is a copy-able starting point. Slide counts assume the matching stage row above.\n\n### (1) B2B SaaS \u002F Enterprise software\n\nCanonical arc — the template most of VC muscle memory is built on. Series B example (20 slides): cover · TL;DR · problem · problem evidence · solution · product loop · market TAM\u002FSAM\u002FSOM · **unit economics (CAC \u002F LTV \u002F payback \u002F GM)** · ARR trajectory · retention cohort · logo wall · team · competitors · financials 4-year · ask. Must-have: unit-econ slide from Series A onward; logo wall from Series B onward.\n\n### (2) Consumer (B2C app \u002F consumer hardware \u002F D2C)\n\nNarrative-driven. Early-stage decks lean on **product-experience screenshots + founding story + \"why now\"** market timing; lighter on unit econ (which are usually weaker than SaaS). Series A example (14 slides): cover · hook (30-second product demo or 1-line vision) · problem (lived experience) · solution (product shots) · product-experience flow · \"why now\" market window · pre-order \u002F crowdfunding \u002F early-sales evidence · retention \u002F engagement (DAU, D30) · market (top-down ok if bottom-up unreliable) · competitive positioning · founder story + team · press \u002F endorsements · financials · ask. Must-have: product visuals on ≥ 3 slides; \"why now\" slide (window justification); engagement metric not just revenue.\n\n### (3) Deep Tech \u002F Frontier tech (AI foundation models, quantum, climate hardware, robotics)\n\nTechnology credibility is the sell. Pre-revenue deep tech replaces \"traction\" with **technical milestones + defensibility**. Series B example (22 slides): cover · thesis (one-line \"what changes if this works\") · problem (current state of art) · solution (technical approach) · **technology architecture** · benchmarks vs SoTA · pipeline \u002F TRL levels · market (long-tail) · business model · early commercial traction (pilots, LOIs) · IP \u002F patents · team (usually PhD \u002F ex-FAANG-research) · partners · financials · ask. Must-have: benchmark slide; IP slide; team slide dense with PhDs \u002F prior-lab names.\n\n### (4) Marketplace \u002F Network business (two-sided platform, social, commerce)\n\nLiquidity is the metric. Replace \"unit econ\" with **GMV + take rate + cohort retention + supply \u002F demand balance**. Series A example (15 slides): cover · problem (friction in current supply-demand) · solution · product demo (both sides) · network effects diagram · early liquidity (first-week GMV, time-to-match) · cohort retention · geographic \u002F category expansion plan · competitive positioning vs incumbents · take-rate model · team · financials · ask. Must-have: liquidity metric slide; cohort retention chart; network-effect diagram.\n\n### (5) Bio \u002F Life sciences \u002F Healthtech\n\nRegulatory pipeline IS the business. Replace \"product roadmap\" with **clinical pipeline + regulatory path + scientific evidence**. Series B example (22 slides): cover · unmet medical need · scientific rationale (mechanism of action) · preclinical \u002F clinical data (ORR, safety, endpoints) · **pipeline chart** (candidates × stages × dates) · differentiation vs standard of care · IP \u002F exclusivity · regulatory strategy (IND, BTD, fast-track) · market (prevalence × pricing) · commercial strategy (orphan \u002F specialty \u002F biosimilar) · partnerships \u002F collaborations · team (CSO \u002F CMO with prior FDA wins) · financials (burn to next milestone) · ask. Must-have: pipeline chart; clinical data slide; team slide with prior regulatory wins.\n\n**Cross-vertical rule.** You can mix elements across templates, but never drop a must-have from your primary vertical. A SaaS deck missing unit econ, a bio deck missing a pipeline chart, a marketplace deck missing a liquidity metric — each is an instant VC disqualification.\n\n## Slide Patterns (layout canon)\n\nPatterns are **layout geometry**; recipes below are **narrative intent**. A slide picks one pattern for its visual shape (6 canonical ones below) and one recipe for what it argues (cover \u002F problem \u002F traction \u002F ...). Multiple recipes can share one pattern — Problem \u002F Why-Now \u002F Traction-callout all lean on the 3-stat row (C.2). Pick the pattern first, then fill it with recipe content.\n\n**Speaker notes rule.** Every content slide (non-cover, non-closing) MUST carry speaker notes via `officecli add \"$FILE\" \u002Fslide[N] --type notes --prop text='…'`. Missing notes = not shippable — inherits pptx v2 §Hard rules (H7). Run `officecli help pptx notes` to confirm prop names before building.\n\n**Pattern reuse discipline.** Never run the same pattern on two consecutive slides — even with different data, two identical geometries in a row read as a template loop. Alternate C.2 with C.4 or C.5b to break rhythm.\n\n**Vertical centering.** When a slide carries fewer elements than the pattern's maximum, nudge y-positions down 2–3cm to center the visual weight. Tables below assume full content.\n\n### C.1 Title \u002F Cover (dark gradient)\n\n3–4 text shapes on a gradient fill. Slide 1 in every deck.\n\n```\n+----------------------------------+\n|                                  |\n|          TITLE (centered)        |\n|          tagline                 |\n|                                  |\n|   round · amount · date          |\n|  ________________________        |  \u003C- thin brand band\n+----------------------------------+\n```\n\n| Element | X | Y | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Title | 2cm | 5cm | 29.87cm | 4cm | serif bold, ≥ 36pt (44 typical) |\n| Tagline | 2cm | 10cm | 29.87cm | 2cm | sans 18–22pt |\n| Meta (round · $ · date) | 2cm | 13cm | 29.87cm | 1.5cm | sans 12–16pt |\n\n**Use this when** the slide is the first one (Cover recipe 1) — 3-second identity grab. Background is a 180° linear gradient between two dark palette shades (e.g. Professional Navy `1E2761 → 0D1F35`). If the title wraps to 2 lines, **add height (4cm → 5cm), never drop font below 36pt** — sub-36pt on a pitch cover reads as timid regardless of content. Transition: fade.\n\n### C.2 3-Stat callout row\n\nTitle + 3 big-number \u002F label pairs across. The default for Problem \u002F Why-Now \u002F Traction-callout slides.\n\n```\n+----------------------------------+\n|  Title                           |\n|                                  |\n|   73%      12hr      $4.2B       |\n|   label    label     label       |\n|   source   source    source      |\n+----------------------------------+\n```\n\n| Element | X | Y | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Title | 1.5cm | 1cm | 30.87cm | 3cm | serif bold ≥ 36pt |\n| Stat 1 number | 2cm | 5cm | 9cm | 4cm | serif bold 60–64pt |\n| Stat 1 label | 2cm | 9.5cm | 9cm | 2cm | sans ≥ 16pt (H4 floor) |\n| Stat 2 number \u002F label | 12.5cm | (same) | 9cm | (same) | (same) |\n| Stat 3 number \u002F label | 23cm | (same) | 9cm | (same) | (same) |\n\n**Use this when** you have 2–3 anchoring numbers and the story is \"three facts argue the point\" — Problem, Why-Now, Market-callout, single-row Traction. Labels ≥ 16pt is the H4 floor (sub-label exception); a number without a label reads as bravado, so never drop labels to 12–14pt to fit more text.\n\n### C.3 4-Stat callout row\n\nSame geometry as C.2 but 4 columns. Numbers 60pt, width 7cm each.\n\n```\n+-------------------------------------+\n|  Title                              |\n|                                     |\n|  73%   12hr   $9M   4.2x            |\n|  lbl   lbl    lbl   lbl             |\n+-------------------------------------+\n```\n\n| Element | X positions | Y | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Title | 1.5cm | 1cm | 30.87cm | 3cm | serif bold 36pt |\n| Stat numbers | 1.5 \u002F 9.5 \u002F 17.5 \u002F 25.5cm | 5cm | 7cm | 4cm | serif bold 60pt |\n| Stat labels | (same X) | 9.5cm | 7cm | 2cm | sans ≥ 16pt |\n\n**Use this when** exactly 4 parallel metrics tell the story and 3 feels under-counted. Prefer C.2 if in doubt — 4 always feels tighter than 3, and wrap risk is real.\n\n> **Wrap warning.** At 60pt in 7cm width, dollar patterns with both `$` and `.` fail: `$9.4M` is 5 glyphs but the wide `$` and `.` in a serif bold make it wrap to 2 lines and destroy the callout. Safe dollar shapes at 60pt\u002F7cm: `$9M`, `$96B`, `$4K` (3–4 chars). Non-dollar shapes: `340%`, `4.2x`, `12.3` safe up to 5 chars. Values ≥ 6 chars (`197min`, `3 Days`) will wrap — either (a) drop font to 44–48pt, (b) abbreviate (`197m`, `$9M`), or (c) shift to C.2 (9cm per stat). Single tokens only, no internal spaces.\n\n### C.4 Chart + Context (chart left, stats right)\n\nChart takes left 55%, 2–3 stacked callouts on the right. The default for Traction \u002F Financials \u002F Market-sizing-with-context.\n\n```\n+-------------------------------------+\n|  Title                              |\n|                                     |\n|  +---------------+   +--------+     |\n|  |               |   | Stat 1 |     |\n|  |    chart      |   +--------+     |\n|  |               |   | Stat 2 |     |\n|  +---------------+   +--------+     |\n+-------------------------------------+\n```\n\n| Element | X | Y | Width | Height |\n|---|---|---|---|---|\n| Title | 2cm | 1cm | 29.87cm | 3cm |\n| Chart | 2cm | 4cm | 17cm | 13cm |\n| Stats column | 21cm | 4cm+ | 11cm | 2.5cm number + 1.5cm label (~3.7cm per pair) |\n\nSub-labels ≥ 16pt (H4 floor). For 5 stats stacked, drop number size to 44pt; 6+ stats means pick a different pattern. Post-batch for column\u002Fbar charts: `officecli set \"$FILE\" \"\u002Fslide[N]\u002Fchart[1]\" --prop gap=80` to tighten bar spacing.\n\n**Use this when** one primary chart drives the story and 2–3 numeric anchors reinforce it — Traction (ARR curve + current ARR + YoY + NRR), Financials (4-year column chart + assumption callouts), Market (bar chart + SOM \u002F CAGR \u002F methodology).\n\n### C.5 Icon-in-circle grid (3-row vertical)\n\n3 vertical rows, each = circle icon on the left + title + 1-line description.\n\n```\n+---------------------------------------+\n|  Title                                |\n|                                       |\n|  (o)  Label one                       |\n|       description one                 |\n|                                       |\n|  (o)  Label two                       |\n|       description two                 |\n|                                       |\n|  (o)  Label three                     |\n|       description three               |\n+---------------------------------------+\n```\n\n| Element | X | Y positions | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Icon circle | 2cm | 4.5 \u002F 8.5 \u002F 12.5cm | 2.5cm | 2.5cm | ellipse, accent fill |\n| Label | 5.5cm | (icon Y + 0) | 25cm | 1.2cm | sans bold 18pt |\n| Description | 5.5cm | (icon Y + 1.3cm) | 25cm | 1.8cm | sans ≥ 16pt (H4 floor), muted |\n\n**Use this when** you have 3 short vertical points that benefit from a visual anchor per row — Solution mechanism, Value pillars, Product loop. Choose C.5b (2×2 grid) when items are parallel and you have exactly 4; choose a horizontal 5-across variant when icons should read side-by-side (e.g. 5-step process).\n\n### C.5b 2×2 Feature grid (4 parallel items)\n\n4 rounded cards, 2 columns × 2 rows. Use when you have exactly 4 parallel items (product pillars, service types, feature quadrants).\n\n```\n+-----------------------------+\n|  Title                      |\n|                             |\n|  +---------+  +---------+   |\n|  | (o) T1  |  | (o) T2  |   |\n|  | body    |  | body    |   |\n|  +---------+  +---------+   |\n|  +---------+  +---------+   |\n|  | (o) T3  |  | (o) T4  |   |\n|  | body    |  | body    |   |\n|  +---------+  +---------+   |\n+-----------------------------+\n```\n\n| Element | X | Y | Width | Height | Font \u002F size |\n|---|---|---|---|---|---|\n| Slide title | 2cm | 1cm | 29.87cm | 2.5cm | serif bold 32pt |\n| Card 1 bg (top-left) | 1.5cm | 4cm | 14.5cm | 7cm | roundRect |\n| Card 2 bg (top-right) | 17.5cm | 4cm | 14.5cm | 7cm | roundRect |\n| Card 3 bg (bottom-left) | 1.5cm | 12cm | 14.5cm | 7cm | roundRect |\n| Card 4 bg (bottom-right) | 17.5cm | 12cm | 14.5cm | 7cm | roundRect |\n| Icon ellipse (each card) | card_x + 0.5cm | card_y + 0.5cm | 2cm | 2cm | — |\n| Card title (each) | card_x + 3.2cm | card_y + 0.6cm | 10.5cm | 1.8cm | sans bold 16pt |\n| Card body (each) | card_x + 0.5cm | card_y + 3cm | 13cm | 3.5cm | sans ≥ 16pt (H4 floor) |\n\n**Use this when** you have exactly 4 parallel items and the eye should land on each equally — 4 product pillars, 4 service tiers, 4 stakeholder types. 3 items feel lonely in a 2×2; 5+ items break the grid — go to a 3×2 (see pptx v2 §(d) grid math) or C.5 row pattern.\n\n> **Z-order canon (critical).** Each card's `roundRect` background must be added immediately before that card's icon \u002F title \u002F body shapes in the batch JSON — pptx paints in insertion order, so a background added after its text paints over and hides the text. When building with `officecli batch`, follow the per-card sequence `bg → ellipse → title → body` strictly. Pattern and z-order details → see pptx v2 §Recipe (c) z-order canon; reuse grid math from pptx v2 §(d) for non-2×2 counts.\n\n**Dark-background variant.** Change card fill from `F0F4F8` (light) to a lighter-dark shade like `1A2540` and bump body text to `FFFFFF` \u002F `E8E8E8`. Palette variables (e.g. `$MUTED`) do NOT expand inside single-quoted heredocs — write the literal hex (`64748B`) in the JSON.\n\n---\n\n## Key-slide recipes (10 essentials)\n\nThe 10 slides every pitch deck carries. Each recipe below gives: **visual outcome** (what the slide looks like from 3m away) + **runnable block** (≤ 18 lines) + **QA one-liner**. All recipes inherit pptx v2 palettes, grid math, type hierarchy, and `--prop tailEnd=triangle` on every connector. Recipes reference the Slide Patterns above: Cover reuses C.1; Problem \u002F Why-Now reuse C.2; Traction \u002F Financials reuse C.4; Feature \u002F pillar slides reuse C.5b. `$FILE` is your deck file.\n\n**Long-title wrap rule.** A 36pt+ title that wraps to 2 lines: add `height` (e.g. 2cm → 3.5cm) — never drop the font below 36pt. Titles \u003C 36pt on a pitch deck read as timid regardless of content.\n\n> **Chart `series1.color=` on `add` works** (applies to every chart recipe below). Passing `--prop series1.color=` (or `series2.color=`, …) on chart `add` applies the series color and exits 0. Verify with a readback if you like: `officecli get \"$FILE\" \"\u002Fslide[N]\u002Fchart[1]\u002Fseries[1]\" --json | jq '.data.results[0].format.color'`.\n\n### (1) Cover slide — company · tagline · round · date\n\n**Visual outcome.** Dark navy fill, centered 44pt company name, 20pt one-line tagline underneath, small 16pt meta line at the bottom with round + amount + date. Thin brand band at the very bottom (0.5cm high) in the accent color.\n\n```bash\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=1E2761\nofficecli add \"$FILE\" \"\u002Fslide[1]\" --type shape --prop name=BrandBand \\\n  --prop geometry=rect --prop fill=CADCFC \\\n  --prop x=0cm --prop y=18.5cm --prop width=33.87cm --prop height=0.55cm\nofficecli add \"$FILE\" \"\u002Fslide[1]\" --type shape --prop name=CoverTitle --prop text=\"Acme DevOps\" \\\n  --prop x=2cm --prop y=7cm --prop width=29.87cm --prop height=3cm \\\n  --prop font=Georgia --prop size=44 --prop bold=true --prop color=FFFFFF --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[1]\" --type shape --prop name=Tagline --prop text=\"Kubernetes observability, built for production at scale\" \\\n  --prop x=2cm --prop y=10.5cm --prop width=29.87cm --prop height=1.5cm \\\n  --prop font=Calibri --prop size=20 --prop color=CADCFC --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[1]\" --type shape --prop name=CoverMeta --prop text='Series B · $35M · April 2026' \\\n  --prop x=2cm --prop y=15cm --prop width=29.87cm --prop height=1.2cm \\\n  --prop font=Calibri --prop size=16 --prop color=FFFFFF --prop align=center --prop fill=none\n```\n\n**QA.** Cover has 4 discrete elements (brand band + title + tagline + meta). 80%-whitespace covers fail the pptx \"cover ≥ 60% filled\" floor.\n\n**Consumer variant (3-second grab).** Consumer decks (B2C app \u002F hardware \u002F D2C) should add a single dominant motif — hero product shot, oversized company name (60–96pt), or symbolic mark (crescent moon \u002F abstract geometric). Replace the 44pt title with an 80–96pt name + one motif shape (`--type shape --prop geometry=ellipse --prop fill=\u003Caccent>` for an abstract mark, or `picture` at ~40% of slide for a product hero). Keep tagline + round + date identical. SaaS \u002F B2B may skip — the typographic-only cover is sufficient.\n\n### (2) Problem slide — industry pain in 1 sentence + 3 data cards\n\n**Visual outcome.** 36pt title stating the pain (not \"The Problem\"). Below, three equal-width data cards across the slide: each a giant number (40pt) + one-line qualifier (16pt) + source footnote (12pt gray).\n\nGrid math for 3 cards, 1.5cm margins, 0.76cm gap: `usable = 33.87 − 3 − 2·0.76 = 29.35`, `col_width = 29.35 \u002F 3 = 9.78cm`. x-positions: `1.5 \u002F 12.04 \u002F 22.58`.\n\n```bash\nSLIDE=2  # second slide, after cover. Adjust from your build order.\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Kubernetes debugging burns 12 engineering hours \u002F incident\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2.5cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\ncat \u003C\u003CEOF | officecli batch \"$FILE\"\n[\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"name\":\"PC1\",\"geometry\":\"roundRect\",\"fill\":\"F5F7FA\",\"x\":\"1.5cm\",\"y\":\"5cm\",\"width\":\"9.78cm\",\"height\":\"10cm\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"73%\",\"x\":\"1.5cm\",\"y\":\"6cm\",\"width\":\"9.78cm\",\"height\":\"3cm\",\"font\":\"Georgia\",\"size\":\"60\",\"bold\":\"true\",\"color\":\"1E2761\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"of incidents take > 1 hour to diagnose\",\"x\":\"1.5cm\",\"y\":\"9.5cm\",\"width\":\"9.78cm\",\"height\":\"3cm\",\"font\":\"Calibri\",\"size\":\"18\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Source: 2025 DORA Report\",\"x\":\"1.5cm\",\"y\":\"13cm\",\"width\":\"9.78cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"12\",\"italic\":\"true\",\"color\":\"666666\",\"align\":\"center\",\"fill\":\"none\"}}\n]\nEOF\n# Repeat the 4-block pattern at x=12.04cm and x=22.58cm for cards 2 and 3.\n```\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"Source\")'` returns ≥ 3 (every claim carries a source). If zero sources, VCs will not trust a single number.\n\n### (2b) Why Now slide — Consumer \u002F Seed \u002F early A must-have\n\n**Visual outcome.** 3 cards across: each = **trigger headline** (24pt bold) + **data point** (60pt number or date) + **one-line implication** (16pt) + **source footnote** (12pt gray). Reuse Problem grid math (`col=9.78cm`, x = `1.5 \u002F 12.04 \u002F 22.58`). §赛道 Consumer row 2 must-have; Seed \u002F early A in any vertical benefits when \"market window\" IS the thesis.\n\n```bash\nSLIDE=3\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Why now: three converging triggers\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2.5cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\n# Card 1 (x=1.5cm) — trigger \u002F data \u002F implication \u002F source. Repeat at x=12.04cm and x=22.58cm.\ncat \u003C\u003CEOF | officecli batch \"$FILE\"\n[\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"geometry\":\"roundRect\",\"fill\":\"F5F7FA\",\"x\":\"1.5cm\",\"y\":\"5cm\",\"width\":\"9.78cm\",\"height\":\"10cm\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"BOM cost\",\"x\":\"1.5cm\",\"y\":\"5.5cm\",\"width\":\"9.78cm\",\"height\":\"1.2cm\",\"font\":\"Calibri\",\"size\":\"24\",\"bold\":\"true\",\"color\":\"1E2761\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"−90%\",\"x\":\"1.5cm\",\"y\":\"7cm\",\"width\":\"9.78cm\",\"height\":\"3cm\",\"font\":\"Georgia\",\"size\":\"60\",\"bold\":\"true\",\"color\":\"B85042\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Wearable BOM fell 90% since 2021; sub-$40 retail now viable\",\"x\":\"1.5cm\",\"y\":\"11cm\",\"width\":\"9.78cm\",\"height\":\"2cm\",\"font\":\"Calibri\",\"size\":\"16\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Source: IDC Wearables Teardown 2025\",\"x\":\"1.5cm\",\"y\":\"13.5cm\",\"width\":\"9.78cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"12\",\"italic\":\"true\",\"color\":\"666666\",\"align\":\"center\",\"fill\":\"none\"}}\n]\nEOF\n# Card 2 pattern: Oura IPO 2024 \u002F +$2.4B valuation \u002F category proven. Card 3: On-device LLM (Llama 3.2) \u002F Q4-24 \u002F privacy moat viable.\n```\n\n**QA.** 3 cards, each with a date\u002Fyear citation in the source footnote, each card ≤ 30 words. `officecli query \"$FILE\" 'shape:contains(\"2024\")'` + `'shape:contains(\"2025\")'` ≥ 2 combined (timing anchors visible).\n\n### (3) Solution slide — product in one sentence + 3-step \"how it works\"\n\n**Visual outcome.** 36pt title naming the product pattern (not \"Our Solution\"). Below: 3 or 4 rounded boxes horizontally at y=7cm with elbow connectors + triangle arrowheads. Each box = one verb (observe \u002F correlate \u002F resolve). Reuse pptx Recipe (c) flowchart — orchestration, not a new primitive.\n\n```bash\n# Title — \"a product pattern, not a brand slogan\".\n# Good: \"Auto-correlate K8s events across 3 data planes in 90 seconds\"\n# Bad:  \"The future of observability\"\nSLIDE=4\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop name=SolTitle \\\n  --prop text=\"Correlate K8s events across 3 data planes in 90 seconds\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2.2cm \\\n  --prop font=Georgia --prop size=32 --prop bold=true --prop color=1E2761 --prop fill=none\n# 3 boxes across: gap = (33.87 − 3 − 3·7) \u002F 2 = 4.93cm; x = 1.5, 13.43, 25.36\n# Connectors + arrowheads: --prop tailEnd=triangle ALWAYS (pptx Known Issues C-P-5..6).\n# Full batch block → see pptx v2 §Creating and Editing (c) 4-step flowchart; swap N from 4 boxes to 3.\n```\n\n**Product-pattern title rule.** The solution title is a verb + differentiated mechanism + metric. \"Observe \u002F Correlate \u002F Resolve\" is generic; VCs read it as any APM vendor. \"Correlate K8s events across 3 data planes in 90 seconds\" is specific; VCs read it as an insight.\n\n**QA.** Count connectors: `officecli query \"$FILE\" 'connector' --json | jq '.data.results | length'` ≥ (step_count − 1). Every connector must have `tailEnd=triangle` — `view annotated` confirms arrowhead direction. Title must be ≤ 12 words (one breath).\n\n### (4) Market slide — TAM \u002F SAM \u002F SOM nested columns\n\n**Visual outcome.** 36pt title \"Market: $X.YB growing Z% CAGR\". Below: three horizontal bars (or three stacked nested rectangles), labeled TAM \u002F SAM \u002F SOM with dollar values + growth rate. Bottom footnote cites **top-down vs bottom-up source** — pick one methodology per deck, don't mix.\n\n```bash\n# Use a pptx column chart with 3 values. Categories = TAM,SAM,SOM. Source annotation is a separate shape.\nSLIDE=5\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"$42B observability market, 18% CAGR\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type chart --prop chartType=bar \\\n  --prop series1.name=\"USD (billions)\" --prop series1.values=\"42,8.4,0.62\" --prop series1.color=1E2761 \\\n  --prop categories=\"TAM,SAM,SOM (5-yr)\" \\\n  --prop x=2cm --prop y=4cm --prop width=22cm --prop height=12cm \\\n  --prop title='Market sizing — bottom-up by enterprise count × ACV'\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='Source: Gartner 2025 APM Magic Quadrant; SAM = 20% of TAM (K8s-first shops); SOM = 7.4% of SAM over 5 years at 18-24% share.' \\\n  --prop x=2cm --prop y=16.5cm --prop width=29.87cm --prop height=2cm \\\n  --prop font=Calibri --prop size=12 --prop italic=true --prop color=666666 --prop fill=none\n```\n\n**QA.** Top-down vs bottom-up MUST be declared in the source footnote. A TAM without methodology reads as fabricated.\n\n### (5) Product slide — screenshot + 3 bullets OR 3-card feature grid\n\n**Visual outcome.** Two layout options: (a) hero product screenshot on the left (60% of slide), 3 one-line feature bullets on the right (each ≥ 18pt body, no bullets under bullets). (b) 3 feature cards with one icon \u002F screenshot thumbnail each. Pick (a) for consumer \u002F app products, (b) for B2B \u002F infrastructure.\n\n```bash\n# (a) screenshot + bullets — consumer pattern\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type picture --prop src=product_hero.png \\\n  --prop x=1cm --prop y=4cm --prop width=18cm --prop height=13cm\nofficecli set \"$FILE\" \"\u002Fslide[$SLIDE]\u002Fpicture[1]\" --prop alt=\"Product UI: dashboard with 12 K8s clusters, live correlation graph\"\n# Right column bullets (each as a separate shape so sizes stay explicit)\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Auto-correlate across 3 data planes\" \\\n  --prop x=20cm --prop y=5cm --prop width=12cm --prop height=1.5cm \\\n  --prop font=Calibri --prop size=20 --prop bold=true --prop color=1E2761 --prop fill=none\n# Repeat for bullets 2 and 3 at y=7.5cm \u002F y=10cm.\n```\n\n**QA.** Picture alt text present (`query 'picture:no-alt'` = empty). Bullets each ≥ 18pt. No \"Lorem\"\u002F\"product name here\"\u002F`{{...}}` tokens.\n\n### (6) Business model slide — unit econ or revenue model\n\n**Visual outcome.** Decision tree by vertical:\n- **SaaS \u002F Enterprise (Series A+)** — 4 KPI callouts: CAC \u002F LTV \u002F Payback \u002F GM (reuse pptx Recipe (e)).\n- **Consumer \u002F D2C** — AOV · repeat-purchase rate · contribution margin · blended CAC.\n- **Marketplace** — GMV \u002F take-rate \u002F liquidity metric \u002F cohort retention.\n- **Bio \u002F Deep tech** — revenue model (license \u002F milestone \u002F royalty split) with assumed ranges.\n\nTitle names the dominant metric (e.g. \"LTV:CAC 4.7x · 14-month payback · 78% gross margin\"), not \"Business Model\". Full 4-card batch block → see pptx v2 §(e) KPI callouts.\n\n```bash\n# SaaS pattern: KPI card values + sub-label + gray VC-floor context under each.\n# Card 1 (LTV): big number \"$420K\", sub \"Lifetime value\", context \"floor: ARPU × GM \u002F churn\"\n# Card 2 (CAC): big number \"$90K\",  sub \"Acquisition cost\", context \"fully-loaded S&M spend\"\n# Card 3 (Payback): big number \"14 mo\", sub \"CAC payback\", context \"VC floor: \u003C 18 mo\"\n# Card 4 (GM): big number \"78%\", sub \"Gross margin\", context \"SaaS floor: 70%+\"\n# Grid math for 4 cards across: usable = 33.87 − 3 − 3·0.76 = 28.59, col = 7.15cm\n# → Full batch template → pptx v2 §(e). Adapt card count 3→4 and card width 9.78cm→7.15cm.\n```\n\n**QA.** For Series B+, all four of {CAC, LTV, payback, GM} present: `officecli query \"$FILE\" 'shape:contains(\"CAC\")'` ≥ 1 AND `shape:contains(\"LTV\")'` ≥ 1 AND `shape:contains(\"payback\")'` ≥ 1 AND `shape:contains(\"gross margin\")'` ≥ 1.\n\n### (7) Traction slide — ARR curve that starts at 0\n\n**Visual outcome.** Line chart taking 60% of slide width; ARR on y-axis **starting at 0** (not at 80% of current value — the VC hockey-stick lie). Right-side commentary card: single giant number (current ARR) + growth rate + 2-3 milestones. If Series B+, second row: cohort retention snippet or logo wall.\n\n```bash\nSLIDE=7\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='ARR: $0 → $18M in 24 months' \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type chart --prop chartType=line \\\n  --prop series1.name=ARR --prop series1.values=\"0.2,0.6,1.4,3.2,6.1,11.3,15.8,18.0\" --prop series1.color=1E2761 \\\n  --prop categories=\"Q1-24,Q2-24,Q3-24,Q4-24,Q1-25,Q2-25,Q3-25,Q4-25\" \\\n  --prop x=1.5cm --prop y=4cm --prop width=21cm --prop height=13cm \\\n  --prop title='Quarterly ARR ($M) — y-axis anchored at 0' \\\n  --prop axismin=0\n# Right callout\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop geometry=roundRect --prop fill=1E2761 --prop line=none \\\n  --prop x=23.5cm --prop y=4cm --prop width=8.8cm --prop height=13cm\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='$18M' \\\n  --prop x=23.5cm --prop y=5cm --prop width=8.8cm --prop height=3cm \\\n  --prop font=Georgia --prop size=64 --prop bold=true --prop color=FFFFFF --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"ARR · +312% YoY · NRR 128%\" \\\n  --prop x=23.5cm --prop y=9cm --prop width=8.8cm --prop height=3cm \\\n  --prop font=Calibri --prop size=18 --prop color=CADCFC --prop align=center --prop fill=none\n```\n\n**`--prop axismin=0` is load-bearing** — without it, pptx auto-scales the y-axis to start near the lowest value. That is the hockey-stick lie. Gate 6 greps this below.\n\n**QA.** ARR curve chart must carry `axismin=0`. `officecli get \"$FILE\" \"\u002Fslide[$SLIDE]\u002Fchart[1]\" --json | jq .format.axisMin` returns `0` (CLI emits camelCase `axisMin` in readback even though input prop is lowercase `axismin`).\n\n### (8) Team slide — avatars + names + prior companies (not just a wall)\n\n**Visual outcome.** 3- or 4-card row across the middle of the slide. Each card: picture (6×6cm) on top; name (20pt bold); role (16pt); **prior company + title** (16pt italic, 1 key line); optional LinkedIn URL footer (12pt). Team slide with just headshots and names reads as amateur.\n\n```bash\nSLIDE=11\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Team: 3 prior exits, 42 years combined K8s\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\n# Card 1 — CEO\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type picture --prop src=alice.jpg \\\n  --prop x=2cm --prop y=5cm --prop width=6cm --prop height=6cm\nofficecli set \"$FILE\" \"\u002Fslide[$SLIDE]\u002Fpicture[1]\" --prop alt=\"Alice Chen, CEO — portrait\"\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Alice Chen\" \\\n  --prop x=2cm --prop y=11.5cm --prop width=6cm --prop height=1cm \\\n  --prop font=Georgia --prop size=20 --prop bold=true --prop color=1E2761 --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"CEO\" \\\n  --prop x=2cm --prop y=12.8cm --prop width=6cm --prop height=0.8cm \\\n  --prop font=Calibri --prop size=16 --prop color=333333 --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"ex-Datadog Director (Series C → IPO); led K8s observability GTM $40M → $200M ARR\" \\\n  --prop x=2cm --prop y=13.8cm --prop width=6cm --prop height=2.5cm \\\n  --prop font=Calibri --prop size=14 --prop italic=true --prop color=333333 --prop align=center --prop fill=none\n# Repeat for Card 2 (CTO, x=10cm) and Card 3 (VP Eng, x=18cm) — 3 cards × 5-6 shapes each.\n```\n\nPrior companies carry **credibility density**. VCs read \"ex-Datadog Director + led $40M → $200M\" in 2 seconds; they read \"co-founder, passionate\" in 0 seconds (because they skip it). Advisors, if shown, go in a smaller row below with a single logo each.\n\n**Arrangement helper.** 3 cards: `col=9.78cm, x=1.5\u002F12.04\u002F22.58`. 4 cards: `col=7.15cm, x=1.5\u002F9.41\u002F17.32\u002F25.23`. 5 cards: `col=5.85cm, x=1.5\u002F7.75\u002F14.0\u002F20.25\u002F26.5` (0.4cm gap, tighter). 6+ or asymmetric → 2-row grid (3×2 \u002F 3×3); see pptx v2 §(d) grid math.\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"ex-\")'` + `'shape:contains(\"prior\")'` + `'shape:contains(\"former\")'` ≥ 1 per team member. If zero, you have a portfolio, not a team.\n\n### (9) Financials slide — 4-year plan + honest assumptions\n\n**Visual outcome.** Column chart: 4 years × (revenue, gross margin $, EBITDA). Right-side card: 3-bullet assumption panel (ARPU assumption, win-rate assumption, churn assumption). Title names the trajectory (\"$18M → $85M by FY29\"), not \"Financial Projections\".\n\nReuse pptx Recipe (b) chart + commentary. Pitch-specific: ASSUMPTIONS column on the right is **load-bearing** — a 4-year plan without visible assumptions reads as aspirational. VCs will ask what's behind every number anyway; surface it.\n\nLeft 2\u002F3 — slide + title + 3-series column chart:\n\n```bash\nSLIDE=17\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='$18M → $85M ARR by FY29' \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type chart --prop chartType=column \\\n  --prop series1.name=\"Revenue ($M)\"  --prop series1.values=\"18,34,58,85\" --prop series1.color=1E2761 \\\n  --prop series2.name=\"Gross Margin ($M)\" --prop series2.values=\"14,26,45,68\" --prop series2.color=CADCFC \\\n  --prop series3.name=\"EBITDA ($M)\"   --prop series3.values=\"-6,-2,8,22\" --prop series3.color=B85042 \\\n  --prop categories=\"FY26,FY27,FY28,FY29\" \\\n  --prop x=1.5cm --prop y=4cm --prop width=20cm --prop height=13cm \\\n  --prop title='4-year plan — revenue, GM, EBITDA ($M)'\n```\n\nRight 1\u002F3 — assumptions commentary card:\n\n```bash\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop geometry=roundRect --prop fill=F5F7FA --prop line=none \\\n  --prop x=22.5cm --prop y=4cm --prop width=9.8cm --prop height=13cm\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Key Assumptions\" \\\n  --prop x=23cm --prop y=4.5cm --prop width=8.8cm --prop height=1.2cm \\\n  --prop font=Georgia --prop size=20 --prop bold=true --prop color=1E2761 --prop fill=none\n# 5 assumption bullets as 5 separate paragraph shapes at y=6, 7.5, 9, 10.5, 12cm — size=14, italic=true.\n# Keep each bullet ≤ 14 words so 8.8cm width fits without wrap.\n```\n\n**Assumptions panel is load-bearing.** A 4-year plan without visible assumptions reads as aspirational. VCs ask what's behind every number anyway — surface the three or four assumptions that drive the curve.\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"assumption\")'` OR `'shape:contains(\"Assumes\")'` ≥ 1. If zero, add the panel.\n\n### (10) The Ask — hero number + 4-bucket Use-of-Funds + runway\n\n**Visual outcome.** Dark fill (match cover). Hero number in the center top: `$35M` at 96pt white. Below, a 4-bucket pie OR a 4-card row listing **Engineering 40% \u002F GTM 35% \u002F G&A 15% \u002F Reserve 10%**. Bottom line: \"18-month runway to $40M ARR\" (next milestone, not \"until next round\").\n\n```bash\nSLIDE=20\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=1E2761\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='$35M Series B' \\\n  --prop x=2cm --prop y=2cm --prop width=29.87cm --prop height=4cm \\\n  --prop font=Georgia --prop size=88 --prop bold=true --prop color=FFFFFF --prop align=center --prop fill=none\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type chart --prop chartType=pie \\\n  --prop series1.name=\"Use of Funds\" --prop series1.values=\"40,35,15,10\" \\\n  --prop categories=\"Engineering,Go-to-Market,G&A,Reserve\" \\\n  --prop colors=\"CADCFC,B85042,97BC62,FFFFFF\" \\\n  --prop x=6cm --prop y=7cm --prop width=12cm --prop height=10cm \\\n  --prop title=\"Use of Funds — 4 buckets\"\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='18 months runway to $40M ARR and Series C' \\\n  --prop x=2cm --prop y=17cm --prop width=29.87cm --prop height=1.5cm \\\n  --prop font=Calibri --prop size=22 --prop color=CADCFC --prop align=center --prop fill=none\n```\n\n**4-bucket convention.** Engineering \u002F GTM \u002F G&A \u002F Reserve is the canonical breakdown. Typical Series A ranges: Eng 40-50%, GTM 30-40%, G&A 10-15%, Reserve 5-10%. Series B shifts 5-10 points from Eng to GTM.\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"Use of Funds\")'` ≥ 1. Pie chart present on ask slide. Runway + milestone on ask slide.\n\n### (11) Pipeline chart — Bio \u002F Deep Tech must-have\n\n**Visual outcome.** Horizontal swimlane. Left column = candidate name; 4 stage columns to the right (Preclinical \u002F Ph1 \u002F Ph2 \u002F Ph3 for bio — or TRL1-3 \u002F TRL4-6 \u002F TRL7-8 \u002F TRL9 for deep tech). Each row's bar extends to its current stage; darker fill for later stages. NCT \u002F trial-ID footer below. §赛道 row 5 Bio must-have; SaaS \u002F Consumer skip.\n\nGrid math: usable `= 30.87cm`, candidate col `= 7cm`, stage cols `= (30.87 − 7) \u002F 4 = 5.97cm` each, row height `= 2.3cm`. Stage col x: `8.5 \u002F 14.47 \u002F 20.44 \u002F 26.41`.\n\n```bash\nSLIDE=6\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Pipeline: 3 candidates across Ph1–Ph3\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\n# 4 stage headers + candidate row 1 (HLX-201 at Ph2, bar width = 3·5.97 = 17.91cm) in one batch.\ncat \u003C\u003CEOF | officecli batch \"$FILE\"\n[\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Preclinical\",\"x\":\"8.5cm\",\"y\":\"4cm\",\"width\":\"5.97cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"16\",\"bold\":\"true\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"F5F7FA\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Phase 1\",\"x\":\"14.47cm\",\"y\":\"4cm\",\"width\":\"5.97cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"16\",\"bold\":\"true\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"F5F7FA\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Phase 2\",\"x\":\"20.44cm\",\"y\":\"4cm\",\"width\":\"5.97cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"16\",\"bold\":\"true\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"F5F7FA\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"Phase 3\",\"x\":\"26.41cm\",\"y\":\"4cm\",\"width\":\"5.97cm\",\"height\":\"1cm\",\"font\":\"Calibri\",\"size\":\"16\",\"bold\":\"true\",\"color\":\"333333\",\"align\":\"center\",\"fill\":\"F5F7FA\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"text\":\"HLX-201 (lead)\",\"x\":\"1.5cm\",\"y\":\"5.5cm\",\"width\":\"7cm\",\"height\":\"1.5cm\",\"font\":\"Calibri\",\"size\":\"18\",\"bold\":\"true\",\"color\":\"1E2761\",\"align\":\"left\",\"fill\":\"none\"}},\n  {\"command\":\"add\",\"parent\":\"\u002Fslide[$SLIDE]\",\"type\":\"shape\",\"props\":{\"geometry\":\"roundRect\",\"fill\":\"1E2761\",\"x\":\"8.5cm\",\"y\":\"5.7cm\",\"width\":\"17.91cm\",\"height\":\"1.1cm\",\"line\":\"none\"}}\n]\nEOF\n# Repeat rows 2 & 3 at y=7.8cm \u002F y=10.1cm with bar widths per stage (Ph1=5.97cm, Ph1-Ph2=11.94cm, Ph1-Ph3=17.91cm).\n# NCT footer full-width at y=16.8cm.\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text='NCT05021323 (HLX-201, Ph2, n=48) · NCT06142091 (HLX-304, Ph1, n=24) · IND-filed Q1-26 for HLX-412' \\\n  --prop x=1.5cm --prop y=16.8cm --prop width=30.87cm --prop height=1.2cm \\\n  --prop font=Calibri --prop size=12 --prop italic=true --prop color=666666 --prop fill=none\n```\n\n**QA.** `officecli query \"$FILE\" 'shape:contains(\"NCT\")' --json | jq '.data.results | length'` ≥ 1. Bar colors darken across stages (`CADCFC` preclinical-only, `1E2761` Ph2-reached).\n\n### (12) Competitive comparison table — Series B+ essential\n\n**Visual outcome.** 5–7 rows × 4–6 cols. Column 1 = competitor name (optional logo shape beside); rest = differentiators (speed \u002F price \u002F integrations \u002F margin \u002F coverage). **Last row = your company, fill highlighted** in an accent color (CADCFC \u002F 97BC62); competitor rows gray. Every Series B+ deck needs this (SaaS: Datadog \u002F New Relic \u002F Splunk; Bio: Kite \u002F Novartis \u002F BMS).\n\n```bash\nSLIDE=13\nofficecli add \"$FILE\" \u002F --type slide --prop layout=blank --prop background=FFFFFF\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type shape --prop text=\"Competitive landscape\" \\\n  --prop x=1.5cm --prop y=1.2cm --prop width=30.87cm --prop height=2cm \\\n  --prop font=Georgia --prop size=36 --prop bold=true --prop color=1E2761 --prop fill=none\n# Inline table via --prop data= (per-cell r#c# is silently ignored \u002F not honored — use data=). Single-quote the data value — '$15\u002Fhost' would strip.\nofficecli add \"$FILE\" \"\u002Fslide[$SLIDE]\" --type table \\\n  --prop data='Competitor,Speed,Price,Integrations,Margin;Datadog,12 min,$15\u002Fhost,680,75%;New Relic,18 min,$25\u002Fhost,520,68%;Splunk,45 min,$45\u002FGB,310,62%;You (Acme DevOps),90 sec,$8\u002Fhost,1200,82%' \\\n  --prop style=medium1 --prop headerFill=1E2761 \\\n  --prop x=1.5cm --prop y=4cm --prop width=30.87cm --prop height=12cm\n# Highlight your row: loop over \u002Fslide[$SLIDE]\u002Ftable[1]\u002Ftr[5]\u002Ftc[1..5] and set cell fill to CADCFC.\n```\n\n**QA.** `officecli query \"$FILE\" 'table' --json | jq '.data.results | length'` ≥ 1. Row count ≥ 4 (you + ≥ 3 named competitors). Your row visually distinct via cell fill (Gate 5b visual check — table style alone does not highlight one row).\n\n## Numbers convention (pitch-specific)\n\nA terse convention table — **not a finance tutorial**. If you don't already know what these mean, pause the deck and ask the user for the values; don't guess.\n\n| Metric | Shape | Floor \u002F convention |\n|---|---|---|\n| **TAM** | `$X.YB`, one methodology | Either top-down (analyst report) or bottom-up (count × ACV). Never both; never neither. |\n| **SAM** | `$X.YB`, fraction of TAM you serve | Typically 15 – 30% of TAM for verticalized SaaS; higher for horizontal |\n| **SOM** | `$X.YB` at year N | Realistic 5-yr share: 5 – 15% of SAM for early stage |\n| **ARR** | MRR × 12. NOT revenue. | SaaS only; contracts on books, net of churn |\n| **MRR** | Monthly recurring | ARR \u002F 12; do not confuse with monthly revenue |\n| **NRR (Net Revenue Retention)** | %, trailing 12 mo | VC floor: > 100% acceptable, > 115% strong, > 130% exceptional |\n| **CAC** | $ fully-loaded | Sales + marketing spend \u002F new logos acquired |\n| **LTV** | $ | ARPU × gross margin × (1 \u002F churn rate) |\n| **LTV:CAC** | ratio | VC floor: 3x OK, > 4x strong, > 5x exceptional |\n| **CAC payback** | months | VC floor: \u003C 18 mo OK, \u003C 12 mo strong |\n| **Gross margin** | % | SaaS floor 70%, strong 80%+; marketplace 15-40%; hardware 30-50% |\n| **Burn \u002F runway** | $\u002Fmonth + months | Gross burn vs net burn — label which; runway to specific milestone |\n| **Use of Funds** | 4-bucket pie | Engineering \u002F Go-to-Market \u002F G&A \u002F Reserve — see Ask slide recipe |\n\n**Rule.** Every number on a deck carries a unit. `18%` or `18M` alone is ambiguous — write `$18M ARR` \u002F `18% NRR growth`. `TBD`, `coming soon`, `(fill in)`, `lorem`, `xxxx` in numeric slots = immediate VC disqualification. Gate 6 greps these below.\n\n## VC ship-check (6 red flags \u002F positive signals)\n\nWhat the VC reads in the first 30 seconds. Six one-line conditions — every \"FAIL\" below is an instant round-killer; fix before delivering.\n\n| # | Red flag (FAIL if present) | Positive signal (shipwise) |\n|---|---|---|\n| 1 | Cover without round + amount + date | `Company · tagline · Series X · $YM · Date` in 4 lines |\n| 2 | TAM > $100B without a cited source \u002F methodology | TAM clearly labeled bottom-up OR top-down with a visible 2024+ source |\n| 3 | Traction chart y-axis does not start at 0 (hockey-stick lie) | Line chart `axismin=0`; growth shape honest |\n| 4 | Team slide: headshots + names only, no prior companies | Every member: prior company + role + 1 achievement metric |\n| 5 | Ask slide missing Use-of-Funds breakdown | `$XM` hero + 4-bucket pie (Eng \u002F GTM \u002F G&A \u002F Reserve) + runway + next milestone |\n| 6 | `TBD` \u002F `lorem` \u002F `xxxx` \u002F `{{...}}` \u002F `(fill in)` anywhere | `view text` clean — zero placeholder tokens |\n\n**Common Series-specific failures.**\n- **Series A specific** — bottom-up TAM calculated from a fictional enterprise-count × ACV (no reference customers to anchor the count); `CAC \u002F LTV` shown with \u003C 12 months of data (statistically meaningless).\n- **Series B specific** — no unit-econ slide at all; CAC payback > 24 months without a \"we're pre-scale, here's the plan\" narrative; logo wall \u003C 8 customers.\n- **Series C specific** — no moat \u002F defensibility slide; revenue growth shown without margin trajectory; international expansion stated but no specific launch plan \u002F hires.\n\nThe Delivery Gate 6 block below executes checks 1–6 above via grep + query. Gate 5b fresh-eyes covers the visual judgments (hockey stick, team credibility) that grep can't see.\n\n## Traction triple-pattern (ARR + milestones + logos)\n\nFor Series B+, traction often spans 2 slides: one for the chart + callout (recipe 7 above), one for **milestone timeline + logo wall**. Timeline = 4-6 horizontal dates with one-line events. Logo wall = 12-20 customer logos in a 4×N or 5×N grid, muted monochrome so no single brand dominates.\n\n```bash\n# Milestone timeline: 5 dates as circles on a horizontal line at y=8cm.\n# Use pptx shapes (ellipse preset) + connectors (shape=straight) between them.\n# Each milestone = ellipse at y=8cm + date label above + event description below.\n# → See pptx v2 Recipe (d) row 9 (Roadmap timeline) for the canonical pattern.\n\n# Logo wall: pictures in a 5×N grid. Typical spacing: logo width = 5cm, height = 2cm, gap = 0.4cm.\n# grid math for 5 logos across, 1.5cm edge margin: usable = 33.87 − 3 − 4·0.4 = 29.27, col = 5.85cm\n# (use 5cm logo width centered in each 5.85cm column)\n```\n\n**QA.** Logo wall should have ≥ 8 logos for Series B+, ≥ 4 for Series A. Fewer = \"lighter than it looks\"; more than 20 = pixel noise.\n\n## QA — Delivery Gate (executable)\n\n**Assume there are problems.** First render is almost never correct. Pitch decks fail at two layers: **structural** (schema, token leaks — caught by pptx v2 Gates 1–3) and **narrative** (wrong stage, missing unit econ, TAM unsourced — the checks that make pptx v2 Gate 5b + Gate 6 indispensable). Every check must print its success message.\n\n### Gates 1–5a — inherited from pptx v2 verbatim\n\n→ see pptx v2 §Delivery Gate L637-679. Copy-paste the full block:\n\n- **Gate 1** — `validate` schema check (whitelist `ChartShapeProperties` warnings per C-P-2).\n- **Gate 2** — token leak via `view text` grep (`$xxx$`, `{{...}}`, `\u003CTODO>`, `lorem`, `xxxx`, empty `()`\u002F`[]`, `\\$`\u002F`\\t`\u002F`\\n` literals).\n- **Gate 3** — hyperlink `rPr` schema trap (C-P-1) — zero `\u003Ca:rPr>\u003Ca:hlinkClick>`.\n- **Gate 4** — slide-order sanity — cover first, dividers before sections, closing last.\n- **Gate 5a** — dark-on-dark contrast — every fill in `{1E2761, 0A1628, 8B1A1A, 2C5F2D, 36454F}` must declare near-white textColor. **This includes charts rendered on that fill**: chart `title.textColor`, `legend.textColor`, axis text default to dark and read as invisible on dark backgrounds — set them explicitly, or place the chart on a light card inside the dark slide.\n\nDo not skip or reorder these five. Every pptx-layer defect caught by Gates 1–5a also fires on pitch decks.\n\n**Gate 2b — pitch-specific shell-strip signatures (MANDATORY).** Gate 2 misses `$35M` that zsh silently stripped to empty (no residue to grep). Run this after Gate 2:\n\n```bash\n# $XXM stripped by zsh leaves bare \" M ARR\" \u002F \" M raised\" \u002F \"Series [A-C] · M\" patterns.\nSTRIP=$(officecli view \"$FILE\" text | grep -niE '(^|[^A-Za-z0-9])M (ARR|raised|Series|runway|round|raise)|Series [A-C] · M( |$)|runway · M|raised · M|raising ·? M')\n[ -z \"$STRIP\" ] && echo \"Gate 2b OK (no \\$-strip signatures)\" || { echo \"REJECT Gate 2b (likely zsh \\$-strip — re-issue with single quotes):\"; echo \"$STRIP\"; exit 1; }\n```\n\nFix: re-issue the offending `add`\u002F`set` with single quotes around the text value (`--prop text='Series B · $35M'`, not double quotes). The same strip hits **chart series names \u002F axis titles** (`--prop name=\"营收 ($M)\"` → legend shows `营收 ()`): single-quote every chart prop carrying `$`.\n\n### Gate 5b — Visual audit via HTML preview (MANDATORY, NOT optional)\n\nGates 1–5a are token-grep defenses. **They cannot see a rendered slide.** This step is the only visual-assembly check. Do not skip.\n\nRun `officecli view \"$FILE\" html` and Read the returned HTML. Walk every slide and answer, for EACH (inherits pptx v2 Gate 5b checklist; pitch-specific additions marked ⭐):\n\n- **overlap**: do any text shapes overlap each other or a chart?\n- **dark-on-dark**: is any text on a fill where fill brightness \u003C 30% AND text brightness \u003C 80%?\n- **divider overlap**: any giant decorative number (01\u002F02\u002F03 at 100pt+) colliding with the divider title text?\n- **order sanity**: does the slide sequence match your stage-appropriate narrative outline?\n- **missing arrowheads**: do flowchart\u002Fdecision-tree connectors show direction, or plain lines?\n- ⭐ **traction y-axis**: does every ARR \u002F revenue \u002F growth line chart start at 0 on the y-axis? (Not 80% of current — that is the hockey-stick lie.)\n- ⭐ **team credibility**: does every team-slide card show a prior company or prior title? (Cards with just headshot + name = reject.)\n- ⭐ **TAM \u002F market number credibility**: is the TAM under $100B for a niche market, or if ≥ $100B, is a methodology source cited? (A claimed `$500B TAM` with no source is an auto-reject red flag.)\n- ⭐ **Use-of-Funds pie**: does the ask slide carry a 4-bucket pie (Engineering \u002F GTM \u002F G&A \u002F Reserve) or a 4-card row with %s?\n- ⭐ **narrative completeness**: is the order cover → problem → solution → market → product → model → traction → team → financials → ask, or your stage-appropriate permutation from §Stage diagnosis?\n\n**Instruction.** Run `officecli view \"$FILE\" html` and Read the HTML. Walk every slide against the questions below. If rendering chart colors, animations, or zoom — those only show in the target viewer (PowerPoint \u002F Keynote \u002F WPS); ask the user to open `.pptx` directly for those runtime features.\n\n> For every slide:\n> (a) Are slides in VC narrative order (cover → problem → solution → market → product → model → traction → team → financials → ask, with your stage's adjustments)? Flag any out-of-sequence.\n> (b) Is every ARR \u002F revenue \u002F growth line chart y-axis anchored at 0? Flag hockey-stick visual lies.\n> (c) Does the team slide carry prior-company credentials for each person? (Not just headshot + name.)\n> (d) Does every TAM \u002F SAM \u002F SOM claim have a visible source or methodology?\n> (e) Does the ask slide have a 4-bucket Use of Funds (Engineering \u002F GTM \u002F G&A \u002F Reserve) and a specific next milestone + runway length?\n> (f) Any text overlap, dark-on-dark, off-slide geometry, missing arrowheads, placeholder tokens (`TBD` \u002F `lorem` \u002F `{{...}}` \u002F `xxxx` \u002F empty `()`)?\n\nReport every instance with slide number. If ANY defect — REJECT; do not deliver until fixed.\n\n**Human preview (optional).** If you want the user to visually preview the deck, run `officecli watch \"$FILE\"` for a live preview the user can open at their own discretion, or have them open the `.pptx` directly in PowerPoint \u002F WPS \u002F Keynote. For final visual verification, open the file in the target presentation viewer.\n\n### Gate 6 — Pitch narrative sanity (executable)\n\nPitch-specific checks that grep the deck for VC red flags. Every one is a token check — combine with Gate 5b's human read for full coverage.\n\n```bash\nFILE=\"deck.pptx\"\n\n# 6.1 — no TBD \u002F lorem \u002F placeholder tokens (stronger than Gate 2 — pitch-specific scope)\nLEAK=$(officecli view \"$FILE\" text | grep -niE 'TBD|lorem|\\(fill in\\)|xxxx|coming soon|placeholder')\n[ -z \"$LEAK\" ] && echo \"Gate 6.1 OK (no placeholder tokens)\" || { echo \"REJECT Gate 6.1:\"; echo \"$LEAK\"; exit 1; }\n\n# 6.2 — TAM \u002F SAM \u002F SOM presence (Series A+)\nTAM_HIT=$(officecli query \"$FILE\" 'shape:contains(\"TAM\")' --json | jq '.data.results | length')\n[ \"$TAM_HIT\" -ge 1 ] && echo \"Gate 6.2 OK (TAM slide present)\" || echo \"WARN Gate 6.2: no TAM mention — confirm stage is Seed \u002F Bridge if intentional\"\n\n# 6.3 — Unit econ presence (Series B+): CAC OR LTV OR payback\nCAC_HIT=$(officecli query \"$FILE\" 'shape:contains(\"CAC\")' --json | jq '.data.results | length')\nLTV_HIT=$(officecli query \"$FILE\" 'shape:contains(\"LTV\")' --json | jq '.data.results | length')\nif [ \"$CAC_HIT\" -ge 1 ] || [ \"$LTV_HIT\" -ge 1 ]; then\n  echo \"Gate 6.3 OK (unit econ surface)\"\nelse\n  echo \"WARN Gate 6.3: no CAC \u002F LTV — confirm stage Seed\u002FA if intentional, REJECT if Series B+\"\nfi\n\n# 6.4 — Use of Funds present on ask slide\nUOF_HIT=$(officecli query \"$FILE\" 'shape:contains(\"Use of Funds\")' --json | jq '.data.results | length')\n[ \"$UOF_HIT\" -ge 1 ] && echo \"Gate 6.4 OK (Use of Funds)\" || { echo \"REJECT Gate 6.4: ask slide missing Use of Funds\"; exit 1; }\n\n# 6.5 — Team prior-company signal (at least one of ex- \u002F former \u002F prior \u002F previously)\nPRIOR_HIT=$(officecli view \"$FILE\" text | grep -ciE '\\b(ex-|former|prior|previously)\\b')\n[ \"$PRIOR_HIT\" -ge 1 ] && echo \"Gate 6.5 OK (team prior-company)\" || { echo \"REJECT Gate 6.5: team slide has no prior-company credentials\"; exit 1; }\n\n# 6.6 — Traction chart y-axis anchored at 0 (at least one chart must set axismin=0, Series A+)\nAXISMIN_HIT=$(officecli query \"$FILE\" 'chart' --json | jq '[.data.results[]? | select(.format.axisMin == \"0\" or .format.axisMin == 0 or .format.axismin == \"0\" or .format.axismin == 0)] | length')\n[ \"$AXISMIN_HIT\" -ge 1 ] && echo \"Gate 6.6 OK (traction chart axisMin=0)\" || echo \"WARN Gate 6.6: no chart sets axisMin=0 — confirm no ARR\u002Frevenue line chart, or add --prop axismin=0\"\n\necho \"Delivery Gate 6 PASS (token + narrative checks) — proceed to Gate 5b fresh-eyes (MANDATORY)\"\n```\n\n**Readback key note.** CLI accepts lowercase `axismin` as input (on `--prop axismin=0`) but emits camelCase `axisMin` in `query --json` readback. The jq above accepts both for forward-compat.\n\nGate 6 is a grep floor. Gate 5b is the visual ceiling. Ship only when both print PASS.\n\n### Honest limit\n\n`validate` catches schema errors, not fundraising errors. A deck passes `validate` with a `$500B TAM` on a $10M market, a team slide of four co-founders with no prior companies, a hockey stick y-axis at 80%, a pitch for a Series B round without unit econ, and an ask slide saying \"we're raising some money\". Gates 5b + 6 above exist because `validate` cannot catch any of this.\n\n## Known Issues & Pitfalls\n\n→ Base pitfalls (shell escape, `[last()]` in resident, connector `@name=` rejection C-P-6, picture alt two-step C-P-7, animation remove C-P-4, chart color normalization C-P-7): see pptx v2 §Known Issues & Pitfalls C-P-1..7.\n\nPitch-specific:\n\n- **Stage misidentified.** Series A deck with 6 pages of CAC\u002FLTV math = over-packaged. Series B deck missing unit econ = incomplete. If unsure, re-read §Stage diagnosis before building.\n- **Hockey-stick y-axis.** If the line chart's y-axis doesn't start at 0, VCs read it as a visual lie within 2 seconds. Always `--prop axismin=0` on ARR \u002F revenue \u002F growth charts. Gate 6.6 checks this.\n- **Team slide = portfolio.** Cards showing only {headshot + name + role} fail VC credibility. Every card needs a prior-company or prior-achievement line. Gate 6.5 checks this.\n- **TAM without methodology.** A claimed number with no \"top-down\" or \"bottom-up\" source footnote = fabricated. Pick one methodology per deck; don't mix.\n- **Use-of-Funds as 3-bucket or 5-bucket.** 4-bucket (Eng \u002F GTM \u002F G&A \u002F Reserve) is convention; departing from it reads as sloppy. Gate 6.4 checks presence.\n- **Pitch deck used for a board review \u002F sales deck.** Narrative arc (problem → ask) makes board reviews awkward — route to pptx v2 Recipe (d) 10-slide instead. See §Reverse handoff above.\n- **pptx v2 Recipe (d′) 20-slide is a starting point, not a formula.** It is stage-agnostic SaaS. Adjust for your stage + 赛道 via §Stage diagnosis and §赛道 arc templates — never ship (d′) unchanged for a non-SaaS Series A.\n\n## Help pointer\n\nWhen in doubt: `officecli help pptx`, `officecli help pptx \u003Celement>`, `officecli help pptx \u003Celement> --json`. Help is the authoritative schema; this skill is the decision guide for fundraising deltas on top of pptx v2.\n",{"name":5,"description":7},"main","25382af4fdcb6903796fd330dc07db653b560d3a","skills\u002Fofficecli-pitch-deck",0,"https:\u002F\u002Fgithub.com\u002Fshixianghua\u002FOfficeCLI-Enhanced","https:\u002F\u002Fgithub.com\u002Fshixianghua","2026-07-13 02:22:31",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add shixianghua\u002FOfficeCLI-Enhanced --skill officecli-pitch-deck",{"tool":36,"command":37},"bunx","bunx skills add shixianghua\u002FOfficeCLI-Enhanced --skill officecli-pitch-deck",{"tool":39,"command":40},"pnpm","pnpm dlx skills add shixianghua\u002FOfficeCLI-Enhanced --skill officecli-pitch-deck","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshixianghua\u002FOfficeCLI-Enhanced\u002Fblob\u002Fmain\u002Fskills\u002Fofficecli-pitch-deck\u002FSKILL.md",true,[],[45,51,58,65,72,79],{"skillNo":46,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M78FR19BZGX7ZZBC8G3ZJHG7","officecli","https:\u002F\u002Fgithub.com\u002Fshixianghua\u002FOfficeCLI-Enhanced\u002Fblob\u002Fmain\u002Fskills\u002Fofficecli\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M78FQTRP3J1DPJ6S7M5Y5KEX","officecli-xlsx","Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV\u002FTSV data into Excel format. Trigger whenever the user mentions 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx\u002F.csv filename.","https:\u002F\u002Fgithub.com\u002Fshixianghua\u002FOfficeCLI-Enhanced\u002Fblob\u002Fmain\u002Fskills\u002Fofficecli-xlsx\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M78FQEMC8QMB1XDX9AXSQ3MW","officecli-word-form","Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document', 'onboarding form', 'HR intake', 'survey template', 'contract \u002F SOW template', 'mail-merge template', 'compliance checklist', 'medical intake questionnaire'. Output is a single .docx where specific fields are editable and the rest is locked. This skill is INDEPENDENT, not a scene layer on docx — payload is `\u003Cw:sdt>` + `\u003Cw:ffData>` + `\u003Cw:fldChar>` + `documentProtection`, none of which docx base skill covers. Do NOT trigger for regular reports, letters, memos, academic papers, pitch decks, or any document with no user-fillable fields — route those to officecli-docx or its scene layers.","https:\u002F\u002Fgithub.com\u002Fshixianghua\u002FOfficeCLI-Enhanced\u002Fblob\u002Fmain\u002Fskills\u002Fofficecli-word-form\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M78FQ6NTDMWT2EPM00FPMBMS","officecli-pptx","Use this skill any time a .pptx file is involved -- as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions 'deck', 'slides', 'presentation', 'pitch', or references a .pptx filename.","https:\u002F\u002Fgithub.com\u002Fshixianghua\u002FOfficeCLI-Enhanced\u002Fblob\u002Fmain\u002Fskills\u002Fofficecli-pptx\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M78FPCYEK6A5DFP5BZBVMZPA","officecli-financial-model","Use this skill when the user wants to build a financial model — 3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity \u002F scenario analysis, debt schedule, or fundraising projections — in Excel. Trigger on: 'financial model', '3-statement model', 'P&L + BS + CF', 'DCF', 'WACC', 'NPV', 'terminal value', 'LBO', 'debt schedule', 'cash sweep', 'MOIC', 'IRR \u002F XIRR', 'sensitivity table', 'scenario analysis', 'ARR model', 'unit economics', 'CAC \u002F LTV', 'cap table forecast'. Output is a single formula-driven .xlsx. This skill is a scene layer on top of officecli-xlsx — it inherits every xlsx v2 rule (4-color code, visual floor, number formats, cache-drift, Known Issues, Delivery Gate minimum cycle). DO NOT invoke for a simple budget tracker, CSV dump, or operational KPI sheet — route those to officecli-xlsx base.","https:\u002F\u002Fgithub.com\u002Fshixianghua\u002FOfficeCLI-Enhanced\u002Fblob\u002Fmain\u002Fskills\u002Fofficecli-financial-model\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M78FP50A5PCW0P1YMPW5FTYJ","officecli-docx","Use this skill any time a .docx file is involved -- as input, output, or both. This includes: creating Word documents, reports, letters, memos, or proposals; reading, parsing, or extracting text from any .docx file; editing, modifying, or updating existing documents; working with templates, tracked changes, comments, headers\u002Ffooters, or tables of contents. Trigger whenever the user mentions 'Word doc', 'document', 'report', 'letter', 'memo', or references a .docx filename.","https:\u002F\u002Fgithub.com\u002Fshixianghua\u002FOfficeCLI-Enhanced\u002Fblob\u002Fmain\u002Fskills\u002Fofficecli-docx\u002FSKILL.md",[],[]]