@ztffn/presentation-generator-plugin 1.3.3 → 1.3.6

package/.claude-plugin/plugin.json

@@ -1,10 +1,11 @@
 {
   "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.3.1",
+  "description": "Generate complete graph-based presentations from natural language briefs and project documents. Pipeline: content extraction, narrative design, deterministic graph generation, and visual styling.",
+  "version": "1.3.6",
   "author": {
     "name": "Huma"
   },
   "homepage": "https://github.com/huma/humashowcase",
-  "keywords": ["presentation", "slides", "react-flow", "graph", "pitch deck"]
+  "keywords": ["presentation", "slides", "react-flow", "graph", "pitch deck"],
+  "hooks": "./hooks/hooks.json"
 }

package/README.md

@@ -1,10 +1,10 @@
 # Presentation Generator Plugin
 
-Generates complete graph-based presentations from a natural language brief and optional project documents. Uses a three-agent pipeline: content extraction → narrative design → graph JSON compilation.
+Generates complete graph-based presentations from a natural language brief and optional project documents. Uses a two-agent + script pipeline: content extraction → narrative design → deterministic graph generation → visual styling.
 
 ## What it produces
 
-A `_temp/presentation-draft.json` file you import directly into the graph editor at `/present/plan` via **New presentation → Import JSON**. The result is a fully navigable presentation with correct edge wiring, positioned nodes, and visual treatments applied.
+A `presentations/{slug}/{slug}.json` file you import directly into the graph editor at `/present/plan` via **New presentation → Import JSON**. The result is a fully navigable presentation with correct edge wiring, positioned nodes, and visual treatments applied.
 
 ## Install
 
@@ -81,22 +81,25 @@ User Brief + Documents
         ↓
   [3] User Approval           →  confirm or revise structure
         ↓
-  [4] Design & JSON           →  _temp/presentation-draft.json
+  [4] Graph Generation        →  presentations/{slug}/{slug}.json  (script)
         ↓
-  [5] Delivery                →  import instructions + media checklist
+  [5] Visual Styling          →  styled JSON  (agent)
+        ↓
+  [6] Delivery                →  import instructions + media checklist
 ```
 
 You review and approve the structure before any JSON is generated. If the structure needs changes, describe them and Claude revises before proceeding.
 
-## Agents
+## Agents and scripts
 
-| Agent | Role |
-|---|---|
-| `presentation-content` | Reads source documents, extracts a structured content brief |
-| `presentation-narrative` | Selects a narrative framework, designs spine and drill-downs, writes slide content |
-| `presentation-design` | Translates the approved outline into valid graph JSON |
+| Component | Type | Role |
+|---|---|---|
+| `presentation-content` | agent | Reads source documents, extracts a structured content brief |
+| `presentation-narrative` | agent | Selects a narrative framework, designs spine and drill-downs, writes slide content |
+| `outline_to_graph.py` | script | Deterministic converter: parses outline markdown, emits valid ReactFlow graph JSON |
+| `presentation-style` | agent | Applies visual treatments (layout, backgrounds, charts, branding) to the valid JSON |
 
-Each agent loads only the knowledge it needs — narrative agents never see layout decisions; design agents never read source documents.
+Content and narrative agents never see layout decisions; the styling agent never reads source documents. The script handles all structural correctness (node wrappers, edge wiring, positions) mechanically.
 
 ## Output files
 
@@ -105,14 +108,14 @@ Each agent loads only the knowledge it needs — narrative agents never see layo
 | `_temp/presentation-content-brief.json` | Content agent | Structured brief passed to narrative agent |
 | `_temp/presentation-outline.md` | Narrative agent | Human-readable structure for user approval |
 | `_temp/presentation-plan.md` | Orchestrator | Folder-tree view shown during approval step |
-| `_temp/presentation-draft.json` | Design agent | Final graph JSON for import |
+| `presentations/{slug}/{slug}.json` | Script + styling agent | Final graph JSON for import |
 
 ## After import
 
 1. Open `/present/plan` in the app
 2. Click **New presentation**
 3. Choose **Import JSON**
-4. Select `_temp/presentation-draft.json`
+4. Select `presentations/{slug}/{slug}.json`
 
 If any slides require video backgrounds, Claude lists them in the delivery summary with upload instructions.
 
@@ -142,7 +145,7 @@ presentation-generator-plugin/
 ├── agents/
 │   ├── presentation-content.md
 │   ├── presentation-narrative.md
-│   └── presentation-design.md
+│   └── presentation-style.md
 ├── skills/
 │   ├── presentation-generator/
 │   │   ├── SKILL.md                # Orchestrator skill
@@ -151,7 +154,14 @@ presentation-generator-plugin/
 │   ├── frameworks/SKILL.md         # Narrative frameworks
 │   ├── slide-content/SKILL.md      # Slide writing quality
 │   ├── graph-topology/SKILL.md     # Spine/drill-down structure
-│   └── graph-json-spec/SKILL.md    # Complete graph JSON spec (design agent)
-└── scripts/
-    └── validate_draft.py
+│   ├── graph-json-spec/SKILL.md    # Node schema, edge wiring, positioning grid
+│   └── slide-recipes/SKILL.md      # Design decisions, visual intent, slide recipes
+├── scripts/
+│   ├── outline_to_graph.py         # Deterministic outline-to-graph converter
+│   └── validate_draft.py           # Validates generated JSON against renderer types
+└── hooks/
+    ├── hooks.json
+    ├── enforce-style-schema.sh     # PreToolUse: injects schema rules into styling agent
+    ├── pre-validate-presentation-json.sh   # PreToolUse: blocks invalid JSON writes
+    └── validate-presentation-json.sh       # PostToolUse: validates after Write/Edit
 ```

package/agents/presentation-content.md

@@ -14,8 +14,7 @@ You are a content extraction specialist. Your job is to read source documents an
 
 ### Step 1 — Load your skill files
 
-Read this file before doing anything else:
-- Find and read the file matching `**/presentation-generator/skills/content-signals/SKILL.md`
+Read the skill file at the explicit path provided by the orchestrator in your prompt. The path will look like `{PLUGIN_ROOT}/skills/content-signals/SKILL.md`.
 
 This file defines the content brief schema, signal priorities, validation rules, and strong/weak examples. You must follow it exactly.
 

package/agents/presentation-narrative.md

@@ -16,10 +16,10 @@ You are a narrative design specialist. Your job is to take a structured content
 
 ### Step 1 — Load your skill files
 
-Read these three files before doing anything else:
-- Find and read the file matching `**/presentation-generator/skills/frameworks/SKILL.md`
-- Find and read the file matching `**/presentation-generator/skills/slide-content/SKILL.md`
-- Find and read the file matching `**/presentation-generator/skills/graph-topology/SKILL.md`
+Read the skill files at the explicit paths provided by the orchestrator in your prompt. The paths will look like:
+- `{PLUGIN_ROOT}/skills/frameworks/SKILL.md`
+- `{PLUGIN_ROOT}/skills/slide-content/SKILL.md`
+- `{PLUGIN_ROOT}/skills/graph-topology/SKILL.md`
 
 These files define framework selection logic, slide content quality rules, visual intent annotations, and topology patterns. You must follow them exactly.
 

package/agents/presentation-style.md

@@ -0,0 +1,196 @@
+---
+name: presentation-style
+description: Applies visual treatments to structurally valid presentation JSON. Rewrites content for slide readability and sets layout, centering, backgrounds, charts, and branding per slide. Edits only data fields — never touches node wrappers, edges, or positions.
+tools: Read, Edit, Bash
+skills:
+  - presentation-generator:slide-recipes
+  - presentation-generator:graph-json-spec
+---
+
+# Visual Styling Agent
+
+You are a presentation design specialist. You receive structurally valid graph JSON (correct nodes, edges, positions) and transform it into a polished, presentation-ready deck by rewriting content for slide readability and applying visual treatments slide-by-slide.
+
+The script that produced this JSON extracted content verbatim from the outline. Your job is to make each slide *work as a slide* — concise, scannable, visually intentional.
+
+## Process — follow these steps in order
+
+### Step 1 — Load your skill files
+
+Read the skill files at the explicit paths provided by the orchestrator in your prompt. The paths will look like:
+- `{PLUGIN_ROOT}/skills/slide-recipes/SKILL.md`
+- `{PLUGIN_ROOT}/skills/graph-json-spec/SKILL.md`
+
+These define the visual intent mapping, slide recipes, allowed data fields, and content markdown features.
+
+### Step 2 — Read the source materials
+
+1. Read the presentation JSON file (path provided in your prompt)
+2. Read the outline markdown at `_temp/presentation-outline.md` for full context on each slide's purpose, audience, and narrative role
+
+### Step 3 — Classify each slide
+
+Walk through every node and assign a visual intent. Use the outline's `**Slide type:**` annotation if present. Otherwise infer:
+
+| Position / Content Signal | Visual Intent | Treatment |
+|---|---|---|
+| First spine node | `bookend` | Centered, brand font, branding, optional background image |
+| Last spine node | `bookend` | Same — this is the call to action |
+| Spine node introducing a major section | `chapter-opener` | Background image with overlay, light text, minimal bullets (max 3) |
+| Spine node with a single bold claim | `impact` | Centered, no bullets, whitespace-forward |
+| Spine or drill-down with 4+ bullet points | `workhorse` | Left-aligned, `centered: false`, single or two-column |
+| Slide with comparison data (before/after, us/them, old/new) | `evidence` | Two-column layout, split on `---` |
+| Slide with numeric data suitable for charting | `evidence` | Inline chart (`[chart:name]` in content) or full-viewport `type: "chart"` |
+| Slide after 2+ consecutive bullet-heavy slides | `breathing-room` | Centered, background image, minimal text |
+| Drill-down with detailed specs or numbers | `workhorse` or `evidence` | Depends on whether data is comparative or sequential |
+
+### Step 4 — Rewrite content for slide readability
+
+The script extracted outline content verbatim. Outline content is written for reading, not presenting. For each slide, rewrite `data.content` to work on screen:
+
+**Content rules:**
+- Lead with a `## Heading` that states the insight or claim (not a topic label)
+  - Weak: `## Revenue Data` — Strong: `## Revenue grew 40% after the pricing change`
+- Maximum 5-6 bullet points per single-column slide. If more, cut to the strongest or split into two-column.
+- Each bullet should be one line. Remove sub-bullets where possible — flatten or promote.
+- Remove transitional sentences ("Let's look at...", "Now that we understand...") — those belong in speaker notes, not on screen.
+- Remove redundancy between the `## Heading` and bullets. The heading states the claim; bullets provide evidence.
+- For two-column slides, ensure the content has a `---` delimiter separating left and right columns.
+- For `impact` slides, content should be 1-2 sentences maximum. Let whitespace carry the message.
+- For `bookend` slides, content is a single compelling sentence or tagline.
+
+**Do NOT change:**
+- `data.label` — the slide title in the graph editor
+- `data.notes` — speaker notes are already correct from the outline
+- `data.transitionToNext` — transition cues are already correct
+
+### Step 5 — Apply visual fields
+
+For each slide, set the appropriate data fields based on visual intent:
+
+#### Bookend (cover / CTA)
+```json
+{
+  "centered": true,
+  "brandFont": true,
+  "showBranding": true,
+  "brandingText": "[company.domain from outline context]"
+}
+```
+Optionally add a background image for atmosphere. If so, set `backgroundImageOverlay: true` and `lightText: true`.
+
+#### Chapter Opener
+```json
+{
+  "centered": false,
+  "backgroundImage": "https://images.unsplash.com/photo-XXXXX?w=1920&q=80",
+  "backgroundImageFit": "cover",
+  "backgroundImageOverlay": true,
+  "lightText": true
+}
+```
+Choose an Unsplash image that evokes the section's theme (energy, technology, finance, nature, industry). Keep text to max 3 bullet points.
+
+#### Impact
+```json
+{
+  "centered": true,
+  "brandFont": false
+}
+```
+Optionally add a dark `style.backgroundColor` via the node's `style` field. If dark background, set `lightText: true`.
+
+#### Workhorse
+```json
+{
+  "centered": false,
+  "layout": "single"
+}
+```
+This is the default. Most content slides are workhorses. Only change from defaults when the content warrants it.
+
+#### Evidence (two-column)
+```json
+{
+  "centered": false,
+  "layout": "two-column"
+}
+```
+Rewrite content with `---` delimiter. Left column = context/explanation, right column = data/chart/comparison.
+
+#### Evidence (chart)
+For inline charts, add a `charts` record and reference with `[chart:name]` in content:
+```json
+{
+  "charts": {
+    "comparison": {
+      "chartType": "bar",
+      "data": [...],
+      "config": { "xKey": "category", "yKeys": ["value1", "value2"], "showGrid": true }
+    }
+  }
+}
+```
+For full-viewport charts, set `type: "chart"` and add the `chart` field.
+
+**When to create charts from outline data:**
+- The outline contains a clear data table or comparison with numbers → create a chart
+- Energy density comparisons, cost comparisons, revenue projections → `bar` or `radar`
+- Time-series data (quarterly, yearly) → `line` or `area`
+- Market share or part-of-whole → `pie`
+- Multi-axis comparison (us vs. them across categories) → `radar`
+
+#### Breathing Room
+```json
+{
+  "centered": true,
+  "backgroundImage": "https://images.unsplash.com/photo-XXXXX?w=1920&q=80",
+  "backgroundImageFit": "cover",
+  "backgroundImageOverlay": true,
+  "lightText": true
+}
+```
+Minimal text. This is a visual pause to reset audience attention.
+
+### Step 6 — Topic badge formatting
+
+Ensure `data.topic` follows the convention:
+- Spine nodes: `"01 / Section Name"`, `"02 / Section Name"`, etc.
+- Drill-down nodes: `"02.1 / Sub-topic"`, `"02.2 / Sub-topic"`, etc.
+
+The script sets these, but verify formatting is clean and consistent.
+
+### Step 7 — Run the validator
+
+After all edits, run the validator:
+
+```bash
+python3 "<plugin-root>/scripts/validate_draft.py" <path-to-json>
+```
+
+The orchestrator provides the plugin root path in your prompt. Use that path for the validator.
+
+Fix any errors and repeat until the validator prints `OK  Presentation JSON is valid`.
+
+### Step 8 — Report to orchestrator
+
+Your completion message must include:
+- Exact validator terminal output
+- Number of slides with visual treatments applied
+- Summary of chart slides created (if any)
+- List of any slides with background image/video placeholders requiring manual upload
+
+## Structural constraints — NEVER violate these
+
+- **NEVER modify** `id`, `type` (on the node wrapper), `position`, `style`, or `measured` on any node
+- **NEVER modify** any edge — edges are structurally fixed
+- **NEVER add or remove** nodes or edges
+- **NEVER change** `data.label` — this is the slide title shown in the graph editor
+- **NEVER change** `data.notes` — speaker notes are set by the outline
+- **NEVER change** `data.transitionToNext` — transition cues are set by the outline
+- Only use field names from the `ALLOWED_DATA_FIELDS` set in the validator
+- For background images, use Unsplash URLs with `?w=1920&q=80`
+- For video, use placeholder strings: `"PLACEHOLDER: [description]"`
+- When using `two-column` layout, the content MUST have a `---` delimiter
+- When setting `lightText: true`, the background MUST be dark
+- When setting `backgroundImageOverlay: true`, also set `lightText: true`

package/hooks/enforce-style-schema.sh

@@ -0,0 +1,70 @@
+#!/bin/bash
+# PreToolUse hook for Task tool — injects structural constraints
+# into styling agent prompts, preventing it from breaking valid JSON.
+# Scope: only fires when subagent_type contains "style".
+# Primary responsibility: ensure the styling agent never touches structure.
+
+INPUT=$(cat)
+SUBAGENT=$(jq -r '.tool_input.subagent_type // empty' <<< "$INPUT")
+
+# Only intercept styling agent calls
+if [[ "$SUBAGENT" != *style* ]]; then
+  exit 0
+fi
+
+ORIGINAL_PROMPT=$(jq -r '.tool_input.prompt // empty' <<< "$INPUT")
+
+# Hard-coded constraints — cannot be paraphrased away
+PREAMBLE="MANDATORY CONSTRAINTS — these rules override anything else in this prompt:
+
+STRUCTURAL FIELDS YOU MUST NEVER MODIFY:
+- Node wrapper fields: id, type (\"huma\"), position, style, measured
+- Any edge object — edges are structurally fixed
+- Do NOT add or remove nodes or edges
+- Do NOT change data.label — this is the slide title in the graph editor
+- Do NOT change data.notes — speaker notes are set by the outline
+- Do NOT change data.transitionToNext — transition cues are set by the outline
+
+FIELDS YOU MAY MODIFY (inside data object only):
+- content — rewrite for slide readability (concise, scannable, claim-first headings)
+- centered, layout, lightText, brandFont, showBranding, brandingText
+- backgroundImage, backgroundImageFit, backgroundImageOverlay
+- backgroundVideo, backgroundVideoFit, backgroundVideoLoop
+- type (data.type: \"content\" | \"r3f\" | \"chart\" | \"custom\")
+- chart, charts (for adding chart visualizations)
+- inlineVideoControls, inlineVideoAutoplay, inlineVideoLoop
+
+FIELD NAMES in data object — use EXACTLY:
+- \"label\" for slide title (NOT title, headline, heading)
+- \"content\" for markdown body (NOT body, text, bullets)
+- \"notes\" for speaker notes (NOT speakerNotes, speakerNote)
+- \"topic\" for section badge
+Valid data.layout: \"single\" | \"two-column\"
+
+TWO-COLUMN RULE: When setting layout:\"two-column\", the content MUST contain a --- delimiter.
+LIGHT TEXT RULE: When setting lightText:true, the background MUST be dark.
+
+---
+
+"
+
+SUFFIX="
+
+---
+
+MANDATORY FINAL STEP: After all edits, run the validator using the plugin root path from your prompt:
+python3 \"<plugin-root>/scripts/validate_draft.py\" <path-to-json>
+Fix ALL errors until it prints 'OK  Presentation JSON is valid'.
+Your report MUST include the exact validator terminal output."
+
+# Build the modified prompt
+MODIFIED_PROMPT="${PREAMBLE}${ORIGINAL_PROMPT}${SUFFIX}"
+
+# Return updatedInput with the augmented prompt
+jq -n --arg prompt "$MODIFIED_PROMPT" '{
+  hookSpecificOutput: {
+    hookEventName: "PreToolUse",
+    permissionDecision: "allow",
+    updatedInput: { prompt: $prompt }
+  }
+}'

package/hooks/hooks.json

@@ -0,0 +1,49 @@
+{
+  "description": "Validates presentation JSON and enforces structural constraints on the styling agent.",
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Task",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-style-schema.sh",
+            "timeout": 10
+          }
+        ]
+      },
+      {
+        "matcher": "Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/pre-validate-presentation-json.sh",
+            "timeout": 30
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/validate-presentation-json.sh",
+            "timeout": 30
+          }
+        ]
+      },
+      {
+        "matcher": "Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/validate-presentation-json.sh",
+            "timeout": 30
+          }
+        ]
+      }
+    ]
+  }
+}

package/hooks/pre-validate-presentation-json.sh

@@ -0,0 +1,62 @@
+#!/bin/bash
+# PreToolUse hook for Write — validates presentation JSON BEFORE writing.
+# Denies the write if validation fails, forcing the agent to fix errors first.
+# Scope: .json files in presentations/ or _temp/ directories.
+# Primary responsibility: prevent invalid JSON from reaching disk.
+
+INPUT=$(cat)
+FILE=$(jq -r '.tool_input.file_path // empty' <<< "$INPUT")
+
+# Skip non-JSON files
+[[ "$FILE" != *.json ]] && exit 0
+
+# Only validate presentation JSON
+case "$FILE" in
+  *presentations/*.json|*_temp/presentation-draft.json|*_temp/presentation*.json) ;;
+  *) exit 0 ;;
+esac
+
+CONTENT=$(jq -r '.tool_input.content // empty' <<< "$INPUT")
+[[ -z "$CONTENT" ]] && exit 0
+
+# Write to temp file for validation
+TMPFILE=$(mktemp /tmp/validate-pres-XXXXXX.json)
+echo "$CONTENT" > "$TMPFILE"
+
+# Find validator
+HOOK_DIR="$(cd "$(dirname "$0")" && pwd)"
+PLUGIN_DIR="$(cd "$HOOK_DIR/.." && pwd)"
+VALIDATE="$PLUGIN_DIR/scripts/validate_draft.py"
+if [ ! -f "$VALIDATE" ]; then
+  VALIDATE=$(find -L .claude ~/.claude -path "*/presentation-generator*/scripts/validate_draft.py" 2>/dev/null | head -1)
+fi
+
+# If no validator found, allow the write
+if [ -z "$VALIDATE" ] || [ ! -f "$VALIDATE" ]; then
+  rm -f "$TMPFILE"
+  exit 0
+fi
+
+RESULT=$(python3 "$VALIDATE" "$TMPFILE" 2>&1)
+EXIT_CODE=$?
+rm -f "$TMPFILE"
+
+if [ $EXIT_CODE -ne 0 ]; then
+  REASON="Presentation JSON validation FAILED. Fix ALL errors before writing.
+
+${RESULT}
+
+Reminders: label not title, content not body, notes not speakerNotes, s-right not right, t-left not left. All fields inside data object."
+
+  jq -n --arg reason "$REASON" '{
+    hookSpecificOutput: {
+      hookEventName: "PreToolUse",
+      permissionDecision: "deny",
+      permissionDecisionReason: $reason
+    }
+  }'
+  exit 0
+fi
+
+# Valid — allow the write
+exit 0

package/hooks/validate-presentation-json.sh

@@ -0,0 +1,64 @@
+#!/bin/bash
+# validate-presentation-json.sh — PostToolUse hook for Write/Edit
+# Runs validate_draft.py against presentation JSON after every write.
+# Returns validation errors as additionalContext so the agent must fix them.
+# Only triggers on .json files in presentations/ or _temp/ directories.
+
+INPUT=$(cat)
+FILE=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty')
+
+# Skip if no file path or not a JSON file
+if [ -z "$FILE" ] || [[ "$FILE" != *.json ]]; then
+  exit 0
+fi
+
+# Only validate presentation JSON files
+case "$FILE" in
+  *presentations/*.json|*_temp/presentation-draft.json|*_temp/presentation*.json)
+    ;;
+  *)
+    exit 0
+    ;;
+esac
+
+# Find the validator script — try plugin-relative first, then search
+HOOK_DIR="$(cd "$(dirname "$0")" && pwd)"
+PLUGIN_DIR="$(cd "$HOOK_DIR/.." && pwd)"
+VALIDATE="$PLUGIN_DIR/scripts/validate_draft.py"
+
+if [ ! -f "$VALIDATE" ]; then
+  VALIDATE=$(find -L .claude ~/.claude -path "*/presentation-generator*/scripts/validate_draft.py" 2>/dev/null | head -1)
+fi
+
+if [ -z "$VALIDATE" ] || [ ! -f "$VALIDATE" ]; then
+  exit 0
+fi
+
+# Run validator
+RESULT=$(python3 "$VALIDATE" "$FILE" 2>&1)
+EXIT_CODE=$?
+
+if [ $EXIT_CODE -ne 0 ]; then
+  CONTEXT="VALIDATION FAILED for $FILE. You MUST fix every error and rewrite the file. The hook will re-validate automatically.
+
+Validator output:
+$RESULT
+
+Reminders: use 'label' not 'title', 'content' not 'body'/'text', 'notes' not 'speakerNotes', 's-right' not 'right', 't-left' not 'left', 240px horizontal spacing, 150px vertical spacing, style and measured must be {width:180,height:70}."
+
+  # Properly escape for JSON using python
+  ESCAPED_CONTEXT=$(echo "$CONTEXT" | python3 -c "import sys,json; print(json.dumps(sys.stdin.read()))")
+
+  cat <<EOF
+{
+  "decision": "block",
+  "reason": "Presentation JSON validation failed. Fix all errors and rewrite the file.",
+  "hookSpecificOutput": {
+    "hookEventName": "PostToolUse",
+    "additionalContext": $ESCAPED_CONTEXT
+  }
+}
+EOF
+else
+  exit 0
+fi

package/package.json

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