pptx-cli 1.3.2__tar.gz → 1.3.4__tar.gz

{pptx_cli-1.3.2 → pptx_cli-1.3.4}/.github/skills/pptx-deck-builder/SKILL.md

@@ -51,6 +51,34 @@ For consulting-style decks, write a **ghost deck** first — a title-only
 outline where each slide title states the takeaway (not the topic). The titles
 alone should tell a coherent story. See `references/mckinsey-style.md`.
 
+### Working from a YAML input file
+
+When the user provides a YAML (or similar structured) file that already
+contains slide content, treat it as the authoritative source. The file
+typically defines `slides:` with per-slide fields such as `title`, `body`,
+`notes`, `table`, `chart`, and `image`.
+
+**Carry over every field.** Walk through each slide in the input and map
+every field into the deck spec. The most common mistake is silently dropping
+fields that do not map to a placeholder — especially `notes`. Always include:
+
+- `title` and `body` → map to the layout's `title` and `content_1`
+- `notes` → map to the slide-level `notes:` key in the deck spec
+- `table` → map to a `{ kind: table, ... }` content block
+- `chart` → map to a `{ kind: chart, ... }` content block
+- `image` → map to a `{ kind: image, ... }` content block
+
+**Do not summarize, rewrite, or omit content** unless the user explicitly
+asks for editing. The goal is faithful conversion from the input format to
+a template-bound deck spec, not reinterpretation.
+
+**Checklist before building:** after writing the deck spec, verify that:
+
+1. The number of slides matches the input.
+2. Every `notes:` block from the input appears in the spec.
+3. Every table, chart, and image from the input is present.
+4. Source attributions are preserved.
+
 ### Step 1 — Initialize the manifest (one-time setup)
 
 Check if a manifest package already exists. If not, initialize from the

{pptx_cli-1.3.2 → pptx_cli-1.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pptx-cli
-Version: 1.3.2
+Version: 1.3.4
 Summary: Template-bound PowerPoint generation for enterprise decks
 Author: Thomas Rohde
 License: MIT License

{pptx_cli-1.3.2 → pptx_cli-1.3.4}/src/pptx_cli/__init__.py

@@ -2,4 +2,4 @@
 
 __all__ = ["__version__"]
 
-__version__ = "1.3.2"
+__version__ = "1.3.4"

{pptx_cli-1.3.2 → pptx_cli-1.3.4}/src/pptx_cli/commands/schema.py

@@ -46,6 +46,18 @@ def copy_to_clipboard(text: str) -> bool:
 # ---------------------------------------------------------------------------
 
 _GENERIC_SCHEMA = """\
+<output-format>
+IMPORTANT: Your output MUST be a YAML deck spec, not a binary .pptx file.
+Do NOT attempt to generate PowerPoint XML, base64 data, or any format
+other than the YAML shown below.  The `pptx deck build` CLI tool handles
+all PowerPoint rendering — you only provide the YAML.
+
+Preferred: offer the YAML as a downloadable file (e.g. a download link or
+file attachment named "deck.yaml") so the user can save it directly.
+Fallback: emit a single ```yaml code block the user can copy-paste into
+a .yaml file and then run `pptx deck build -f deck.yaml`.
+</output-format>
+
 <slide-schema>
 Use this schema to draft presentation content.  Layout assignment and
 template binding happen later, so focus on the slides themselves.