Slide Components

Path convention: All commands run from the session workspace. Prefix skill scripts with .opencode/skills/pptx/. Generated files go in outputs/.

Components are the DEFAULT way to build a deck from scratch. Each component is a tested layout function: fixed 0.5" margins, the SKILL.md typography scale, contrast-safe color picking, and shrink/truncate guards so long content cannot overflow. Assembling slides from components is much faster than hand-placing shapes and produces decks that pass lint.py on the first try. Drop to raw pptxgenjs (pptxgenjs.md) only for a layout no component covers — and even then, keep the rest of the deck on components.

Components are for the from-scratch path only. When editing a chosen template, follow editing.md instead.

Design language: engineered monochrome

The default visual system is engineered monochrome: a white field with near-black ink, hierarchy carried by weight and size (not color). It is intentionally restrained — the design reads as precise and technical rather than decorated.

• White field, ink text. Content slides are white; text is near-black (not pure black), with a gray reserved for genuinely secondary lines. Body copy stays dark for comfortable contrast.
• Rules, not cards. Panels and columns are separated by thin hairline rules and whitespace — never tinted card fills.
• Hairline grid. Title, section, and closing slides carry a faint architectural grid in the empty region (kept clear of text).
• The notched plate. The one accent shape is a cut-corner rectangle (snip1Rect) filled in the primary ink with reversed text — used as the single dominant emphasis element on a slide (the title meta chip, one hero stat, the closing CTA). Never more than one per slide.
• Rectilinear. No circles. Timeline markers are small filled ink squares; icons sit bare (no colored backers).
• Type. Inter carries display and body; a monospace (Fira Code) is the "technical voice" for labels, section markers, step numbers, and attributions. Display headlines read best in sentence case ending with a period ("Give your team superpowers.").

Themeability is preserved. Every motif derives from the theme object — the hairline is a low blend of background toward text, the grid likewise per light/dark field, the plate is theme.primary with theme.onPrimary text, and dark slides use a theme-derived dark field. Passing a custom palette to makeTheme renders the same architecture in those colors, with no brand-specific values leaking in.

Setup

Use the default monochrome palette (defaultTheme()) unless the user wants a specific palette:

const C = require(".opencode/skills/pptx/scripts/components.js");

const theme = C.defaultTheme(); // engineered monochrome — colors + fonts, no branding
const pres = C.createPresentation(theme, { title: "Deck Title", author: "You" });

// ...one component call per slide...

await pres.writeFile({ fileName: "outputs/deck.pptx" });

For a topic-specific palette, makeTheme inherits the whole system in your colors:

const theme = C.makeTheme({
  primary: "1E2761",   // dominant ink — plates, dark bookend field, markers
  secondary: "CADCFC", // supporting tone — muted reversed text on dark
  accent: "F96167",    // sharp accent — stat numerals, emphasis
  headerFont: "Montserrat",
  bodyFont: "Inter",
  monoFont: "Fira Code",
});

makeTheme needs only primary; everything else is derived and overridable. Keys: primary, secondary, accent, background (light field, default white), text, muted, hairline, gridLight, gridDark, darkField (bookend background — defaults to primary if dark, else a computed near-black), and headerFont/bodyFont/monoFont (rejected if not installed in the sandbox — see SKILL.md Typography). All colors are 6-digit hex, # optional. Contrast-safe roles (onPrimary, onDark, accentStrong, …) are computed for you — you never pick a text color per slide.

Component catalog

Every component has the signature component(pres, theme, opts) and returns the created slide. Content beyond each limit is truncated with an ellipsis; oversized text shrinks within its box (down to a floor) before truncating.

Example: chart + stats + icons deck slice

const theme = C.defaultTheme();

C.titleSlide(pres, theme, { title: "Q4 in review.", subtitle: "Revenue, retention, roadmap.", meta: "ACME · Q4 2026" });

C.statCallouts(pres, theme, {
  title: "Where we landed",
  stats: [
    { value: "$7.1M", label: "Q4 revenue", desc: "Up 14% quarter over quarter", hero: true },
    { value: "98%", label: "Retention" },
    { value: "3.2x", label: "Pipeline coverage" },
  ],
});

// chart.py PNG sized to the chartSlide region (see charts.md)
C.chartSlide(pres, theme, {
  title: "Quarterly revenue",
  chart: { path: "outputs/chart-revenue.png" },
  takeaway: "Q4 broke the flat trend — enterprise deals drove the jump.",
});

// icons pre-rendered with icon.js in ink, placed bare (no circle backer):
//   node .opencode/skills/pptx/scripts/icon.js trending-up --color 0F0F0F -o outputs/icons/up.png
C.iconRow(pres, theme, {
  title: "What worked",
  items: [
    { iconPath: "outputs/icons/up.png", label: "Expansion", desc: "Existing accounts grew 22%" },
    { iconPath: "outputs/icons/shield.png", label: "Churn control", desc: "Saves program cut churn in half" },
  ],
});

Rules

• One dominant visual per slide. Each component already places exactly one (chart, image, icon row, stat row, one hero plate…). Don't add a second visual, don't set two hero stats, and don't stack components on one slide.
• Vary layouts across the deck — don't render five twoColumn slides in a row; mix in iconRow, statCallouts, timeline, quoteSlide.
• Render assets first, pass paths in: icons via icon.js (render in an ink color for the bare-icon treatment), charts via chart.py (charts.md), and user-supplied or workspace images. Components never fetch or generate assets.
• Never fabricate chart data — with no underlying series, use statCallouts (see charts.md grounding rule).
• Content limits are guards, not targets — a slide with 3 crisp bullets beats one with 6 truncated ones.
• QA still applies: run lint.py, then the visual pass (SKILL.md "QA"). Components make lint findings rare, not impossible — especially when you mix in raw pptxgenjs shapes.

Demo / smoke test

scripts/components_demo.js renders a deck (on defaultTheme()) with one slide per component and must stay lint-clean:

node .opencode/skills/pptx/scripts/components_demo.js outputs/components-demo.pptx
python .opencode/skills/pptx/scripts/lint.py outputs/components-demo.pptx