document-authoring

Document Authoring

1. Establish the requested format, audience, content and acceptance criteria from the brief and supplied references. Reuse source material; for complex work, track criteria and verification evidence in plan details.
2. Choose the creation tool based on the requested output:
   • Charts: use document.echarts.render with one named entry per requested chart and native ECharts JSON options. Ground the values in supplied/retrieved data, label units, and select only the requested image formats. Each chart becomes a separate SVG/PNG artifact. Use both formats when a vector document figure and raster preview are useful. Inspect a PNG preview and fix clipping or misleading axes before delivering it. Do not use image-generation models to invent or redraw quantitative charts.
   • Presentations: use document.slidev.create for an editable project, author slides.md and style.css with the file tool, and place selected chart/image assets in public/. Treat the scaffold as editable: owner choices for theme, layout, colors, typography, icons and animation override all defaults. Replace scaffold styles and components when needed; ensure additional themes have compatible installed dependencies. Use local Lucide icons and coherent cover/section/content layouts. Default to fully visible slides and a simple transition: fade between them. Animate mechanisms inside the slide automatically while it is active: moving evidence along a flow, state changes, process cycles or grounded chart evolution. Use CSS or v-motion with a static reduced-motion fallback. Avoid generic text/panel entrance and exit effects. Add click-triggered reveals (v-click or click motion variants) and elaborate slide transitions only when the owner explicitly requests them. Ground technical claims in retrieved context/source and label illustrative data. Batch independent grounding reads and author related files together. Use fenced code or HTML-escaped <pre v-pre><code> for literal examples; keep Vue markup balanced. Run inspect, then check; during repairs select affected options.slides. Targeted success has complete=false and cannot establish full-deck coverage. Run the default full check on the final source and require scope=full, complete=true and ok=true. Batch independent checks/previews and requested exports once source is stable; never edit files while those operations are reading them. Reuse current-run evidence and successful results while relevant source/assets are unchanged. Preview early/late motion frames and, only for requested staged reveals, initial/final click states; a passing check alone does not establish visual or animation quality. Finish with present to start/reuse a managed native Slidev server and open the deck in the host’s default browser. Return its audience and presenter links, Space/Right/Left navigation and f fullscreen control. Verify opening with the browser tool; if browserOpened=false, explain the reported issue and host-local URL scope. Use Satellite for device-side presentation when Leon runs remotely and ensure the project is on that device. Keep the session until the owner finishes, then stop its sessionId. Export web/PDF/PNG/PPTX downloads only when requested; opening a deck should not require extracting files or running commands. A web ZIP includes serve.mjs: extract and run node serve.mjs, then open its localhost URL; it can also be hosted as a static site. PDF/PNG and PowerPoint exports capture states rather than native browser motion. Normal PPTX contains slide images; editable PPTX may rasterize complex elements and needs fidelity review. Shared web decks omit notes by default; an optional source ZIP (includeSource=true) always contains them; omit that archive unless requested.
   • PDF: write a local .typ source with the file tool, then call document.typst.compile. Keep the source and selected assets together in a project directory. Use the smallest rootPath containing that project. Built-in/local assets require no generation-provider account or package download.
   • Editable Word: use document.document.create with format=docx. Typst does not export DOCX.
   • SVG/PNG: compile Typst with the requested format. Each selected page becomes an image artifact. For a standalone figure, set the page dimensions to fit the figure rather than exporting a full report page.
   • Plain text, CSV, Markdown and source files: use existing file writing.
   • Hosted generation or Office formats requiring a provider: inspect document.document.capabilities, then use generate with the configured defaults. Reserve generateWithModel for an explicitly owner-requested provider/model.