slide-factory/docs/google-slides-workflow.md

Google Slides Workflow

Slide Factory supersedes the older AgentPlane Google Slides project as the active slide-generation product. The older project remains useful as a brand-safe Google Slides renderer pattern and is now folded into this repo as implementation guidance.

Source

Prior project:

/Users/tars/AgentPlane/projects/google-slides

Key reusable assets:

• Template inventory workflow.
• Container/object-id mapping.
• Brand-safe deck mutation rules.
• Contact sheet visual QA.
• Container-oriented deck spec schema.

Operating Rule

Treat Google Slides templates as design systems. A Slide Factory Google Slides renderer should copy a template first, inspect its native containers, then fill existing text containers by object ID. It should create new page elements only when the user explicitly permits that or when no usable container exists.

Brand-Safe Flow

1. Copy the template deck.
2. Generate a template inventory.
3. Choose slides by container pattern.
4. Delete existing text and insert generated text into existing containers.
5. Delete unused template slides.
6. Render thumbnails and a contact sheet.
7. Patch copy density before changing layout geometry.

Local Skill Scripts

The current implementation helpers still live in the local Codex skill until they are ported into Slide Factory packages:

/Users/tars/.codex/skills/google-slides/scripts/

Primary scripts:

• slides_template_inventory.py
• slides_contact_sheet.py
• slides_structured_deck.py
• slides_container_map.py

Contract Bridge

Slide Factory's current DeckSpec is PPTX-oriented. Google Slides export should use an adapter step that maps the internal DeckSpec into the container-based Google Slides schema at:

schemas/google-slides-deck-spec.schema.json

Do not mutate live/private Google Drive files directly from the planner. The renderer should work from a copied template deck and return the edit URL, presentation ID, source template, target folder, and contact sheet evidence.

Handoff Evidence

At handoff, include:

• Deck title.
• Presentation ID and edit URL.
• Source template and folder.
• Auth account used.
• Contact sheet path.
• Whether brand-safe mode was used.
• Slides with overflow risk or weak template matches.