skilldrop-cli 1.1.3 → 1.2.0

package/packs/design/skills/deck-builder/SKILL.md

@@ -1,209 +0,0 @@
----
-name: deck-builder
-description: Generate a real PowerPoint (.pptx) file from content, audience, and either a brand template or a color palette — with charts, tables and images, not only bullets. Slide count, density and layout are tuned to the audience: execs, boards, technical reviewers, sales prospects, investors, internal teams. Use when the user wants an actual editable .pptx rather than an outline, wants their corporate template or brand colours applied, or says "build the deck", "make it a pptx", "use our template".
----
-
-# deck-builder
-
-This skill produces an **actual editable `.pptx` file**, not an outline. It runs `python-pptx`
-to materialise slides — either on a brand template's own masters and layouts, or on the skill's
-built-in design in the user's brand: their colours, logo and fonts.
-
-It pairs with three others:
-- **[`brand-kit`](../brand-kit/SKILL.md)** — captures the brand once as a `brand.json` this skill reads, so nobody answers the brand questions for every deck
-- **[`audience-profile`](../../../stakeholder-comms/skills/audience-profile/SKILL.md)** — decides how dense, how many, which sections
-- **[`slide-outliner`](../slide-outliner/SKILL.md)** — drafts per-slide content before this skill builds it
-
-For a single fast pipeline, run all three in order: profile → outline → build.
-
-## How to respond
-
-**Four rules come before the steps and outrank them:**
-
-- **Answer what was asked, first.** Open with the answer, the decision or the artifact, in plain words. Scores, matrices, frameworks and tags come after it, and anything that doesn't change the answer is cut.
-- **Use only what you were given.** Don't add facts, names, numbers, incidents, history, steps or sections the input doesn't contain. What you need and don't have is left out of the artifact and listed once at the end under "To confirm".
-- **Deliver from what you have.** When the request gives you something to work on, state your assumptions in a line and produce the result. When it gives you nothing to work on, ask for it in one or two plain sentences and say what you will do once you have it.
-- **Write for someone who has never heard of this skill.** No skill names, no paths or scripts from this folder, no internal terms, and nothing about how the run was set up. A next step is one plain sentence at the end that describes the work.
-- **For this skill:** Read "the deck" as an existing file: look for it, and if it isn't there, ask for it along with any content that is missing. Don't announce audience, format or palette choices before there is content to put on slides.
-
-### 1. Run the setup block — once
-
-Ask everything in **one** message, with defaults already chosen, so the user can answer with a
-single line or say "go". Never trickle out four separate questions, and never generate a deck
-with the design silently defaulted.
-
-> Before I build, confirm these — reply "go" to take the defaults:
-> 1. **Audience** — `exec` · `board` · `technical` · `sales` · `internal` · `investor` · `partner` · `customer`
-> 2. **Format** — live presentation / read-ahead / async share, **how many minutes**, and **16:9** (default) or **4:3**
-> 3. **Brand** — the deck should look like it came from your team. Send any of:
->    - a **`brand.json`** from brand-kit, which covers everything below in one file;
->    - a **template**: path to a corporate `.pptx` / `.potx`, and the deck inherits its masters, fonts, colours, logo and slide size;
->    - your **logo** as a PNG (and a white version for dark slides), **brand colours** as hex values for `primary` / `secondary` / `accent` / `background` / `text`, and your **heading and body fonts**;
->    - or, with no brand, a named **palette**: `corporate-blue` (default for B2B) · `monochrome` · `vibrant` · `dark-mode` · `editorial` · `forest` · `sunset`
-> 4. **Anything to embed** — numbers to chart, a table, diagram PNGs
-
-Rules for reading the answers:
-
-- **Content is the one hard input.** If the user supplied only a topic, stop and ask for the
-  material. Inventing the content is the easiest way to produce a bad deck.
-- **A free-form audience maps to the closest archetype** — "VP of Eng and their staff at a
-  partner" → `technical`, stated out loud. Mixed audience → the least technical archetype, with
-  the rest served by appendix slides.
-- **Time sets slide count**, not the other way round: 1.5–2 minutes per slide live. 30 minutes →
-  12–15 slides including cover and close.
-- **A partial brand palette gets completed**, using the rules in
-  [`reference.md`](reference.md#color-palette-principles) — say which roles were filled in.
-- **Template beats palette** for chrome; the palette still colours charts, tables, big numbers
-  and quote bars, so ask for brand hexes even when a template is supplied.
-- **Brand material beats a named palette.** If the user sent a logo or brand colours, never fall
-  back to `corporate-blue`. If they have brand material but no `brand.json`, suggest running
-  `brand-kit` first, so the next deck and any flyer match this one.
-- **Logos must be PNG or JPG.** PowerPoint can't place SVG or EPS: ask for a PNG export, and
-  never build with the logo silently missing.
-
-**Non-interactive runs** (subagent, CI, headless): audience, format, time and palette degrade to
-`[assumption]` lines stated at the top of the response — default `exec`, live, 16:9,
-`corporate-blue`, or the `brand.json` when one is in the input. Never invent a logo or brand colour. Missing *content* does not degrade: emit `BLOCKED: need deck content
-(outline, doc, or point list)` and build nothing.
-
-### 2. Plan the slide list against the audience archetype
-
-| Audience | Slide count | Density | Required sections |
-|---|---|---|---|
-| `exec` | 6–10 | Low — 3 bullets max | Ask • TL;DR • Business impact • Risks • Ask (closing) |
-| `board` | 8–12 | Low — big numbers | Cover • TL;DR • Strategic context • Financials • Risks • Ask |
-| `technical` | 12–20 | High — detail welcome | Context • Goals • Proposal (3–5) • Alternatives • Risks • Rollout |
-| `sales` | 8–12 | Story arc, visual | Hook • Pain • Solution • Proof • Pricing • Close |
-| `internal` | 5–10 | Mixed | Context • Proposal • Discussion topics • Action items |
-| `investor` | 10–15 | Polished, narrative | Problem • Market • Product • Traction • Team • Ask |
-
-Full archetype spec: [`audience-profile`](../../../stakeholder-comms/skills/audience-profile/SKILL.md). Slide-count budgets per
-format and time: [`reference.md`](reference.md#slide-count-budgets).
-
-### 3. Build a deck spec
-
-A JSON document — full schema, with every layout and the template block, in
-[`templates/deck-spec.json`](templates/deck-spec.json):
-
-```json
-{
-  "title": "ProjectX Migration — Board Update",
-  "audience": "board",
-  "aspect": "16:9",
-  "template": "./brand/acme-master.potx",
-  "layout_map": { "title": "Title Slide", "content": "Title and Content" },
-  "palette": { "primary": "#1A2A6C", "accent": "#FDBB2D" },
-  "brand": "./brand/brand.json",
-  "slides": [
-    { "layout": "title", "title": "...", "subtitle": "...", "presenter": "...", "date": "..." },
-    { "layout": "content", "title": "...", "bullets": ["..."], "notes": "..." },
-    { "layout": "chart", "title": "...", "takeaway": "...", "chart": { "type": "column", "categories": ["..."], "series": [{ "name": "...", "values": [1, 2] }] }, "source": "..." },
-    { "layout": "table", "title": "...", "columns": ["..."], "rows": [["..."]] },
-    { "layout": "image", "title": "...", "image": "./diagram.png", "position": "right", "bullets": ["..."] },
-    { "layout": "big_number", "title": "...", "number": "$24M", "caption": "ARR at risk" },
-    { "layout": "closing", "title": "Approval requested", "subtitle": "..." }
-  ]
-}
-```
-
-Ten layouts: `title`, `section`, `content`, `two_column`, `big_number`, `quote`, `image`,
-`table`, `chart`, `closing`. Most slides are `content`; `chart`, `table` and `big_number` carry
-the evidence; `quote` and `image` break the rhythm. Which content shape earns which layout:
-[`reference.md`](reference.md#layout--content-matching).
-
-Every slide gets a `notes` field. Slide numbers appear automatically past 10 slides — override
-with `"slide_numbers": false`.
-
-### 4. Build from the user's template when there is one
-
-A corporate template is the difference between a deck that gets presented and one that gets
-rebuilt by hand. When the user names one:
-
-```bash
-# Claude Code — list the template's layouts first
-python3 "${CLAUDE_SKILL_DIR}/scripts/build_deck.py" --list-layouts ~/brand/acme-master.potx
-
-# Other IDEs (from the skill folder)
-python3 scripts/build_deck.py --list-layouts ~/brand/acme-master.potx
-```
-
-Map each logical layout to one of the printed names in `layout_map`, then build. The template's
-masters, theme fonts, colours, logos and slide size are inherited; any sample slides it ships
-with are dropped. A logical layout left out of the map falls back to the skill's built-in
-design on the template's blank layout — acceptable for `big_number` or `quote`, wrong for
-`title` and `content`, which is where the branding shows.
-
-`.potx` and `.pptx` both work. Templates carry no charts or tables of their own, so those are
-drawn into whatever content region the mapped layout defines.
-
-### 5. Run the build script
-
-```bash
-# Claude Code
-python3 "${CLAUDE_SKILL_DIR}/scripts/build_deck.py" /tmp/deck-spec.json -o ./out/deck.pptx
-
-# Other IDEs (from the skill folder)
-cd path/to/deck-builder && python3 scripts/build_deck.py /tmp/deck-spec.json -o ./out/deck.pptx
-```
-
-Add `--brand ./brand/brand.json` to build in the user's brand (or set `"brand"` in the spec).
-The brand fills whatever the spec leaves out: palette colours, the template, logo files and
-fonts. On the built-in design the logo goes on every slide: large on the cover, small in the
-lower-left corner elsewhere, and the on-dark version on dark section and closing slides. The
-brand's heading and body fonts are applied to titles, text, tables and charts. A template
-already carries its own logo and fonts, so they come from the template instead.
-
-Add `--strict` to fail the build on a missing or unreadable image instead of drawing a
-placeholder box — use it in CI, not in a conversation.
-
-**Read the warnings.** The script degrades rather than crashing: a missing image, a short data
-series, an unresolvable template layout each produce a warning and a visible fallback. Report
-every warning to the user with the file path; never present a deck with an unexplained
-placeholder box in it.
-
-### 6. Recommend the refinement pass
-
-A generated deck is a strong first draft. Always tell the user to:
-
-- Review the speaker notes — the agent wrote them, and they get read aloud
-- Replace any placeholder box with the real diagram
-- Do one audience pass: read every slide title in order, does the *narrative* land for that audience?
-- Run [`doc-critique`](../../../core/skills/doc-critique/SKILL.md) against the deck rubric before it goes out
-
-## Useful references
-
-- [`reference.md`](reference.md) — palette principles, layout-vs-content matching, chart and table rules, density and slide-count budgets
-- [`templates/deck-spec.json`](templates/deck-spec.json) — full JSON schema with every layout and the template block
-- [`templates/palettes.json`](templates/palettes.json) — the seven presets
-- [`examples/exec-board-update.md`](examples/exec-board-update.md) — worked example: brief → spec → deck
-- [`examples/templated-brand-deck.md`](examples/templated-brand-deck.md) — worked example: corporate `.potx` → layout map → deck
-- [`scripts/build_deck.py`](scripts/build_deck.py) — the generator (don't edit unless adding a layout)
-
-## Quality bar
-
-- **Design is chosen by the user, never silently defaulted** — a `brand.json`, a template, brand colours and logo, or a named palette, confirmed in the setup block.
-- **The user's brand shows on every slide** — their logo (PNG) and colours, and their fonts when they gave them. A deck built from brand material that comes out in `corporate-blue` has failed.
-- **A supplied template is actually inherited** — `layout_map` covers `title`, `section`, `content` and `closing` at minimum. A branded deck rendered on the blank layout has thrown away the branding.
-- **Title slide isn't blank** — real title, subtitle, presenter, date.
-- **Numbers are charted, not bulleted** — three or more comparable figures belong in a `chart` or a `table`, not a bullet list.
-- **Every chart and table cites its `source`** and uses only figures from the user's material.
-- **Bullet density matches audience** — `exec`, *3 bullets max*, period. `technical`, up to 6 when the content needs it.
-- **Speaker notes on every slide** — even one sentence.
-- **Section dividers used sparingly** — at most one every 4–5 content slides.
-- **Zero unexplained warnings** — every warning the script emits is fixed or reported to the user.
-- **Colour is consistent** — palette roles only, no stray colours; text-on-background contrast ≥ 4.5:1.
-
-## Anti-patterns to avoid
-
-- ❌ Ignoring a template the user already named, or asking for a palette after they supplied one. The template is the answer to "what should this look like".
-- ❌ Asking for brand colours when a `brand.json` was supplied, or building without the logo because it was an SVG. Ask for a PNG export instead.
-- ❌ Mapping every logical layout onto the template's one title-and-bullets layout. That is a branded deck that still looks generated.
-- ❌ Generating without confirming audience. The same content for execs and engineers is a different deck.
-- ❌ Inventing a statistic to fill a `big_number`, or a series to fill a chart. No source, no chart.
-- ❌ A table with 20 rows. Over ~12 it is an appendix or a spreadsheet, not a slide.
-- ❌ Passing an SVG or EMF diagram to `image` — `python-pptx` reads raster only. Convert to PNG first.
-- ❌ Shipping the deck with a grey placeholder box still in it because the warning went unread.
-- ❌ Defaulting to bullets when a `big_number`, `chart`, `quote` or `two_column` would land harder.
-- ❌ More than ~20 slides for any audience. If the point needs 21, the deck is the wrong format.
-- ❌ **Showing the machinery.** The reply and the artifact are for the person who asked. Don't mention this skill, its files, templates, caps or internal terms, or that the run is non-interactive. Name another skill once, at the end, as a suggested next step, never inside the artifact.
-- ❌ **A bare `BLOCKED` line.** Keep the `BLOCKED: need <X>` line, then write for a person: what is missing in plain words, what you will produce once you have it, and anything the request already lets you say.

package/packs/design/skills/deck-builder/evals/eval_queries.json

@@ -1,14 +0,0 @@
-[
-  { "query": "Build me a PowerPoint from this content", "should_trigger": true },
-  { "query": "Generate a .pptx deck for this exec presentation", "should_trigger": true },
-  { "query": "Turn this into actual slides I can present, with our brand colors", "should_trigger": true },
-  { "query": "I need a real deck file, not an outline", "should_trigger": true },
-  { "query": "Build the deck on our corporate template — marketing rejects anything else", "should_trigger": true },
-  { "query": "Use our .potx master for this QBR deck", "should_trigger": true },
-  { "query": "Put these quarterly numbers on a slide as a chart", "should_trigger": true },
-  { "query": "Just outline the slides — I'll build the deck myself", "should_trigger": false },
-  { "query": "Write a one-page summary for executives", "should_trigger": false },
-  { "query": "Which audience archetype should I target and what are its rules?", "should_trigger": false },
-  { "query": "Critique the deck I already made", "should_trigger": false },
-  { "query": "Extract the text out of this existing .pptx so I can email it", "should_trigger": false }
-]

package/packs/design/skills/deck-builder/evals/evals.json

@@ -1,67 +0,0 @@
-{
-  "skill_name": "deck-builder",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "Build a .pptx from this content for an exec audience, using our brand palette (navy/white).",
-      "assertions": [
-        "A real .pptx file is produced, not an outline",
-        "Audience, format and design are confirmed in a single setup block rather than as a trickle of separate questions",
-        "The title slide carries a real title, subtitle, presenter, and date — never left blank",
-        "Section dividers appear sparingly, at most one every 4-5 content slides",
-        "Big-number layouts use only numbers the user supplied; no statistic is invented for emphasis",
-        "Bullet density matches the stated audience rather than a fixed default",
-        "The requested palette is applied rather than the default theme"
-      ]
-    },
-    {
-      "id": 2,
-      "prompt": "Build the Q3 QBR deck on our corporate template at ~/brand/acme-master.potx — 25 minutes, live, partner audience.",
-      "assertions": [
-        "The template's layouts are listed with --list-layouts before the spec is written, rather than layout names being guessed",
-        "The spec sets `template` and a `layout_map` covering at least title, section, content and closing",
-        "A palette is still collected, because the template does not colour charts, tables or big numbers",
-        "`aspect` is not fought with — the template's own slide size is accepted and stated",
-        "Slide count is derived from the 25-minute budget at roughly 2 minutes per slide"
-      ]
-    },
-    {
-      "id": 3,
-      "prompt": "Here are our renewal rates for the last three quarters (88%, 91%, 94%) and the SLA table from the contract. Put them in the deck.",
-      "assertions": [
-        "The three comparable figures become a `chart` slide, not a bullet list",
-        "The chart carries a `takeaway` sentence and a `source`",
-        "The SLA data becomes a `table` slide rather than aligned bullets",
-        "No figure appears that the user did not supply",
-        "Any build warning (missing image, short series) is reported to the user with its path rather than left in the file"
-      ]
-    },
-    {
-      "id": 4,
-      "held_out": "2026-10-18",
-      "prompt": "Build the November board deck from ashby-vale-board-notes.md as a PowerPoint and save it as ashby-vale-board-nov.pptx. Everything you need should be in the notes.",
-      "assertions": [
-        "Writes ashby-vale-board-nov.pptx, a valid PowerPoint file with no more than 6 slides",
-        "It states the decision the board is asked to make (approve drawing £250,000 from the loan facility to start Tanner's Yard in January 2027) clearly, not buried in a later bullet",
-        "It notices the notes disagree on how many Furlong Close homes are let (14 versus 12 of 14) and does not put either figure on a slide as settled without flagging it",
-        "It notices the net surplus (£89,650) does not match the lines above it (£85,650) and does not present the stated total as checked fact without flagging it",
-        "It does not make up five years of arrears data: it shows only 2024 to 2026 and tells the user the five-year trend the treasurer asked for cannot be drawn from the notes",
-        "At least some of the figures (finance or arrears) appear as a chart or table in the deck, as the notes ask, rather than only as bullet text",
-        "It does not invent figures, names, dates or achievements that are not in the notes"
-      ]
-    },
-    {
-      "id": 5,
-      "held_out": "2026-10-18",
-      "prompt": "need a powerpoint for the PTA meeting on thursday about the playground fundraiser. 3 slides max. we've raised £2,340 so far out of the £5,000 target, the bake sale did best, and we still want to do a sponsored walk in spring but haven't picked a date. can you do it?",
-      "assertions": [
-        "Writes a .pptx file with no more than 3 slides",
-        "The figures are right: £2,340 raised of a £5,000 target, and any figure it works out is correct (£2,660 still to raise, about 47%)",
-        "It says the bake sale did best without making up how much it raised or what other events raised",
-        "The sponsored walk is shown as planned for spring with the date still to be decided; no date is invented",
-        "It does not invent other facts such as the school's name, people's names, numbers of families or deadlines",
-        "It delivers the file without asking questions first, and the reply is short and in plain words"
-      ]
-    }
-  ]
-}

package/packs/design/skills/deck-builder/evals/files/4/ashby-vale-board-notes.md

@@ -1,36 +0,0 @@
-# Ashby Vale Community Land Trust: notes for the November board
-
-Board meets Thursday 26 November 2026. **6 slides maximum**, the chair is strict about this.
-The board likes to see numbers as charts or tables, not paragraphs.
-Use our colours: deep green #24553A, stone #E8E1D3, terracotta #B5562F.
-
-## Homes
-- Phase 1 at Furlong Close: 14 homes completed and let (as of 31 October).
-- Phase 2 at Tanner's Yard (9 homes): planning approved in September, build not started.
-
-## Lettings officer update
-12 of the 14 Furlong Close homes are let. Two are awaiting tenants after the first nominees withdrew.
-
-## Finance (year to 31 October)
-
-| Line | £ |
-|---|---:|
-| Rent income | 96,400 |
-| Grant (Vale Housing Fund) | 40,000 |
-| Maintenance | -18,250 |
-| Loan interest | -22,700 |
-| Admin and insurance | -9,800 |
-| **Net surplus** | **89,650** |
-
-## Rent arrears (% of rent due, at 31 October)
-
-| Year | Arrears |
-|---|---:|
-| 2024 | 2.1% |
-| 2025 | 3.4% |
-| 2026 | 4.8% |
-
-The treasurer has asked for a five-year arrears trend chart.
-
-## Decision needed
-Board to approve drawing £250,000 from the Vale Housing Fund loan facility so the Tanner's Yard build can start in January 2027.

package/packs/design/skills/deck-builder/examples/exec-board-update.md

@@ -1,108 +0,0 @@
-# Example: Quarterly board update for a migration project
-
-**Prompt the user gave:** *"Build me a board update deck for our migration project. We're 60% through, on track for Q1 close, $2.4M annualised infra savings so far, but we discovered two services need a schema rewrite and we now have a multi-region regulatory requirement. We're asking for a $620k budget overrun. Use corporate-blue palette."*
-
-## Step 1 — Audience archetype lookup
-
-Board update → use `audience-profile.board` archetype:
-
-- **Slide count target:** 8–12
-- **Bullet density:** ≤ 3 bullets/slide, ≤ 6 words/bullet
-- **Required sections:** Cover, TL;DR, Strategic context, Financials, Risks, Ask
-- **Tone:** Outcomes-led, business-first, big numbers welcome
-- **Layouts to favour:** `big_number` (for the $2.4M and the $620k), `quote` (for credibility), `two_column` (for scope changes)
-
-## Step 2 — Build the deck spec
-
-```json
-{
-  "title": "ProjectX Migration — Board Update",
-  "audience": "board",
-  "palette": "corporate-blue",
-
-  "slides": [
-    {
-      "layout": "title",
-      "title": "ProjectX Migration",
-      "subtitle": "Board update — Q3 FY26",
-      "presenter": "John Doe",
-      "date": "2026-09-15",
-      "notes": "Open with: 'We're 60% through, on track, and asking for an overrun. Here's why it's still a good deal.'"
-    },
-    {
-      "layout": "content",
-      "title": "60% complete, zero customer incidents, on track for Q1 close",
-      "bullets": [
-        "8 of 14 services cut over",
-        "p99 latency down 22% on migrated services",
-        "Two services moved to phase 3 — schema rewrite"
-      ],
-      "notes": "Lead with zero incidents. Boards remember that more than any other number on this slide."
-    },
-    {
-      "layout": "big_number",
-      "title": "Annualised infra savings already realised",
-      "number": "$2.4M",
-      "caption": "From the 8 migrated services. Projected $5.8M at completion.",
-      "notes": "Pause. Let the number land. Don't rush to the next slide."
-    },
-    {
-      "layout": "two_column",
-      "title": "What changed since the original plan",
-      "left": {
-        "title": "Original scope",
-        "bullets": ["14 services migrated", "Single-region active", "Legacy DB decommissioned"]
-      },
-      "right": {
-        "title": "Discovered in flight",
-        "bullets": ["Schema rewrite for 2 services", "Multi-region (EU regulator)", "Auth refactor coupling"]
-      },
-      "notes": "Multi-region is a regulator change, not a planning miss. Say so explicitly."
-    },
-    {
-      "layout": "quote",
-      "quote": "The migration went smoother than any I've seen in 20 years.",
-      "attribution": "VP Engineering, post phase-2 cut-over",
-      "notes": "Optional, but de-risks the perception that we're behind."
-    },
-    {
-      "layout": "content",
-      "title": "Top 3 risks for the remaining 40%",
-      "bullets": [
-        "Schema rewrite: 6 weeks, dry-runs underway",
-        "Auth refactor coupling: increases coordination overhead",
-        "Holiday freeze: -4 calendar weeks"
-      ],
-      "notes": "Don't soften the risks. Boards trust presenters who name them."
-    },
-    {
-      "layout": "big_number",
-      "title": "Budget overrun we're requesting",
-      "number": "$620k",
-      "caption": "Covers schema rewrite + multi-region buildout. Payback: < 8 months.",
-      "notes": "Position the overrun against the $5.8M projected savings — net positive within the same fiscal year."
-    },
-    {
-      "layout": "closing",
-      "title": "Approval requested: $620k FY26 budget overrun",
-      "subtitle": "Decision needed by 2026-10-01 to keep Q1 close",
-      "notes": "Land here. Take questions. Don't add a thank-you slide."
-    }
-  ]
-}
-```
-
-## Step 3 — Generate
-
-```bash
-python3 scripts/build_deck.py /tmp/board-update.json -o ./out/board-update.pptx
-```
-
-## Step 4 — Hand-off to the user
-
-> Generated `out/board-update.pptx` — 8 slides, corporate-blue palette. Two notes before you present:
->
-> 1. **Verify the speaker notes** — I wrote them based on the content you gave me. Read through and adjust your phrasing.
-> 2. **Replace the slide 5 quote** — I used a placeholder attribution. If you have the actual quote (and clearance to use it), paste it in slide 5.
->
-> Want me to also produce an exec-summary one-pager from the same content?

package/packs/design/skills/deck-builder/examples/templated-brand-deck.md

@@ -1,148 +0,0 @@
-# Example: Q3 partner QBR on the company's own PowerPoint template
-
-**Prompt the user gave:** *"Make the Q3 QBR deck for Northwind. Use our corporate template at
-`~/brand/acme-master.potx` — it's mandatory, marketing rejects anything else. 25 minutes, live,
-with the partner's CTO and two of their architects in the room. Renewal rate went 88 → 91 → 94%
-over the last three quarters, ticket volume is down 31%, and we want to land the co-sell
-expansion ask. Brand colours are #0B3D6B and #E8A33D."*
-
-## Step 1 — Setup block, answered in one pass
-
-| Input | Value | How it was resolved |
-|---|---|---|
-| Content | Renewal trend, ticket volume, expansion ask | Supplied |
-| Audience | `partner` | Stated ("partner's CTO and architects") |
-| Format | Live, 25 min → 12–14 slides | Stated; slide count derived at ~2 min/slide |
-| Aspect | From the template | `aspect` ignored — the `.potx` is 16:9 |
-| Design | `~/brand/acme-master.potx` + brand hexes | Template for chrome, palette for charts |
-| Embeds | Renewal trend (chart), SLA table | Three comparable figures ⇒ chart, not bullets |
-
-The palette is still collected: the template does not colour charts, tables or big numbers.
-`primary: #0B3D6B`, `accent: #E8A33D`; `secondary`, `background` and `text` derived per
-[`reference.md`](../reference.md#color-palette-principles) and called out to the user.
-
-## Step 2 — Read the template's layouts before writing the spec
-
-```bash
-python3 "${CLAUDE_SKILL_DIR}/scripts/build_deck.py" --list-layouts ~/brand/acme-master.potx
-```
-
-```
-acme-master.potx — slide size 13.33in x 7.50in
-  [0] Acme Cover
-  [1] Acme Section Break
-  [2] Acme Title and Body
-  [3] Acme Two Column
-  [4] Acme Statement
-  [5] Acme Full Bleed Image
-  [6] Blank
-```
-
-The names are the template's, not PowerPoint's defaults — which is exactly why the map is read
-from the file rather than guessed.
-
-## Step 3 — The deck spec
-
-```json
-{
-  "title": "Northwind QBR — Q3 FY26",
-  "audience": "partner",
-  "template": "~/brand/acme-master.potx",
-  "layout_map": {
-    "title": "Acme Cover",
-    "section": "Acme Section Break",
-    "content": "Acme Title and Body",
-    "two_column": "Acme Two Column",
-    "big_number": "Acme Statement",
-    "quote": "Acme Statement",
-    "chart": "Acme Statement",
-    "table": "Acme Statement",
-    "image": "Acme Full Bleed Image",
-    "closing": "Acme Statement"
-  },
-  "palette": {
-    "primary": "#0B3D6B",
-    "secondary": "#4A6E94",
-    "accent": "#E8A33D",
-    "background": "#FFFFFF",
-    "text": "#222222"
-  },
-  "slides": [
-    {
-      "layout": "title",
-      "title": "Northwind × Acme — Q3 business review",
-      "subtitle": "Renewals, service quality, and the FY27 co-sell ask",
-      "presenter": "Jane Roe, Partner Director",
-      "date": "2026-09-30",
-      "notes": "Thank them for the quarter before the first slide. Name the ask now so it isn't a surprise at slide 12."
-    },
-    {
-      "layout": "chart",
-      "title": "Renewal rate has climbed every quarter this year",
-      "takeaway": "Three consecutive quarters of improvement — the joint success plan is what changed.",
-      "chart": {
-        "type": "line",
-        "categories": ["Q1 FY26", "Q2 FY26", "Q3 FY26"],
-        "series": [{ "name": "Renewal rate (%)", "values": [88, 91, 94] }],
-        "number_format": "0\"%\""
-      },
-      "source": "Northwind CS dashboard, 30 Sep 2026",
-      "notes": "Let them claim the win — ask their CTO what drove Q2. The answer is usually the thing to double down on in FY27."
-    },
-    {
-      "layout": "big_number",
-      "title": "Support load is down as adoption is up",
-      "number": "-31%",
-      "caption": "Ticket volume vs. Q3 FY25, on 2.4× the seat count",
-      "notes": "The pairing is the point: more users, fewer tickets. Pause after saying it."
-    },
-    {
-      "layout": "table",
-      "title": "SLA performance against contract",
-      "columns": ["Metric", "Contracted", "Q3 actual", "Status"],
-      "rows": [
-        ["Availability", "99.9%", "99.97%", "Met"],
-        ["P1 response", "15 min", "9 min", "Met"],
-        ["P1 resolution", "4 hrs", "3h 10m", "Met"],
-        ["Change failure", "< 5%", "6.2%", "Missed"]
-      ],
-      "caption": "Change-failure remediation plan on the next slide.",
-      "notes": "Do not skip the missed row. Naming it before they do is what makes the other three credible."
-    },
-    {
-      "layout": "closing",
-      "title": "Ask: co-sell motion for FY27, two named accounts each",
-      "subtitle": "Kick-off 15 Oct, joint pipeline review monthly",
-      "notes": "Land on the ask. Get the kick-off date agreed in the room, not in follow-up email."
-    }
-  ]
-}
-```
-
-*(Abridged — the full deck is 13 slides; the four above are the ones that show the new layouts.)*
-
-## Step 4 — Build
-
-```bash
-python3 "${CLAUDE_SKILL_DIR}/scripts/build_deck.py" /tmp/northwind-qbr.json -o ./out/northwind-qbr.pptx
-```
-
-```
-template: dropped 2 sample slide(s), kept masters and layouts
-wrote ./out/northwind-qbr.pptx (13 slides, template)
-```
-
-No warnings, so nothing to report. Had the SLA table's diagram been an `.svg`, the build would
-have drawn a placeholder box and warned — which gets reported to the user with the path, not
-quietly shipped.
-
-## What the template bought
-
-| Without the template | With it |
-|---|---|
-| Calibri, generated-looking cover | Acme's typeface, cover, and logo on every slide |
-| Palette-coloured title bars | The master's own chrome |
-| Marketing sends it back | Passes brand review unchanged |
-
-The palette still did real work: the line chart, the `-31%`, and the table header are brand
-colours because `palette` was collected *alongside* the template, not instead of it.

package/packs/design/skills/deck-builder/manifest.json

@@ -1,18 +0,0 @@
-{
-  "name": "deck-builder",
-  "version": "0.3.4",
-  "description": "Generate a real PowerPoint (.pptx) file from content, audience, and either a brand template or a color palette — with charts, tables and images, not only bullets. Slide count, density and layout are tuned to the audience: execs, boards, technical reviewers, sales prospects, investors, internal teams. Use when the user wants an actual editable .pptx rather than an outline, wants their corporate template or brand colours applied, or says \"build the deck\", \"make it a pptx\", \"use our template\".",
-  "entrypoint": "SKILL.md",
-  "deps": {
-    "npm": [],
-    "pip": ["python-pptx==1.0.2"]
-  },
-  "env": { "required": [], "optional": [] },
-  "related": ["brand-kit", "audience-profile", "slide-outliner", "doc-critique"],
-  "install": {
-    "pip": "python3 -m pip install -r requirements.txt"
-  },
-  "tags": ["powerpoint", "pptx", "deck", "presentation", "template", "charts", "stakeholder-communication"],
-  "permissions": {"network": [], "commands": [], "files": "named-paths", "notes": "Needs the python-pptx package (declared in deps)."},
-  "model": { "tier": "standard", "rationale": "Shapes content, maps a brand template's layouts, and runs a script. Judgment, not hard reasoning." }
-}