page-builder

Name: page-builder
Availability: InStock
Author: Allen

Map storyboard pages to PageType prompts and emit SlideSpec JSON fragments.

Updated Aug 23, 2026

Search Tags:#automation #ppt #storyboard #prompt-engineering #deck-generation #slide-spec #page-type

Ready to run

npx skills add https://github.com/AllenZhou/MIRISE --skill page-builder-allenzhou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: page-builder
Source: https://github.com/AllenZhou/MIRISE/tree/main/agents/ppt-pipeline/skills/page-builder
Command: npx skills add https://github.com/AllenZhou/MIRISE --skill page-builder-allenzhou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates turning a storyboard.json into per-page SlideSpec fragments using PageType-specific prompts, saving time and ensuring consistency across pages.

Core Features & Use Cases

Translates each storyboard page (page_type) into a corresponding SlideSpec JSON using prompts/<PageType>.md templates.
Enforces anti-ai-tone rules, consistent CSS classes, and evidence tagging per page.
Use Case: A deck with 12 pages can be generated from a single storyboard input, with each page mapped to its dedicated SlideSpec.

Quick Start

Use a storyboard.json input to generate slides JSON fragments for all pages.

Frequently Asked Questions about page-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate SlideSpec JSON from a storyboard for PPT deck generation?▼

To generate SlideSpec JSON from a storyboard, map each storyboard page to a dedicated PageType prompt. This enforces strict anti-ai-tone and formatting rules, validating output against doc-type budgets and slide renderer constraints.

How do I enforce anti-ai-tone rules and consistent CSS classes across automated slide generation?▼

Enforcing anti-ai-tone rules and consistent CSS classes across automated slide generation requires applying global context rules to each PageType prompt. This ensures evidence tagging and strict formatting validation per SlideSpec JSON fragment.

What is the best way to structure prompt-engineering for 12 distinct page types in a deck?▼

The best way to structure prompt-engineering for 12 distinct page types is using dedicated PageType prompt templates. Each template maps a storyboard page to a SlideSpec JSON fragment, enforcing formatting rules and validating doc-type budgets.

Can I use a single storyboard input to generate slides JSON fragments for all pages in a deck?▼

Yes, you can use a single storyboard.json input to generate slides JSON fragments for all pages. The system loads appropriate PageType prompt templates and applies global context rules to automate the entire deck generation workflow.

Does deck generation with PageType prompts validate output against slide renderer constraints?▼

Yes, deck generation with PageType prompts validates output against slide renderer constraints. It also checks against doc-type budgets and enforces anti-ai-tone rules to ensure the SlideSpec JSON fragments meet strict formatting standards.

Why does my automated slide generation fail to maintain consistent formatting across different page types?▼

Automated slide generation fails to maintain consistent formatting without dedicated PageType prompt templates. Mapping each storyboard page to a specific PageType enforces global context rules, ensuring consistent CSS classes and evidence tagging.