# Pptx Slide Specification

> Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.

Source: https://skillsagentes.com/skills/wshobson/agents/pptx-slide-specification
Repository: https://github.com/wshobson/agents
Author: wshobson
License: MIT
Updated: hace 27 días
Context cost: 25 tok installed, 489 tok once triggered, 859 tok with every bundled file
Bundle: 2 files, 3 KB
Permissions requested: none declared

## Install

```bash
npx -y skills add wshobson/agents --skill pptx-slide-specification --agent claude-code
```

## What it does

- Define un contrato JSON estricto con coordenadas explícitas (`layout_tree`) para diapositivas de PPTX editables
- Especifica campos obligatorios por objeto: `id`, `kind`, `role`, `classification`, `content`, `style`, `bbox`, `z_index`
- Fija reglas de autoría: márgenes seguros, tamaño mínimo de texto (9pt), IDs estables, grids compartidos
- Describe el contrato de construcción: mapear bboxes con `Inches(...)`, rechazar geometría cero o negativa

## Use it when

- Al redactar o reparar una especificación JSON coordinate-explicit para un PPTX editable

## What triggers it

- "Genera el JSON layout_tree para esta presentación PPTX"
- "Repara la especificación de diapositivas con coordenadas explícitas"
- "Crea el contrato de bboxes en pulgadas para mi deck editable"

## Before you install

- Requiere consultar references/layout-contract.md para el esquema compacto y guía de reparación.

## Files

- SKILL.md — 2 KB
- references/layout-contract.md — 1 KB

## SKILL.md

Reproduced verbatim from wshobson/agents under MIT. This section is the upstream document and is in English.

# PPTX Slide Specification

Author final coordinates directly in `layout_tree`. No renderer may decide placement, shrink text, or infer layout after the audit.

## Required contract

- The root JSON contains `summary` and `slides`.
- Every slide has a stable `id`, a message-led `title`, an accessibility reading order, and a complete `layout_tree`.
- A layout tree declares slide size, root group, id-keyed groups and objects, final inch bboxes, styles, z-indexes, and classifications.
- Every meaningful object has `id`, `kind`, `role`, `classification`, `content`, `style`, `bbox`, and `z_index`.
- Production `summary` contains an explicit `layout_policy` (safe margin, content bottom, footer top, minimum gap) and accessibility metadata.

## Authoring rules

1. Use stable readable IDs, absolute groups, and positive inch dimensions.
2. Keep normal content inside the safe margin and above the footer rail. Only background `layout_design` objects may be full bleed.
3. Use native `text`, `shape`, `line`, `table`, and `image` objects. Recreate labels and values from any supporting visual as native objects.
4. Give meaningful images alt text. Record `source_ref` for sourced claims.
5. Keep content text at 9 pt or greater; shorten, resize, or split dense content before reducing type.
6. Use shared grids, consistent gaps, explicit color, explicit font size, and an intentional z-order.

## Build contract

A task-local builder starts from a blank slide layout and maps all bboxes with `Inches(...)`. Explicitly set wrapping, disabled auto-size, text insets, anchors, alignment, fonts, colors, line settings, image aspect ratio, and hidden-slide state. Reject zero or negative geometry before adding an object.

See `references/layout-contract.md` for the compact schema and repair guidance.

---

Skills Agentes — https://skillsagentes.com/skills/wshobson/agents/pptx-slide-specification