Skip to content
Portfolio/Capabilities

CAPABILITY 04 / 30

Decks that come out on brand

Thirty layouts, light and dark, native charts, and a render check that looks at every slide.

IN PRODUCTION

This runs in client systems today. The sample below was regenerated for a fictional company.

A deck generator is easy to write and easy to trust too much. This one builds real PowerPoint files from content, in thirty approved layouts with editable charts, then renders every slide and checks it for overflow and overlap before anyone sees it. The same content also re-flows under a style overlay for the person presenting it.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

The mechanism is the production one. The company, the catalogue, and every figure are fictional.

Loading the slide browser.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

House build, every layout
House build, every layoutPowerPoint · 33 pages · 33 slides, 11 of them dark, all 30 layouts, 3 native charts. The reference build.Download the deck ↗PDF
Analyst overlay
Analyst overlayPowerPoint · 32 pages · 32 slides. Type scale 0.84, dense, numbers pulled behind the agenda, breather slides dropped, KPI row and before and after rendered as tables, two analyst only slides added.Download the deck ↗PDF
Narrative overlay
Narrative overlayPowerPoint · 30 pages · 30 slides. Type scale 1.18, airy, detail and table slides dropped except the price sheet, the three column slide split into one statement per idea, a statement slide opening each section.Download the deck ↗PDF
Board overlay
Board overlayPowerPoint · 34 pages · 34 slides. Type scale 1.06, high contrast, a summary slide behind the agenda, nothing dropped but detail and table slides moved behind the appendix divider.Download the deck ↗PDF
JSON
Render QA output, verbatimData · Written by render-qa.py. Carries the conversion path, the thresholds, the check definitions, per build and per slide results, the rendered image index, and the log of what earlier runs found and what changed in the generator.Open the file ↗
JSON
Deck content, the single source of factsData · Every number, name, price and date in all four builds. The overlays never touch it.Open the file ↗
JSON
The three executive overlaysData · Type scale, leading, density, drop and defer tags, and the ordering rules for analyst, narrative and board.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is
  1. 01Write the content

    Slides are data. Nobody types into a text box.

  2. 02Pick the layout

    Each entry names an approved layout, and the generator refuses an unknown one.

  3. 03Build

    A real .pptx comes out, with native charts that stay editable.

  4. 04Overlay

    The same content re-flows for the analyst, the narrative, or the board style.

  5. 05Render and check

    Every slide is rendered and inspected for overflow, overlap, and contrast before release.

WHAT IT READS

  • The deck content as data, one entry per slide
  • The approved layout set, light and dark
  • A style overlay per presenter
  • The brand token set

WHAT IT CHECKS BEFORE IT SHIPS

  • No text overflows its placeholder on any slide
  • Charts are native objects, not images
  • Dark slides meet a contrast floor
  • An unknown layout name stops the build
In production: 30 layouts in light and dark against a 60-slide master, with 12 decks approved in one company system.

The mechanism runs inside client systems. Everything on this page was regenerated for Apex Instruments, a company that does not exist. Client names, source files, and internal wording stay private.

What it producesWhat is being built next