PPTX Quality Gates
Use this skill before delivering a generated PPTX. Treat deterministic failures as repair work, not exceptions.
Workflow
- Confirm the spec, builder, PPTX, source manifest, and audit paths.
- Apply
references/audit-checklist.md to the coordinate contract before building.
- Reopen the PPTX and compare slide count, actual bounds, hidden slides, and requested geometry with the layout tree.
- For production decks, run
pptx-reference-deck-analysis/scripts/validate_package.py and save the JSON report.
- Check document language, slide titles, meaningful-image alt text, reading order, table headers, and source references.
- When a compatible renderer is already available, inspect previews for clipping, font fallback, contrast, crop, and hierarchy. Do not add a renderer dependency.
- Repair the spec or task-local builder, rebuild, and rerun the same checks.
Required artifacts
Keep the spec, PPTX, build record, geometry audit, accessibility audit, package report, and source manifest together. Report any documented exception with slide ID, object ID, owner, reason, and review date.
Pass criteria
Zero content collisions, text overflows, unsafe content bounds, invalid positive geometry, and package-integrity errors. Meaningful slide content must remain native editable objects; images support rather than replace it.
See references/audit-checklist.md for the complete checklist.
1---2name: pptx-quality-gates3description: Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity.4---5
6# PPTX Quality Gates
7
8Use this skill before delivering a generated PPTX. Treat deterministic failures as repair work, not exceptions.
9
10## Workflow
11
121. Confirm the spec, builder, PPTX, source manifest, and audit paths.
132. Apply `references/audit-checklist.md` to the coordinate contract before building.
143. Reopen the PPTX and compare slide count, actual bounds, hidden slides, and requested geometry with the layout tree.
154. For production decks, run `pptx-reference-deck-analysis/scripts/validate_package.py` and save the JSON report.
165. Check document language, slide titles, meaningful-image alt text, reading order, table headers, and source references.
176. When a compatible renderer is already available, inspect previews for clipping, font fallback, contrast, crop, and hierarchy. Do not add a renderer dependency.
187. Repair the spec or task-local builder, rebuild, and rerun the same checks.
19
20## Required artifacts
21
22Keep the spec, PPTX, build record, geometry audit, accessibility audit, package report, and source manifest together. Report any documented exception with slide ID, object ID, owner, reason, and review date.
23
24## Pass criteria
25
26Zero content collisions, text overflows, unsafe content bounds, invalid positive geometry, and package-integrity errors. Meaningful slide content must remain native editable objects; images support rather than replace it.
27
28See `references/audit-checklist.md` for the complete checklist.
majiayu000