compono

Agent-oriented, code-based PPTX generation. Describe a deck as typed primitives — an LLM agent never writes raw coordinates or touches OOXML.

compono lets an LLM agent (or a human) describe a slide deck as data — headers, bullet text, stats, tables, charts, images, process sequences, shapes — and get back a real, editable .pptx file. The agent never writes raw x/y/w/h coordinates: a constraint-based layout resolver computes every position from a small set of typed primitives.

Every rendered element is a genuine, editable native shape (p:sp, p:pic, p:graphicFrame) — never a flattened image or embedded video. Open the result in PowerPoint and drag a box around; it's a real object, not a picture of one.

This file is both the human-facing README and the in-context reference an agent uses to call compono correctly — see skills/compono/SKILL.md for the packaged version of the same content.

See it in action

compono isn't scoped to one deck genre — the same primitives compose into client proposals, conference talks, research talks, college presentations, or a lighter explainer. Every image below is rendered directly from the matching examples/*.json spec (.pptx → PNG via LibreOffice, see scripts/render_example_screenshots.py) — nothing here is a mockup:

Client proposal	Conference talk

Research talk	Fun explainer

shape + connector compose into real diagrams, not just colored boxes — a layered system architecture, built entirely from examples/architecture_diagram.json:

See examples/ for the full specs (client_proposal.json, conference_talk.json, research_talk.json, college_presentation.json, fun_explainer.json, architecture_diagram.json, and full_catalog.json).

Install

pip install compono
# or
uv add compono

For local development, see CONTRIBUTING.md.

Quickstart

from compono import render_deck

spec = {
    "slides": [
        {
            "header": {"title": "Q3 Results", "subtitle": "Engineering team"},
            "body": [
                {
                    "primitive": "text",
                    "mode": "bullets",
                    "content": [
                        "Shipped the new layout resolver",
                        "Cut render time by 40%",
                        "Zero overflow bugs in production",
                    ],
                    "emphasis_indices": [1],
                }
            ],
        }
    ]
}

report = render_deck(spec, "deck.pptx")
print(report.pptx_path, report.warnings)

Or from the command line:

compono validate spec.json
compono render spec.json -o deck.pptx

Core concepts

• One entry point, two verbs. render_deck(spec, output_path) and validate(spec) are the only two functions you need. validate is cheap — no pptx write, millisecond-scale — so an agent can iterate on a spec before paying render cost.
• A spec is plain data. Either a raw dict/JSON (what an agent's tool-calling naturally produces) or the typed builder classes (Deck, Header, Text, ...) — both serialize to the identical shape. There's no divergence between the two paths.
• You never write coordinates. Every primitive claims space in a slide; the resolver (a CSS-flexbox-style directional box model) computes real EMU positions. grid is the one primitive that does true 2D row/column math.
• Errors are fixes, not diagnoses. Every validation/render failure is {slide, primitive, field, error, detail, fix} — see Error shape below.
• render_deck returns a report, not just a file — {pptx_path, manifest, warnings, actual_layout} — so an agent can reason about what happened without reopening the file.

API reference

from compono import (
    render_deck, validate,
    Deck, Slide, Header, Text, Image, Stat, Grid, Table, Sequence, Chart, Shape,
    DeckValidationError,
)

A Deck is {template?: str, slides: [Slide, ...]}. A Slide is {header?: Header, body: [primitive, ...], notes?: str}. body (and grid.items) accept any primitive, keyed by its "primitive" field.

Error shape

{
  "slide": 3,
  "primitive": "grid.items[1]",
  "field": "content",
  "error": "overflow",
  "detail": "Text is ~14pt too tall for the box at font size 18pt (6 lines).",
  "fix": "Shorten the text, reduce bullet/line count, or split into two slides."
}

The feedback loop in practice

This is the actual point of validate() being cheap and separate from render_deck() — an agent runs it first, gets back something it can act on, and only pays render cost once the spec is clean. No new API for this, just the two verbs above used the way they're meant to be:

1st pass — a real spec, sharing a slide with two stats, packs in three long bullets:

spec = {
    "slides": [{
        "header": {"title": "Q3 Roadmap"},
        "body": [
            {"primitive": "text", "mode": "bullets", "content": [
                "Ship onboarding redesign across web, iOS, and Android, "
                "with full localization support for every launch market",
                "Migrate billing to the new usage-based pricing engine, "
                "including proration, credits, and dunning retries",
                "Roll out SSO and SCIM provisioning for enterprise "
                "customers across every supported identity provider",
            ]},
            {"primitive": "stat", "value": "42%", "label": "YoY revenue growth"},
            {"primitive": "stat", "value": "99.97%", "label": "platform uptime"},
        ],
    }]
}
validate(spec).errors

[{
  "slide": 0, "primitive": "body[0]", "field": "content", "error": "overflow",
  "detail": "Text is ~22pt too tall for the box at font size 18pt (6 lines).",
  "fix": "Shorten the text, reduce bullet/line count, or split into two slides."
}]

2nd pass — the agent applies the fix verbatim (shortens the bullets), nothing else about the spec changes:

spec["slides"][0]["body"][0]["content"] = [
    "Ship onboarding redesign across web, iOS, and Android",
    "Migrate billing to usage-based pricing",
    "Roll out SSO and SCIM for enterprise customers",
]
validate(spec).valid  # True
render_deck(spec, "q3-roadmap.pptx")  # now succeeds

render_deck would have raised DeckValidationError on the 1st-pass spec instead of writing a broken file — the loop above is what an agent actually runs, not a hypothetical.

Primitive catalog

Every primitive accepts an optional id (needed if another primitive references it, e.g. a connector) and an optional notes (speaker notes).

Every schema field's description is written as an instruction (e.g. "Keep under ~60 characters — longer titles will be shrunk by the resolver"), not a bare type label — call Header.model_json_schema() (or any primitive class) to get the full JSON Schema with these descriptions inline.

Image placeholders

Set "placeholder": true (with an optional caption) instead of src when you don't have a real image yet. It renders as an intentional design element — dashed border, centered caption — and render_deck's RenderReport.manifest gets one entry per placeholder: {slide, primitive, rect: {x, y, w, h}, caption}. A later pass (image search/generation/human upload) can fill each reserved rect directly from the manifest EMU rect — no re-layout needed, and the deck-building agent itself never needs image-generation capability.

Worked examples

1. Title slide

{
  "slides": [
    { "header": { "title": "2026 Roadmap", "subtitle": "Platform team", "eyebrow": "Q1 Kickoff" } }
  ]
}

2. Two-column comparison with a connector

{
  "slides": [{
    "header": { "title": "Before vs. After" },
    "body": [
      {
        "primitive": "grid",
        "columns": 2,
        "items": [
          { "id": "before", "primitive": "shape", "kind": "rounded_rect", "fill": "#EF4444",
            "text": { "content": "Manual layout" } },
          { "id": "after", "primitive": "shape", "kind": "rounded_rect", "fill": "#10B981",
            "text": { "content": "Resolver-computed layout" } }
        ]
      },
      { "primitive": "shape", "kind": "connector", "connects": { "from_id": "before", "to_id": "after" } }
    ]
  }]
}

3. Stat + table + chart dashboard

{
  "slides": [{
    "header": { "title": "Q3 Metrics" },
    "body": [
      { "primitive": "stat", "value": "42%", "label": "YoY growth", "trend": "+12% vs Q2" },
      { "primitive": "table", "headers": ["Quarter", "Revenue"], "rows": [["Q1", "10"], ["Q2", "14"]] },
      { "primitive": "chart", "chart_type": "bar", "categories": ["Q1", "Q2"],
        "series": [{ "name": "Revenue", "values": [10, 14] }] }
    ]
  }]
}

4. Process sequence

{
  "slides": [{
    "header": { "title": "Our Process" },
    "body": [{
      "primitive": "sequence",
      "orientation": "horizontal",
      "steps": [
        { "label": "Discover", "description": "Understand the problem" },
        { "label": "Design", "description": "Sketch options" },
        { "label": "Ship", "description": "Release to users" }
      ]
    }]
  }]
}

See examples/full_catalog.json for a complete, runnable spec (also used as a test fixture).

Fonts and templates

A deck's typeface comes from its template, not a per-primitive field — Deck.template (default "default") names a config file under src/compono/templates/. Two ship today:

{ "template": "modern", "slides": [ ... ] }

or via the CLI: compono render spec.json --template modern -o deck.pptx (a CLI/kwarg template always overrides the spec's own template field). An unknown name is a structured unknown_template error (validate/render alike), not a crash — the fix lists what's available.

If a user asks the agent for a font that isn't default or modern: there is no schema field to smuggle an arbitrary typeface through a single render call — that's deliberate (see Core concepts); fonts live in a reviewed template file, not agent-request data. So:

• A coding agent with write access to this repo (e.g. Claude Code working on compono itself) can add a new src/compono/templates/<name>.yaml — copy default.yaml's page/margin values, set the requested font_family — then use {"template": "<name>"} going forward. This is a one-time, reviewed, host-side change, the same as adding modern.yaml was.
• An agent that only has render_deck/validate as tools (e.g. over MCP, no filesystem access to compono's own package) cannot invent a template on the fly. It should tell the user the requested font isn't available, list the templates that are, and either fall back to one of them or ask a human to add the template file.

Overflow checking (validate's layout errors, and the "shrink text on overflow" behavior it protects against) reads real glyph advance widths via fonttools — no rendering required. As of this release, no font is bundled into the package yet (src/compono/fonts/ is a placeholder); validation falls back to a system font if one is found (e.g. arial.ttf on Windows), and is skipped — not faked — with a warning if none is available. This is independent of font_family above — overflow metrics don't yet reflect the template's chosen typeface (known limitation, see CHANGELOG). A bundled, OFL-licensed safe-font list is planned before the first tagged release; this section will list it once shipped.

CLI

compono validate spec.json
compono render spec.json --template modern -o deck.pptx

Mirrors validate/render_deck exactly — useful for agent frameworks that can only shell out rather than import Python.

MCP server

compono-mcp exposes validate/render_deck as MCP tools, for any MCP-compatible client — not just Claude Code.

pip install compono-mcp
# or
uv add compono-mcp

Add to your MCP client config (Claude Desktop / Claude Code style):

{ "mcpServers": { "compono": { "command": "compono-mcp" } } }

Exposes validate_deck/render_deck_tool tools (identical spec shape to the Python API) and a compono://reference resource carrying the full agent-facing reference doc, for clients without Claude Code's skill system.

Claude Code plugin

This repo is also a Claude Code plugin marketplace, bundling the skills/compono/SKILL.md reference doc as an installable skill:

/plugin marketplace add Shaik-Hamzah123/compono
/plugin install compono

Contributing

See CONTRIBUTING.md for dev setup, branching, and code style. If you're using Claude Code, .claude/README.md describes the build-workflow skill, review subagent, and commit/format hooks set up for this repo.