@ztffn/presentation-generator-plugin 1.1.4 → 1.2.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "presentation-generator",
   "description": "Generate complete graph-based presentations from natural language briefs and project documents. Includes a three-agent pipeline: content extraction, narrative design, and graph JSON compilation.",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "author": {
     "name": "Huma"
   },

package/agents/presentation-content.md

@@ -1,11 +1,9 @@
 ---
 name: presentation-content
 description: Extracts structured content briefs from project documents for presentation generation. Reads source files, identifies presentation-worthy content, and produces a canonical content brief JSON.
-tools:
-  - Read
-  - Glob
+tools: Read, Glob
 skills:
-  - presentation-generator/narrative/content-signals
+  - presentation-generator:content-signals
 ---
 
 # Content Extraction Agent

package/agents/presentation-design.md

@@ -1,16 +1,13 @@
 ---
 name: presentation-design
 description: Translates approved slide outlines into complete graph JSON with nodes, edges, positions, and visual treatments. Pure translation — never alters content or structure from the outline.
-tools:
-  - Read
-  - Write
-  - Bash
+tools: Read, Write, Bash
 skills:
-  - presentation-generator/system/node-schema
-  - presentation-generator/system/edge-conventions
-  - presentation-generator/system/layout-templates
-  - presentation-generator/system/positioning
-  - presentation-generator/examples/pitch-reference
+  - presentation-generator:node-schema
+  - presentation-generator:edge-conventions
+  - presentation-generator:layout-templates
+  - presentation-generator:positioning
+  - presentation-generator:pitch-reference
 ---
 
 # Design & JSON Generation Agent
@@ -83,14 +80,15 @@ All 8 valid handle IDs: `s-right`, `s-left`, `s-top`, `s-bottom`, `t-right`, `t-
 }
 ```
 
-4. Run `scripts/validate_draft.py` using Bash. This is a Python script — you must execute it, not read it. Reading the JSON file is not validation.
+4. Run the validator script using Bash. This is a Python script — you must execute it, not read it. Reading the JSON file is not validation.
+
+The script is bundled with the plugin. Find it and run it:
 
 ```bash
-python3 scripts/validate_draft.py presentations/{slug}/{slug}.json
+VALIDATE=$(find -L .claude ~/.claude -path "*/presentation-generator/scripts/validate_draft.py" 2>/dev/null | head -1)
+python3 "$VALIDATE" presentations/{slug}/{slug}.json
 ```
 
-If the working directory is different, use the absolute path to the script.
-
 The script prints either `OK  Presentation JSON is valid` (exit 0) or a list of `ERROR` lines (exit 1).
 
 If there are any `ERROR` lines:

package/agents/presentation-narrative.md

@@ -1,13 +1,11 @@
 ---
 name: presentation-narrative
 description: Designs narrative structure and slide outlines for graph-based presentations. Selects story frameworks, designs spine and drill-down topology, and writes detailed slide content outlines.
-tools:
-  - Read
-  - Write
+tools: Read, Write
 skills:
-  - presentation-generator/narrative/frameworks
-  - presentation-generator/narrative/slide-content
-  - presentation-generator/narrative/graph-topology
+  - presentation-generator:frameworks
+  - presentation-generator:slide-content
+  - presentation-generator:graph-topology
 ---
 
 # Narrative Design Agent

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ztffn/presentation-generator-plugin",
-  "version": "1.1.4",
+  "version": "1.2.0",
   "description": "Claude Code plugin for generating graph-based presentations",
   "bin": {
     "presentation-generator-plugin": "bin/index.js"

package/skills/{presentation-generator/narrative/content-signals.md → content-signals/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: content-signals
+description: Content signal extraction patterns and content brief schema for identifying presentation-worthy material from source documents.
+---
+
 # Content Extraction Signals
 
 Guidance for extracting presentation-worthy content from source documents.

package/skills/{presentation-generator/system/edge-conventions.md → edge-conventions/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: edge-conventions
+description: Authoritative reference for wiring navigation edges — handle IDs, bidirectional pairs, and validation checklist.
+---
+
 # Edge Conventions
 
 Authoritative reference for wiring navigation edges in the presentation graph.

package/skills/{presentation-generator/narrative/frameworks.md → frameworks/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: frameworks
+description: Proven narrative story structures for presentations, with selection guidance based on goal and audience.
+---
+
 # Narrative Frameworks
 
 Proven story structures for presentations. Select the right framework based on

package/skills/{presentation-generator/narrative/graph-topology.md → graph-topology/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: graph-topology
+description: How narrative structure maps to graph navigation — spine, drill-down, and hub topology patterns.
+---
+
 # Graph Topology for Presentations
 
 How narrative structure maps to graph navigation.

package/skills/{presentation-generator/system/layout-templates.md → layout-templates/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: layout-templates
+description: Decision guide mapping content signals to slide type, layout, background treatment, and visual configuration.
+---
+
 # Layout Templates & Design Decisions
 
 Decision guide for the design agent. Maps content signals from the slide outline

package/skills/{presentation-generator/system/node-schema.md → node-schema/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: node-schema
+description: Authoritative reference for SlideNodeData interface — all fields, types, and defaults for graph presentation nodes.
+---
+
 # Node Schema Reference
 
 Authoritative reference for the `SlideNodeData` interface.

package/skills/{presentation-generator/examples/pitch-reference.json → pitch-reference/SKILL.md}

@@ -1,6 +1,14 @@
-{
-  "_comment": "Reference example: 7-node presentation demonstrating key slide types. Trimmed from _temp/presentation-demo-output.json. Each node shows a different design pattern the design agent should know how to produce.",
+---
+name: pitch-reference
+description: Reference example of a complete 7-node presentation graph JSON demonstrating key slide types and edge wiring.
+---
+
+# Pitch Reference Example
 
+A 7-node presentation demonstrating key slide types. Each node shows a different design pattern the design agent should know how to produce.
+
+```json
+{
   "_node_1_comment": "COVER NODE: centered, branded, brand font. Sets the context. No content-heavy text.",
   "_node_2_comment": "CONTENT NODE: standard bullets, left-aligned (centered:false). Includes notes field for speaker context. The workhorse slide type.",
   "_node_3_comment": "TWO-COLUMN NODE: layout:two-column splits on --- delimiter. Good for comparison or text+visual.",
@@ -153,3 +161,4 @@
     { "id": "e-end-bgimage", "source": "end", "target": "feat-bgimage", "sourceHandle": "s-left", "targetHandle": "t-right" }
   ]
 }
+```

package/skills/{presentation-generator/system/positioning.md → positioning/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: positioning
+description: Grid system and placement rules for positioning nodes on the graph canvas.
+---
+
 # Node Positioning
 
 How to place nodes on the graph canvas for a clean, readable layout in the editor.

package/skills/presentation-generator/SKILL.md

@@ -42,12 +42,22 @@ If no documents are provided, skip Phase 2 and construct a minimal content brief
 
 ## Phase 2 — Content Extraction
 
-Invoke the `presentation-content` sub-agent:
+Delegate content extraction to the specialist agent using the Task tool:
 
 ```
-Agent: presentation-content
-Input: List of document paths from the user
-Output: _temp/presentation-content-brief.json
+Task tool:
+  subagent_type: "presentation-content"
+  description: "Extract content brief"
+  prompt: |
+    Read these source documents and extract a structured content brief:
+
+    Documents:
+    - [list each file path from Phase 1]
+
+    Audience: [audience identified in Phase 1]
+    Goal: [goal identified in Phase 1]
+
+    Write the result to _temp/presentation-content-brief.json
 ```
 
 The content agent reads all source documents and writes a structured content brief.
@@ -72,12 +82,20 @@ If any check fails, ask the user ONE targeted question to fill the gap. Do not p
 
 ## Phase 3 — Narrative Design
 
-Invoke the `presentation-narrative` sub-agent:
+Delegate narrative design to the specialist agent using the Task tool:
 
 ```
-Agent: presentation-narrative
-Input: Reads _temp/presentation-content-brief.json
-Output: _temp/presentation-outline.md
+Task tool:
+  subagent_type: "presentation-narrative"
+  description: "Design narrative outline"
+  prompt: |
+    Read the content brief at _temp/presentation-content-brief.json and design
+    the narrative structure for this presentation.
+
+    Audience: [audience from Phase 1]
+    Goal: [goal from Phase 1]
+
+    Write the result to _temp/presentation-outline.md
 ```
 
 The narrative agent selects a story framework, designs the spine and drill-down structure, and writes a detailed slide outline.
@@ -114,12 +132,21 @@ This loop continues until the user explicitly approves.
 
 ## Phase 5 — Design and JSON Generation
 
-Invoke the `presentation-design` sub-agent:
+Delegate design and JSON generation to the specialist agent using the Task tool:
 
 ```
-Agent: presentation-design
-Input: Reads _temp/presentation-outline.md
-Output: presentations/{slug}/{slug}.json
+Task tool:
+  subagent_type: "presentation-design"
+  description: "Generate presentation JSON"
+  prompt: |
+    Read the approved outline at _temp/presentation-outline.md and translate it
+    into a complete presentation graph JSON.
+
+    Presentation slug: {slug}
+    Output path: presentations/{slug}/{slug}.json
+
+    After writing the JSON, run the validator script and fix any errors until
+    it passes. Include the validator terminal output in your completion message.
 ```
 
 The design agent translates each slide into a fully specified graph node, wires all edges with bidirectional pairs, and validates the result.
@@ -158,9 +185,9 @@ Replace the PLACEHOLDER string with the returned URL after upload.
 
 | Agent | Skills Loaded | Purpose |
 |---|---|---|
-| `presentation-content` | `narrative/content-signals` | Extract structured brief from documents |
-| `presentation-narrative` | `narrative/frameworks`, `narrative/slide-content`, `narrative/graph-topology` | Design story structure and slide content |
-| `presentation-design` | `system/node-schema`, `system/edge-conventions`, `system/layout-templates`, `system/positioning`, `examples/pitch-reference` | Translate outline to valid graph JSON |
+| `presentation-content` | `content-signals` | Extract structured brief from documents |
+| `presentation-narrative` | `frameworks`, `slide-content`, `graph-topology` | Design story structure and slide content |
+| `presentation-design` | `node-schema`, `edge-conventions`, `layout-templates`, `positioning`, `pitch-reference` | Translate outline to valid graph JSON |
 
 ## Working Without Documents
 

package/skills/{presentation-generator/narrative/slide-content.md → slide-content/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: slide-content
+description: Quality guide for writing individual slide content — density rules, assertion-evidence structure, headlines, speaker notes.
+---
+
 # Slide Content Quality Guide
 
 How to write individual slide content at a high quality level.