design-render

Design Render

Turn a validated semantic-composition@2 into a client-grade deliverable and hand back its files. The platform route delegates PPTX creation to the host presentation skill; HTML follows this plugin's DOM contract. On every route, design-verify independently gates handover. Never edit a rendered page, deck or composition to make a check pass: frozen copy, unit order and source lineage are exactly what they protect.

Every delivery contains the native artifact, platform provenance, independent verification and visual review.

Inputs

• A normalized brief — the data of a successful publishing-validate normalize run, saved as its own JSON file.
• A semantic composition — the data of a successful design-compose compose run whose targets include the target to render.
• A theme — the theme_path from the manage-themes selection handoff, or a theme directory. Its directory name must equal the composition's design_system.name, and it must ship the authoritative tokens/*.json carrying the token roles listed in ${CLAUDE_PLUGIN_ROOT}/references/design-render.md; the pptx target also needs its colour tokens in hex. Every bundled theme qualifies; a tier-0 theme (theme.md only) derives its tokens through manage-themes Operation 7. A theme may also ship licensed faces, one per weight of a family, declared in its assets/fonts/faces.json beside each face's licence; the html target embeds every face of the copy family, each under its declared weight (declaration fields: design-render.md §Fonts). The bundled cogni-work theme ships DM Sans Regular and Bold.
• The language — taken from the brief's metadata; pass --language for a direct brief that does not state one (for example --language de).
• The narrative — optional context only. Never use it as a source of deliverable copy.

Platform route — PPTX

Resolve the host presentation skill

Resolve by host, in this order. On Codex, select the bundled presentations:Presentations skill even when document-skills:pptx is installed. On an Anthropic host, select its installed anthropic-skills:pptx or document-skills:pptx capability. On another host, select an installed skill whose description explicitly claims .pptx creation. Rely on the host's normal description-based skill triggering; do not create or consult a renderer registry. Load the selected theme as the design system. Its token files under tokens/, their compiled tokens.resolved.json when present, assets/fonts/faces.json when shipped, and theme.md are authoritative when another brand skill disagrees. Resolve semantic dark-surface roles to existing theme colors: use explicit bg-dark / text-on-dark tokens when present; otherwise map them to the theme's existing primary / bg colors and record that mapping in provenance and visual review. Invent no color.