Acid Agency Deck

Supply the subject, audience, purpose, key messages and source facts, communication/content languages and exact slide count. Include opening and closing in that count unless specified otherwise. If the length is undecided, agree a count from the material and speaking time; twelve recipes do not impose twelve slides.

Approve a page sequence with one useful job per slide. For a sprint proposal, separate the motivating question, proposed schedule, team responsibilities, working principles, experiment and next decision. Replace fictional names and planning figures with authorized content, retaining uncertainty rather than inventing research or performance evidence.

Choose the picture route before generation: use supplied pictures first, then reuse the library, generate only gaps, or generate every asset anew. Reuse is the default when no choice is available. There is no fixed image quota; record page, subject, ratio, placement and saved result for each needed slot. Use each pictorial source once; cropping, rotating or recoloring the same source does not create another unique image. Functional icons may repeat.

Check catalog descriptions against the subject before embedding library IDs. A mismatched or unavailable picture leaves an identified frame that must be resolved or disclosed. For fresh art, follow the slot ratio in the style kit, not a conflicting example prompt ratio. Use built-in image generation or the supplied FAL helper with FAL_KEY; FAL submissions are paid, submitted once, then polled/fetched. Do not automatically resubmit a failed paid task. Without a supported generator, return to library reuse.

Compose plan.json from the selected style-kit recipes, assign text, pictures, alt text, icons and actual data by node ID, and remove unused objects. Run the bundled Python composition step, resolve unfilled images and leftover example content, then build the standalone HTML and run the deck check against the agreed count. Python 3 handles core building/checks; Node is used by the optional picture helpers. Keep assets embedded and the file below the package’s 20 MB ceiling; optimize and recheck if warned.

Inspect every page at presentation size over local HTTP: type hierarchy, density, contrast, arched crops, complete heads/hands, picture uniqueness, bounds, page numbering and notes. Check the schedule is labeled as a plan and supplied evidence has not become an exaggerated claim. Exercise text/block edits, picture changes, layout/color changes, undo/redo, notes, Save and reopen. Presentation mode should disable editing and hide idle controls.

Deliver the standalone HTML and explain Edit/E, browser-local recovery and Save (Cmd/Ctrl+S), which writes changes into a portable HTML file. Keep interface language separate from slide language; switching the UI does not translate content. CJK uses system fallbacks and RTL follows framework rules. For requested PPTX, export, run the supplied checker and inspect fonts/crops/layers in PowerPoint, Keynote or WPS; inspect printed PDF separately before calling either verified.