reports-pdfs-and-slide-automation
Reports, PDFs, and Slide Automation
Overview
Use this skill when the output is a deliverable rather than a standalone chart. That includes reports, briefing decks, PDFs, slide exports, document embeds, and reusable figure assets that other systems can place into files.
Default assumption: build figures as durable assets first, then compose them into documents. Do not rely on screenshots unless the workflow truly has no better option.
For editorial reports and infographic packages, use ../../references/foundations/editorial-infographic-system.md before layout. For visual stories that include animation, generated imagery, illustrated substrates, WebGL, particles, 3D, or scrollytelling, also use ../../references/foundations/art-directed-interactive-visual-stories.md. When page, slide, or figure composition materially affects interpretation, use ../../references/foundations/meaning-preserving-visual-design-workflow.md and ../../references/foundations/mobile-first-responsive-visualization.md for concept generation, user approval, mobile variants, and semantic design contracts. The deliverable should read as a sequence of claims supported by figures, not as a dashboard export.
For reports, decks, PDFs, and documents with multiple meaningful figures, use ../../references/foundations/embedded-visualization-self-use.md before page or slide composition. Each chart, map, table-graphic, inset, flow layer, static fallback, and export-only frame needs a specialist owner and mini-brief before it becomes a placed asset.