Skip to content
Development
Skill

/attentive-pixel-perfect-slides

Use when creating, converting, editing, or QAing Attentive PowerPoint decks with the canonical 2026 template, including new presentations, rebranding existing decks, and checking brand or layout fidelity.

From plugin
rules-for-claude
415 skills9 hooks

Claude Code

$ npx -y skills add chancegraff/rules-for-claude --skill attentive-pixel-perfect-slides --agent claude-code

SKILL.md

attentive-pixel-perfect-slides.SKILL.md
name: attentive-pixel-perfect-slides
description: Use when creating, converting, editing, or QAing Attentive PowerPoint decks with the canonical 2026 template, including new presentations, rebranding existing decks, and checking brand or layout fidelity.

Attentive Pixel-Perfect Slides

Create editable `.pptx` decks by duplicating and filling approved slides from the bundled 164-slide Attentive template. Vanessa Kuras maintains this skill.

Non-negotiable method

Every output slide must trace to one physical canonical slide number. Use `attentive-slide-builder/build_from_plan.py`, which duplicates the selected slide and replaces only its content. Never recreate a template layout with blank slides, `add_slide()` plus shapes, or hand-written OOXML geometry.

If no canonical slide fits, shorten the copy, split the content, or select a different canonical slide. Build a custom layout only after the user explicitly approves that exception.

Before beginning, read the resources that match the task:

  • New deck: [brand voice](references/brand-voice.md),

[formatting](references/slide-formatting.md), [design](references/slide-design.md), and [builder](references/slide-builder.md).

  • Existing-deck conversion: follow the structural extraction and mapping-approval

steps below before building.

  • Final QA: read the [QA checklist](references/slide-builder/qa-checklist.md).
  • Brand details: open [voice and tone](references/brand-voice/voice-and-tone.md),

[messaging](references/brand-voice/messaging.md), [mechanics](references/brand-voice/mechanics.md), [terms and trademarks](references/brand-voice/terms-and-trademarks.md), or the [final checklist](references/brand-voice/checklists.md) as needed.

  • Layout selection details: open

[archetypes](references/slide-design/archetypes.md), [design tokens](references/slide-design/design-tokens.md), and [slot contracts](references/slide-formatting/slot-contracts.md) as needed.

Workflow

1. Confirm the brief without inventing facts

Establish the audience, purpose, source content, and approximate slide count. Ask only for missing information that would materially change the deck. Never invent metrics, dates, owners, customer claims, links, or launch status. When the user asks you to use judgment, make conservative assumptions and list them at handoff.

For an existing deck, keep its structure intact and extract it directly:

python3 attentive-slide-builder/extract_source.py source.pptx \
  --rank --images-dir source-images --out source-blocks.json

Show a source-to-canonical mapping table and obtain approval before building. The table must include source slide, narrative purpose, proposed canonical slide, and any content that must be shortened, split, or omitted.

2. Write Attentive copy

Apply [brand voice](references/brand-voice.md) to every topic label, title, body, bullet, statistic, quote, and caption. Keep content-slide headers short enough to remain on one line. Preserve trademarks and approved product names exactly.

3. Check capacity, then choose canonical slides

Formatting comes before design. Use the slot contracts and fit rules to determine whether each block fits. Never truncate. Compress, split, or paginate content that does not fit.

Choose canonical slides by purpose and density using the archetypes and the machine-readable builder data. Inspect the chosen slide and its known traps instead of rescanning the entire template:

python3 attentive-slide-builder/build_from_plan.py --inspect 24
python3 attentive-slide-builder/slide_facts.py --slide 24

Answer these questions for every slide:

1. Which canonical slide am I duplicating? 2. Why does it fit the content? 3. Which existing placeholders am I replacing? 4. Will the content fit without changing template geometry? 5. If not, should I compress, split, or choose another template?

Pay special attention to repeated slots, reading order, positive/negative variants, roadmap badges, inherited image crops, stock photography, comments, speaker notes, hyperlinks, and empty placeholders. `slide_facts.py` records the known traps.

4. Create and preflight the plan

Store the plan and output deck in the user's working directory, not inside this skill. A slide number always means “duplicate this physical canonical slide,” never “rebuild this design.”

{
  "template": "Template—2026 NEW Attentive Company Deck Template.pptx",
  "slides": [
    {
      "template_slide": 16,
      "note": "cover",
      "text": {
        "Insert the name of the deck here.": "Six reasons to stay with Attentive"
      }
    },
    {
      "template_slide": 24,
      "note": "agenda",
      "text": {
        "Section 01": "Overview",
        "Section 02": "Results"
      }
    }
  ]
}

Matching is literal, so run `--inspect` before authoring each map. For repeated placeholders, use the builder's per-shape `shapes`, `runs`, or `tables` fields; do not use a whole-slide text replacement that would give siblings identical copy.

python3 attentive-slide-builder/preflight_lint.py /path/to/plan.json --strict

Resolve every overflow, unmatched key, invalid slide number, monotony finding, and transition inconsistency before building. Do not use `--force` or `--no-lint` for a deliverable deck.

5. Build and verify

The scripts require Python 3 with `python-pptx`. Check the current environment first. If it is unavailable, use an already-configured compatible runtime or tell the user what is missing. Do not install packages into the runtime while using this skill.

python3 attentive-slide-builder/build_from_plan.py \
  /path/to/plan.json /path/to/deck.pptx

Post-build structural verification runs automatically. If LibreOffice and Poppler are already available, add `--verify-render` and inspect every rendered slide at full size. Do not install system software as part of a deck request.

Before delivery, confirm:

  • Every output slid
Read more
@chancegraff
Ships withrules-for-claude

My global Claude Code setup, mirrored from ~/.claude: the rules, the hook scripts that enforce them, and the global CLAUDE.md.

Stars on GitHub

Momentum

stars in total
4
Star history of chancegraff/rules-for-claude on GitHub, a chart by star-history.com

Other skills on rules-for-claude.

archify

archify

Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone…

pr-review

pr-review

How to answer review feedback on a pull request. Load when a bot or human reviewer leaves findings, when the base branch moves…

docx

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx).…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills12d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react3d252k
@facebook@facebookInstall Skill

Questions about attentive-pixel-perfect-slides.

Which coding agents can use attentive-pixel-perfect-slides?
attentive-pixel-perfect-slides installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.