ipIterPrompt

Pptx Quality Gates

Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity.

wshobson · agentsUpdated 2026-05-271,794 copies

Pptx Quality Gates — Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity. Imported from wshobson/agents (MIT).

SKILL.md

---
name: pptx-quality-gates
description: "Use when validating or repairing an editable PPTX deck for geometry, accessibility, native editability, source lineage, and OOXML package integrity."
---

# PPTX Quality Gates

Use this skill before delivering a generated PPTX. Treat deterministic failures as repair work, not exceptions.

## Workflow

1. Confirm the spec, builder, PPTX, source manifest, and audit paths.
2. Apply `references/audit-checklist.md` to the coordinate contract before building.
3. Reopen the PPTX and compare slide count, actual bounds, hidden slides, and requested geometry with the layout tree.
4. For production decks, run `pptx-reference-deck-analysis/scripts/validate_package.py` and save the JSON report.
5. Check document language, slide titles, meaningful-image alt text, reading order, table headers, and source references.
6. When a compatible renderer is already available, inspect previews for clipping, font fallback, contrast, crop, and hierarchy. Do not add a renderer dependency.
7. 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.

Run this skill on a real model without leaving the page. Every run is saved to your history for this skill.

How to use

  1. 1Save the content below as SKILL.md in your agent's skills directory (e.g. .claude/skills/<name>/SKILL.md).
  2. 2Or paste it directly into the conversation as context before asking the agent to do the task.
  3. 3Adjust any project-specific paths or conventions mentioned in the skill to match your setup.

Related

Inclusive Design Review — SaaS Dashboard

Review a design for exclusion beyond disability. Purpose-built for saas dashboard contexts.

4,309 copiesOpen ↗

Inclusive Design Review — Onboarding Flow

Review a design for exclusion beyond disability. Purpose-built for onboarding flow contexts.

1,656 copiesOpen ↗

Keyboard & Focus Spec — E-commerce Store

Specify complete keyboard interaction for a component/flow. Purpose-built for e-commerce store contexts.

3,310 copiesOpen ↗

Screen Reader Experience Design — E-commerce Store

Design what the flow sounds like, not just looks like. Purpose-built for e-commerce store contexts.

4,151 copiesOpen ↗