Name: Investigate PPTX Compatibility
Author: jongalloway

Prompt file imported from jongalloway/MarpToPptx (.github/prompts/investigate-pptx-compatibility.prompt.md). Copyright stays with the author.

Investigate a PPTX compatibility problem for this repository.

Use this prompt when a generated .pptx:

fails OpenXmlValidator
opens with a PowerPoint repair prompt
passes validation but still fails to open in PowerPoint
differs from a known-good reference package in suspicious ways

Repository rules:

PowerPoint compatibility is the real success criterion.
Passing OpenXmlValidator is necessary but not sufficient.
Prefer package-structure and relationship analysis before changing slide content logic.
Use dotnet run --project src/MarpToPptx.Cli -- ... for local renderer debugging, not dnx, unless the published tool path is the thing being tested.

Required references:

doc/pptx-compatibility-notes.md
scripts/README.md
doc/openxml-3.4.1-audit.md when the question involves SDK capabilities or package-shaping assumptions

Expected workflow:

Identify the failing artifact, scenario, or repro path.
Find the relevant renderer, validator, test, sample, or script entry points.
If needed, recommend or run the repo-standard validation flow in this order:
- targeted tests in tests/MarpToPptx.Tests
- local CLI generation
- .NET Open XML validation through src/MarpToPptx.OpenXmlValidator
- PowerPoint smoke flow on Windows when compatibility risk remains
Inspect likely package-shape causes before proposing renderer changes:
- required parts
- slide, layout, master, and theme relationships
- [Content_Types].xml
- relative vs absolute targets
- part inventory differences against a known-good package
If useful, compare against a PowerPoint-authored or other known-good reference package.
Summarize the most likely root cause, the evidence, and the smallest safe next change.

Output requirements:

Start with the most likely findings, ordered by severity or confidence.
Cite the concrete files, scripts, tests, or package parts that matter.
Distinguish clearly between:
- validator/schema failures
- package-shape or relationship failures
- unverified hypotheses
If you recommend a code change, prefer the smallest compatibility-focused change.
If you recommend more investigation, state the exact next command, script, or comparison to run.

Do not give generic Open XML advice when the repo’s own compatibility notes already define the expected package invariants.

Investigate a PPTX compatibility problem for this repository. Use this prompt when a generated `.pptx`: - fails `OpenXmlValidator` - opens with a PowerPoint repair prompt - passes validation but still fails to open in PowerPoint - differs from a known-good reference package in suspicious ways Repository rules: - PowerPoint compatibility is the real success criterion. - Passing `OpenXmlValidator` is necessary but not sufficient. - Prefer package-structure and relationship analysis before changing slide content logic. - Use `dotnet run --project src/MarpToPptx.Cli -- ...` for local renderer debugging, not `dnx`, unless the published tool path is the thing being tested. Required references: - `doc/pptx-compatibility-notes.md` - `scripts/README.md` - `doc/openxml-3.4.1-audit.md` when the question involves SDK capabilities or package-shaping assumptions Expected workflow: 1. Identify the failing artifact, scenario, or repro path. 2. Find the relevant renderer, validator, test, sample, or script entry points. 3. If needed, recommend or run the repo-standard validation flow in this order: - targeted tests in `tests/MarpToPptx.Tests` - local CLI generation - `.NET` Open XML validation through `src/MarpToPptx.OpenXmlValidator` - PowerPoint smoke flow on Windows when compatibility risk remains 4. Inspect likely package-shape causes before proposing renderer changes: - required parts - slide, layout, master, and theme relationships - `[Content_Types].xml` - relative vs absolute targets - part inventory differences against a known-good package 5. If useful, compare against a PowerPoint-authored or other known-good reference package. 6. Summarize the most likely root cause, the evidence, and the smallest safe next change. Output requirements: - Start with the most likely findings, ordered by severity or confidence. - Cite the concrete files, scripts, tests, or package parts that matter. - Distinguish clearly between: - validator/schema failures - package-shape or relationship failures - unverified hypotheses - If you recommend a code change, prefer the smallest compatibility-focused change. - If you recommend more investigation, state the exact next command, script, or comparison to run. Do not give generic Open XML advice when the repo’s own compatibility notes already define the expected package invariants.

{ "prompt": "Investigate a PPTX compatibility problem for this repository.\n\nUse this prompt when a generated `.pptx`:\n- fails `OpenXmlValidator`\n- opens with a PowerPoint repair prompt\n- passes validation but still fails to open in PowerPoint\n- differs from a known-good reference package in suspicious ways\n\nRepository rules:\n- PowerPoint compatibility is the real success criterion.\n- Passing `OpenXmlValidator` is necessary but not sufficient.\n- Prefer package-structure and relationship analysis before changing slide content logic.\n- Use `dotnet run --project src/MarpToPptx.Cli -- ...` for local renderer debugging, not `dnx`, unless the published tool path is the thing being tested.\n\nRequired references:\n- `doc/pptx-compatibility-notes.md`\n- `scripts/README.md`\n- `doc/openxml-3.4.1-audit.md` when the question involves SDK capabilities or package-shaping assumptions\n\nExpected workflow:\n1. Identify the failing artifact, scenario, or repro path.\n2. Find the relevant renderer, validator, test, sample, or script entry points.\n3. If needed, recommend or run the repo-standard validation flow in this order:\n - targeted tests in `tests/MarpToPptx.Tests`\n - local CLI generation\n - `.NET` Open XML validation through `src/MarpToPptx.OpenXmlValidator`\n - PowerPoint smoke flow on Windows when compatibility risk remains\n4. Inspect likely package-shape causes before proposing renderer changes:\n - required parts\n - slide, layout, master, and theme relationships\n - `[Content_Types].xml`\n - relative vs absolute targets\n - part inventory differences against a known-good package\n5. If useful, compare against a PowerPoint-authored or other known-good reference package.\n6. Summarize the most likely root cause, the evidence, and the smallest safe next change.\n\nOutput requirements:\n- Start with the most likely findings, ordered by severity or confidence.\n- Cite the concrete files, scripts, tests, or package parts that matter.\n- Distinguish clearly between:\n - validator/schema failures\n - package-shape or relationship failures\n - unverified hypotheses\n- If you recommend a code change, prefer the smallest compatibility-focused change.\n- If you recommend more investigation, state the exact next command, script, or comparison to run.\n\nDo not give generic Open XML advice when the repo’s own compatibility notes already define the expected package invariants.", "variables": [], "notes": "Investigate a PPTX that fails validation, opens with repair, or fails to open in PowerPoint Arguments: PPTX path, sample deck, failing test, or issue summary.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/jongalloway/MarpToPptx", "path": ".github/prompts/investigate-pptx-compatibility.prompt.md", "ref": "488e4ec40a8d6552aa93f46869583fc5990c9f5e", "url": "https://github.com/jongalloway/MarpToPptx/blob/488e4ec40a8d6552aa93f46869583fc5990c9f5e/.github/prompts/investigate-pptx-compatibility.prompt.md", "key": "jongalloway/MarpToPptx/.github/prompts/investigate-pptx-compatibility.prompt.md" } } }

Investigate PPTX Compatibility

About

Use it

Manifest

Reviews