@ztffn/presentation-generator-plugin 1.2.0 → 1.3.1

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.2.0",
+  "version": "1.3.1",
   "author": {
     "name": "Huma"
   },

package/README.md

@@ -133,27 +133,25 @@ Pushing the tag triggers the publish workflow. Team members get the update with
 ## Plugin structure
 
 ```
-presentation-generator/
+presentation-generator-plugin/
 ├── .claude-plugin/
 │   └── plugin.json
+├── package.json
+├── bin/
+│   └── index.js
 ├── agents/
 │   ├── presentation-content.md
 │   ├── presentation-narrative.md
 │   └── presentation-design.md
-└── skills/
-    └── presentation-generator/
-        ├── SKILL.md
-        ├── narrative/
-        │   ├── content-signals.md
-        │   ├── frameworks.md
-        │   ├── slide-content.md
-        │   └── graph-topology.md
-        ├── system/
-        │   ├── node-schema.md
-        │   ├── edge-conventions.md
-        │   ├── layout-templates.md
-        │   └── positioning.md
-        └── examples/
-            ├── pitch-reference.json
-            └── presentation-guide.md
+├── skills/
+│   ├── presentation-generator/
+│   │   ├── SKILL.md                # Orchestrator skill
+│   │   └── presentation-guide.md
+│   ├── content-signals/SKILL.md    # Content extraction patterns
+│   ├── 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
 ```

package/agents/presentation-design.md

@@ -3,11 +3,7 @@ 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
 skills:
-  - presentation-generator:node-schema
-  - presentation-generator:edge-conventions
-  - presentation-generator:layout-templates
-  - presentation-generator:positioning
-  - presentation-generator:pitch-reference
+  - presentation-generator:graph-json-spec
 ---
 
 # Design & JSON Generation Agent
@@ -18,11 +14,11 @@ You are a design and JSON generation specialist. Your job is to translate an app
 
 1. Read the approved outline from `_temp/presentation-outline.md`
 2. For each slide in the outline, make three categories of decision:
-   a. **Slide type and layout**: Based on content signals, select `type`, `layout`, `centered`, and related fields using the layout-templates skill
+   a. **Slide type and layout**: Based on content signals, select `type`, `layout`, `centered`, and related fields per the graph-json-spec skill
    b. **Visual treatment**: Set background media, `lightText`, branding flags, and chart configuration
-   c. **Positioning**: Place each node on the grid defined in the positioning skill
+   c. **Positioning**: Place each node on the 240px/150px grid
 3. Build all nodes with complete `data`, `style`, and `measured` objects
-4. Wire all edges with bidirectional pairs following the edge-conventions skill
+4. Wire all edges with bidirectional pairs per the edge wiring rules
 5. Run the edge validation checklist before finalizing
 6. Write the complete JSON to `_temp/presentation-draft.json`
 
@@ -39,6 +35,57 @@ When translating from the outline to `data` fields, use **exactly** these SlideN
 **DO NOT use these field names** — they are not part of the schema and will be silently ignored by the renderer:
 `headline`, `subheadline`, `bullets`, `speakerNote`, `speakerNotes`, `visualHint`, `theme`, `title`, `body`, `text`, `background`, `showLogo`, `keyMessage`, `claim`, `hook`, `description`, `summary`
 
+## Valid Enum Values
+
+- `data.type`: `"content"` (default) | `"r3f"` | `"chart"` | `"custom"`
+- `data.layout`: `"single"` (default) | `"two-column"` (splits content on `---`)
+- `data.centered`: `true` (default) | `false`
+- `data.backgroundImageFit`: `"cover"` (default) | `"contain"`
+- `data.backgroundVideoFit`: `"cover"` (default) | `"contain"`
+
+## Positioning Grid
+
+- Horizontal spacing: 240px between nodes
+- Vertical spacing: 150px between levels
+- Node size: always `{ width: 180, height: 70 }` in both `style` and `measured`
+- Spine: all at y:0, x increments by 240 (0, 240, 480, 720...)
+- Drill-down level 1: y:150, same x as parent
+- Drill-down level 2: y:300
+- Siblings at same depth: increment x by 240
+
+## Chart Config
+
+Charts use a `config` wrapper for axis and display settings:
+
+```json
+{ "chartType": "bar", "data": [...], "config": { "xKey": "quarter", "yKeys": ["revenue", "cost"], "showGrid": true, "showLegend": true } }
+```
+
+- Inline: put in `charts` record, reference with `[chart:name]` in content
+- Full-viewport: put in `chart` field, set `type: "chart"`
+- Chart types: `"bar"` | `"line"` | `"area"` | `"pie"` | `"radar"`
+
+## Reference Node
+
+A complete correct node for pattern-matching:
+
+```json
+{
+  "id": "problem",
+  "type": "huma",
+  "position": { "x": 240, "y": 0 },
+  "data": {
+    "label": "The Problem",
+    "topic": "01 / Problem",
+    "content": "## Linear tools break complex stories\n\n- Point one\n- Point two",
+    "notes": "Speaker notes here",
+    "centered": false
+  },
+  "style": { "width": 180, "height": 70 },
+  "measured": { "width": 180, "height": 70 }
+}
+```
+
 ## Edge Handle Rules
 
 **WRONG** — these handle values will break navigation:

package/package.json

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