guxiong108-beep/technical-ppt-builder

Technical PPT Builder

Build or improve editable PowerPoint decks through explicit planning, visual design, generation, and review gates. Preserve source meaning and never modify the user's original files.

Select the route

• For a new deck, follow Brief -> Outline -> Visual Strategy -> Generator -> Review.
• For an existing deck whose page count, order, template identity, and source meaning must remain locked, follow Beautifier -> Review.
• If the requested changes add or remove pages, redesign the sequence, replace the template, or rewrite the core message, use the new-deck route with the source deck as authorized material.
• If the user requests only a Brief, Outline, or Visual Strategy, stop after that stage passes its completion gate.
• Require Review for every task that creates or modifies a PPTX.

Read Workflow for the complete routing, transition gates, project-state model, naming rules, and completion criteria.

Choose the execution mode

• Use Continuous mode by default. Complete the required stages without routine pauses, update project state at each stage boundary, and pause only for a blocking source gap, material ambiguity, or decision outside prior authorization.
• Use Checkpointed mode only when the user explicitly requests staged confirmation. For a new deck, pause after Brief, Outline, and Visual Strategy. For beautification, pause after Diagnosis and Beautification Plan. After the final planned checkpoint, complete generation or execution and Review continuously.
• Keep route and mode separate: the route selects the work to perform; the mode selects how the user participates in decisions.
• Follow the user's requested slide language. When unspecified, use the dominant source language. Create a bilingual deck only when explicitly requested.

Load only the required guidance

• Read Brief to establish audience, purpose, source boundaries, gaps, and assumptions.
• Read Outline to define the argument and page sequence.
• Read Visual Strategy to create executable slide communication contracts.
• Read Generator before creating a new PPTX.
• Read Beautifier before improving an existing PPTX.
• Read Review before presenting a generated or beautified deck as reviewed.
• Read Design System for shared visual judgment.
• Read Visual Foundations when deck direction, typography, grid, hierarchy, page families, or layout patterns matter.
• Read Diagram Rules when a slide contains architecture, topology, process, branch, loop, boundary, spatial, parallel, many-to-many, or multi-relation meaning.
• Read Visual Assets when using images, icons, generated visuals, or PNG exports.
• Read Delivery and Quality for templates, rendering, structural inspection, evidence, and delivery checks.

Preserve source files

• Treat every user-provided file as read-only unless the user explicitly authorizes an in-place change.
• Never overwrite, rename, move, or delete an original PPTX or supporting source file.
• Create a new working PPTX for every generation or beautification task.
• If a target filename already exists, add _v2, _v3, or the next available version instead of replacing it.
• Use reviewed in a filename only after the Review gate passes.
• Use final only after the user explicitly approves final delivery.

Place outputs

Apply this priority order:

1. Use an output path explicitly provided by the user.
2. For one source PPTX, place primary PPTX outputs in that file's directory.
3. For multiple source files in one directory, place primary PPTX outputs in their shared directory.
4. For sources in different directories, use the primary source's directory; ask only if the primary source cannot be determined safely.
5. When no local source exists, use the user-selected workspace or the current task directory.
6. If the selected directory is not writable, stop and request a writable location.
7. Obey higher-priority host workspace rules when they require a different output location, and report the actual location.

Keep the primary working and reviewed PPTX files beside the source. Store persistent state, renders, inspections, and QA evidence under technical-ppt-builder-work/<task>/ in that same directory. Store disposable caches in the operating system temporary directory.

Maintain project state

Maintain one presentation_state.md for multi-stage generation or full-deck beautification. Record the route, mode, source boundary, constraints, decisions, assumptions, evidence paths, deviations, risks, review result, and actual artifact paths. Write human-readable state in the user's working language while keeping stable technical identifiers in English where useful.

Use the available presentation runtime

Use the presentation-generation skill or runtime available in the host environment as authoritative for implementation libraries, workspace setup, rendering, and structural inspection. Treat image generation, image search, Graphviz, and SVG conversion as supporting producers rather than the PPTX assembly runtime.

Preserve editability. Render every generated or modified deck, inspect its structure, repair must-fix defects, and refresh the evidence after repairs.

Complete the task

Complete only when:

• the requested route reaches its terminal stage;
• project state matches the actual artifacts and evidence;
• every generated or beautified PPTX passes Review;
• all must-fix items are repaired and rechecked;
• original files remain unchanged;
• source-locked beautification preserves its recorded page, template, content, and meaning constraints; and
• delivered filenames accurately indicate draft, reviewed, or final status.