pptx-slide-specification
wshobson/agents
Author coordinate-explicit JSON specifications for editable PPTX decks with precise layout control.
What is pptx-slide-specification?
This skill enables you to create and repair PPTX slide decks by writing detailed JSON specifications that define exact coordinates, styles, and accessibility metadata. Use it when you need pixel-perfect control over slide layout without relying on automatic rendering or text shrinking.
- Define slide layouts with absolute inch-based bounding boxes for all objects
- Specify complete styling including fonts, colors, z-indexes, and text properties
- Declare accessibility reading order and meaningful object classifications
- Enforce safe margins, footer rails, and content placement rules
- Build native text, shape, line, table, and image objects with explicit properties
- Validate geometry and reject invalid dimensions before rendering
How to install pptx-slide-specification
npx skills add https://github.com/wshobson/agents --skill pptx-slide-specification- Node.js environment with npx available
- Understanding of PPTX structure and coordinate systems
- Familiarity with JSON schema and layout specifications
How to use pptx-slide-specification
- 1.Install the skill using: npx skills add https://github.com/wshobson/agents --skill pptx-slide-specification
- 2.Define your presentation structure with a root JSON containing summary and slides array
- 3.For each slide, create a layout_tree with stable IDs, groups, and coordinate-explicit objects
- 4.Specify every object's bbox in inches, style properties, z-index, and accessibility role
- 5.Ensure all content stays within safe margins and above footer rails
- 6.Validate all geometry is positive and non-zero before building
- 7.Use the layout-contract.md reference to map bboxes and set rendering properties
Use cases
- Creating presentation decks where layout precision is critical for brand compliance
- Repairing existing PPTX files by rewriting their coordinate specifications
- Generating accessible presentations with explicit reading order and alt text
- Building templated slide systems with consistent grids and spacing
- Authoring data-driven presentations where content must fit predetermined layouts
- Presentation automation engineers
- Accessibility-focused developers
- Technical documentation teams
- Enterprise template builders
- Agents authoring or modifying PPTX files programmatically
pptx-slide-specification FAQ
No. The specification is coordinate-explicit and final. No renderer may decide placement, shrink text, or infer layout after the audit.
Bounding boxes are specified in inches using absolute positioning within the slide layout.
Every slide must declare an accessibility reading order, and every meaningful object must have a role and classification. Provide alt text for images and record source references for sourced claims.
Yes, only background layout_design objects may be full bleed. All normal content must stay inside the safe margin and above the footer rail.
Native objects include text, shape, line, table, and image. Recreate labels and values from visuals as native objects rather than using grouped graphics.
Full instructions (SKILL.md)
Source of truth, from wshobson/agents.
name: pptx-slide-specification description: "Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck."
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
summaryandslides. - Every slide has a stable
id, a message-ledtitle, an accessibility reading order, and a completelayout_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, andz_index. - Production
summarycontains an explicitlayout_policy(safe margin, content bottom, footer top, minimum gap) and accessibility metadata.
Authoring rules
- Use stable readable IDs, absolute groups, and positive inch dimensions.
- Keep normal content inside the safe margin and above the footer rail. Only background
layout_designobjects may be full bleed. - Use native
text,shape,line,table, andimageobjects. Recreate labels and values from any supporting visual as native objects. - Give meaningful images alt text. Record
source_reffor sourced claims. - Keep content text at 9 pt or greater; shorten, resize, or split dense content before reducing type.
- 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.
Related skills
More from wshobson/agents and the wider catalog.
pptx-visual-assets
Select and place approved icons, images, SVGs, and diagrams in PowerPoint decks while preserving editability.
preference-optimization
Align fine-tuned models with preference data using DPO, ORPO, KTO, or SimPO.
projection-patterns
Build read models and projections from event streams for CQRS and event-sourced systems.
prometheus-configuration
Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications.
prompt-engineering-patterns
Master advanced prompt engineering techniques to maximize LLM performance and reliability.
protect-mcp-setup
Cryptographic policy enforcement and Ed25519-signed audit receipts for Claude Code tool calls.