Presentation Design Pack

The Slide Master Trap and the Engineer's Context Switch

You've spent weeks on a project. The architecture is clean, the tests pass, and the metrics prove value. You open PowerPoint, Keynote, or your preferred slide tool, and the real work begins—or so the business assumes. You stare at a blank canvas. You spend forty-five minutes fighting with SmartArt. You align text boxes until your eyes cross. You pick a color palette that looks fine in isolation but clashes with your company's branding guidelines. By the time you're done wrestling with decoration, the narrative is buried, the key insight is lost in the noise, and you're exhausted.

You're not a designer. You're an engineer. Your job is to solve problems, build systems, and ship code. You shouldn't have to be a graphic artist to get your work recognized. Yet every quarter, every promotion cycle, every budget review demands a deck that lands. The friction isn't just about time; it's about cognitive load. Switching from deep engineering work to slide design fractures your focus. We built the Presentation Design Pack so you don't have to make that switch. We engineered a workflow that treats presentation design like code: structured, validated, and reusable. You define the story and the data; the skill handles the structure, the visual grammar, and the export. You get a deck that communicates your value without you touching a single text box alignment.

The Hidden Tax of Unstructured Decks

Every hour you spend aligning shapes is an hour stolen from shipping. But the cost of a bad deck goes far beyond lost time. When stakeholders can't find the answer in thirty seconds, they assume the answer doesn't exist. You lose budget. You lose trust. You get the "send me the deck" email instead of the green light.

We've seen engineers burn ten or more hours on a quarterly review that could have been a twenty-minute conversation because the data visualization was cluttered and the headline didn't drive the point home. That's not just time lost; that's career capital eroding. A misaligned deck creates ambiguity. Ambiguity kills momentum. When your presentation lacks a clear hierarchy, decision-makers fill the gaps with their own assumptions, often the wrong ones.

The research is clear: structure dictates impact. HBR notes that the most effective presenters use the same techniques as great storytellers, reminding people of the status quo and then revealing the path to a better way ^[1]. Without that structure, you're just dumping information. You're creating noise. A deck without a narrative arc forces the audience to do the synthesis work. Most won't. They'll skim. They'll miss the nuance. They'll ask for a follow-up meeting that could have been avoided.

Bad structure also propagates downstream. If your presentation is a mess, your written reports likely are too. Teams that skip presentation discipline often struggle with broader stakeholder alignment. For teams managing stakeholder communication packs, this skill ensures your decks align with your written reports, creating a consistent narrative thread across all channels. When your presentation and your documentation tell the same story, credibility compounds. When they diverge, trust fractures.

A Platform Team's Migration Story That Almost Flopped

Imagine a platform team that just migrated a critical service to a new architecture. Latency dropped 40%. Cost down 25%. They have the metrics. They open their slide tool. They paste a screenshot of the Grafana dashboard. They add a bullet list of the migration steps. They call it "done."

The VP of Engineering looks at it and asks, "So what? Why should I care?"

The team is blindsided. They had the data, but they lacked the narrative architecture. They presented the tool, not the transformation. Duarte's research emphasizes that in the world of presentations, the audience is the hero, and the speaker is the mentor ^[4]. In this scenario, the team forgot the hero. They made the VP watch a technical migration instead of showing how the migration enabled the new feature launch that the VP's team is counting on.

A better approach would have started with the status quo—the pain of the old latency hurting customer retention—and revealed the path to the improved state. Duarte's blog highlights that storytelling is about transformation through a three-act structure ^[2]. The team missed the act. They missed the tension. They missed the resolution. As a result, the VP didn't see the value immediately. The team had to go back, restructure, and re-present. That's the cost of skipping the design workflow.

This isn't just a communication problem; it's a design problem. The team didn't know how to map their data to the right visual encoding. They pasted a raw dashboard instead of a focused chart. They ignored the principles of visual hierarchy. As Alberto Cairo's work on data visualization teaches, effective communication requires stripping away the non-essential and highlighting the signal ^[8]. The team didn't. They dumped the signal and the noise together.

If your team also builds technical presentation packs for architecture reviews, this skill plugs right in. The templates/storyboard.yaml enforces narrative roles for architecture diagrams, ensuring your visual aids sync with your spoken narrative rather than competing with it. You get the structure for technical depth without sacrificing clarity.

From Raw Data to Decision-Ready Storyboards in Minutes

Now you install the Presentation Design Pack. You define your objective. You feed the data. The skill orchestrates the workflow. You get a storyboard that follows the Minto Pyramid Principle. You get chart recommendations based on the Financial Times Visual Vocabulary. You get speaker notes that handle the Q&A. You export to markdown for your AI slide tool. You spend fifteen minutes on structure and data, not decoration. The deck lands. The VP sees the headline: "Latency cut by 40%, enabling the new feature launch." The green light comes. You're back to coding.

The skill enforces constraints that prevent common failures. The scripts/validate-storyboard.sh parser checks your YAML against the schema. It cross-references chart types against the templates/visual-vocabulary.json. It flags missing data sources. It rejects weak headlines. It's like a linter for your narrative. If you try to use a pie chart for a time-series comparison, the validator throws an error. If you forget the visual_constraints field, the build fails. You can't ship a flawed storyboard.

The templates/visual-vocabulary.json maps data types to optimal chart types and defines encoding rules. It flags anti-patterns based on established visual grammar. You don't have to remember which chart works for which data. The skill tells you. This is especially valuable when synthesizing findings from ux research packs. The visual vocabulary maps user journey data to the right charts, ensuring your research insights are presented with maximum clarity.

The references/delivery-techniques.md provides embedded canonical knowledge on pacing, Q&A handling, and rehearsal protocols. Engineers often wing the talk. This skill gives you a protocol. It tells you how to synchronize your visual aids with your speech. It offers frameworks for handling tough questions. It includes cross-cultural communication adjustments for global audiences. You're not just building a deck; you're preparing for the delivery.

For teams managing internal communications packs, this skill standardizes the narrative across your org. The examples/quarterly-review.storyboard.yaml demonstrates a complete executive review deck, showing how to apply storytelling frameworks and data visualization rules within the production template. You can fork the example, swap the data, and ship a professional deck in minutes.

Even in high-stakes scenarios, a structured storyboard adds discipline. If you're managing a crisis communication pack, this skill ensures your messaging remains consistent under pressure. The validation step prevents ad-hoc changes that could dilute your core message. For automated environments, this integrates with tools used in crisis communication simulation packs to stress-test your messaging workflows before they go live.

What's in the Presentation Design Pack

• skill.md — Orchestrator that defines the end-to-end presentation design workflow, references all templates, references, scripts, and examples, and instructs the agent on when to apply storytelling frameworks, data viz rules, and delivery techniques.
• templates/storyboard.yaml — Production-grade slide structure template grounded in McKinsey's pyramid principle and corporate slide automation standards. Enforces narrative roles, data specifications, visual constraints, and speaker notes with strict YAML schema.
• templates/visual-vocabulary.json — Chart selection matrix and visual grammar rules derived from the Financial Times Visual Vocabulary and Alberto Cairo's principles. Maps data types to optimal chart types, defines encoding rules, and flags anti-patterns.
• references/storytelling-frameworks.md — Embedded canonical knowledge on narrative architecture: Minto Pyramid Principle, McKinsey slide structure, problem-solution-benefit arcs, and executive summary drafting. Contains actionable frameworks, not links.
• references/data-viz-principles.md — Embedded canonical knowledge on data visualization: chart selection logic, visual hierarchy, cognitive load management, color/typography constraints, and progressive revelation techniques for stakeholder presentations.
• references/delivery-techniques.md — Embedded canonical knowledge on presentation delivery: pacing strategies, Q&A handling frameworks, rehearsal protocols, visual aid synchronization, and cross-cultural communication adjustments for business audiences.
• scripts/validate-storyboard.sh — Executable validator that parses the storyboard YAML, cross-references chart types against the visual vocabulary JSON, enforces required fields (headline, data_source, visual_constraints), and exits non-zero on structural or semantic failures.
• scripts/render-to-markdown.sh — Executable workflow that converts validated storyboards into structured markdown optimized for AI slide generation tools. Handles narrative flow assembly, data spec extraction, and speaker note formatting.
• examples/quarterly-review.storyboard.yaml — Worked example demonstrating a complete executive quarterly review deck. Shows real-world application of storytelling frameworks, data visualization rules, and delivery notes within the production template.
• tests/integration.test.sh — Test harness that runs the validator against the example and a deliberately flawed storyboard, asserts exit codes, and verifies template schema compliance. Exits non-zero if any validation or schema check fails.

Ship Decks That Move Decisions

Stop wrestling with slide masters. Start shipping decks that move decisions. Upgrade to Pro to install the Presentation Design Pack.