mirror of
https://github.com/JimLiu/baoyu-skills.git
synced 2026-08-07 01:13:04 +08:00
chore: release v0.7.0
- baoyu-comic: adds --aspect (3:4, 4:3, 16:9) and --lang options; multi-variant storyboard workflow - baoyu-comic/baoyu-slide-deck: adds analysis-framework and template references - Multiple skills: restructured SKILL.md, moved details to references/ Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Jim Liu 宝玉
@@ -10,31 +10,13 @@ Transform content into professional slide deck images with flexible style option
|
||||
## Usage
|
||||
|
||||
```bash
|
||||
# Auto-select style based on content
|
||||
/baoyu-slide-deck path/to/content.md
|
||||
|
||||
# Specify a style
|
||||
/baoyu-slide-deck path/to/content.md --style sketch-notes
|
||||
/baoyu-slide-deck path/to/content.md --style minimal
|
||||
|
||||
# Target specific audience
|
||||
/baoyu-slide-deck path/to/content.md --audience executives
|
||||
|
||||
# Set output language
|
||||
/baoyu-slide-deck path/to/content.md --lang zh
|
||||
|
||||
# Limit slide count
|
||||
/baoyu-slide-deck path/to/content.md --slides 10
|
||||
|
||||
# Generate outline only (skip image generation)
|
||||
/baoyu-slide-deck path/to/content.md --outline-only
|
||||
|
||||
# Direct content input
|
||||
/baoyu-slide-deck
|
||||
[paste content]
|
||||
|
||||
# Combine options
|
||||
/baoyu-slide-deck path/to/content.md --style storytelling --audience experts --slides 15
|
||||
/baoyu-slide-deck # Then paste content
|
||||
```
|
||||
|
||||
## Script Directory
|
||||
@@ -58,7 +40,7 @@ Transform content into professional slide deck images with flexible style option
|
||||
|--------|-------------|
|
||||
| `--style <name>` | Visual style (see Style Gallery) |
|
||||
| `--audience <type>` | Target audience: beginners, intermediate, experts, executives, general |
|
||||
| `--lang <code>` | Output language for prompts and slides (en, zh, ja, etc.) |
|
||||
| `--lang <code>` | Output language (en, zh, ja, etc.) |
|
||||
| `--slides <number>` | Target slide count |
|
||||
| `--outline-only` | Generate outline only, skip image generation |
|
||||
|
||||
@@ -66,33 +48,31 @@ Transform content into professional slide deck images with flexible style option
|
||||
|
||||
| Style | Description | Best For |
|
||||
|-------|-------------|----------|
|
||||
| `sketch-notes` | Hand-drawn sketch notes, warm & friendly | Educational, tutorials, knowledge sharing |
|
||||
| `blueprint` | Technical blueprint, precise & analytical | Architecture, system design, data analysis |
|
||||
| `bold-editorial` | Magazine editorial, high-impact & dynamic | Product launches, marketing, keynotes |
|
||||
| `vector-illustration` | Flat vector with black outlines, retro & cute | Creative proposals, children's content, brand showcases |
|
||||
| `minimal` | Ultra-clean, maximum whitespace | Executive briefings, keynotes, premium brands |
|
||||
| `storytelling` | Cinematic, full-bleed visuals | Narratives, case studies, emotional impact |
|
||||
| `warm` | Soft gradients, wellness aesthetic | Lifestyle, wellness, personal development |
|
||||
| `notion` (Default) | SaaS dashboard, clean data focus | Product demos, SaaS, productivity tools |
|
||||
| `corporate` | Navy/gold, professional business | Investor decks, client proposals, quarterly reports |
|
||||
| `playful` | Vibrant colors, dynamic rounded shapes | Workshops, training, creative pitches |
|
||||
|
||||
Detailed style definitions: `references/styles/<style>.md`
|
||||
| `sketch-notes` | Hand-drawn, warm & friendly | Educational, tutorials |
|
||||
| `blueprint` | Technical, precise & analytical | Architecture, system design |
|
||||
| `bold-editorial` | Magazine, high-impact & dynamic | Product launches, keynotes |
|
||||
| `vector-illustration` | Flat vector, retro & cute | Creative, children's content |
|
||||
| `minimal` | Ultra-clean, maximum whitespace | Executive briefings, premium |
|
||||
| `storytelling` | Cinematic, full-bleed visuals | Narratives, case studies |
|
||||
| `warm` | Soft gradients, wellness aesthetic | Lifestyle, personal development |
|
||||
| `notion` (Default) | SaaS dashboard, clean data focus | Product demos, productivity |
|
||||
| `corporate` | Navy/gold, professional | Investor decks, proposals |
|
||||
| `playful` | Vibrant, dynamic shapes | Workshops, training |
|
||||
|
||||
## Auto Style Selection
|
||||
|
||||
| Content Signals | Selected Style |
|
||||
|-----------------|----------------|
|
||||
| tutorial, learn, education, guide, intro, beginner | `sketch-notes` |
|
||||
| architecture, system, data, analysis, technical, engineering | `blueprint` |
|
||||
| launch, marketing, brand, keynote, impact, showcase | `bold-editorial` |
|
||||
| creative, children, kids, cute, illustration, retro | `vector-illustration` |
|
||||
| architecture, system, data, analysis, technical | `blueprint` |
|
||||
| launch, marketing, brand, keynote, impact | `bold-editorial` |
|
||||
| creative, children, kids, cute, illustration | `vector-illustration` |
|
||||
| executive, minimal, clean, simple, elegant | `minimal` |
|
||||
| story, journey, case study, narrative, emotional | `storytelling` |
|
||||
| wellness, lifestyle, personal, growth, mindfulness | `warm` |
|
||||
| saas, product, dashboard, metrics, productivity | `notion` |
|
||||
| investor, quarterly, business, corporate, proposal, client | `corporate` |
|
||||
| workshop, training, fun, playful, energetic, team | `playful` |
|
||||
| investor, quarterly, business, corporate, proposal | `corporate` |
|
||||
| workshop, training, fun, playful, energetic | `playful` |
|
||||
| Default | `notion` |
|
||||
|
||||
## Design Philosophy
|
||||
@@ -106,214 +86,82 @@ This deck is designed for **reading and sharing**, not live presentation:
|
||||
## File Management
|
||||
|
||||
### With Content Path
|
||||
|
||||
Save to `slide-deck/` subdirectory in the same folder as the content:
|
||||
|
||||
```
|
||||
content-dir/
|
||||
├── source-content.md
|
||||
└── slide-deck/
|
||||
├── outline.md
|
||||
├── prompts/
|
||||
│ ├── 01-slide-cover.md
|
||||
│ ├── 02-slide-{slug}.md
|
||||
│ └── ...
|
||||
├── 01-slide-cover.png
|
||||
├── 02-slide-{slug}.png
|
||||
├── ...
|
||||
│ └── 01-slide-cover.md, 02-slide-{slug}.md, ...
|
||||
├── 01-slide-cover.png, 02-slide-{slug}.png, ...
|
||||
├── {topic-slug}.pptx
|
||||
└── {topic-slug}.pdf
|
||||
```
|
||||
|
||||
### Without Content Path
|
||||
|
||||
Save to `slide-outputs/YYYY-MM-DD/[topic-slug]/`:
|
||||
|
||||
### Without Content Path (Pasted Content)
|
||||
```
|
||||
slide-outputs/
|
||||
└── 2026-01-17/
|
||||
└── ai-future-trends/
|
||||
├── outline.md
|
||||
├── prompts/
|
||||
│ ├── 01-slide-cover.md
|
||||
│ └── ...
|
||||
├── 01-slide-cover.png
|
||||
├── ...
|
||||
├── ai-future-trends.pptx
|
||||
└── ai-future-trends.pdf
|
||||
slide-outputs/YYYY-MM-DD/{topic-slug}/
|
||||
├── source.md
|
||||
├── outline.md
|
||||
├── prompts/
|
||||
├── *.png
|
||||
├── {topic-slug}.pptx
|
||||
└── {topic-slug}.pdf
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
### Step 1: Analyze Content & Determine Settings
|
||||
### Step 1: Analyze Content
|
||||
|
||||
1. Read source material
|
||||
2. **Style selection**:
|
||||
- If `--style` specified, use that style
|
||||
- Otherwise, scan for style signals and auto-select
|
||||
3. **Language detection**:
|
||||
- If `--lang` specified, use that language for all prompts and slide text
|
||||
- Otherwise, detect language from source material
|
||||
- If uncertain (mixed languages or unclear), ask user to confirm
|
||||
4. **Slide count**:
|
||||
- If `--slides` specified, use that count
|
||||
- Otherwise, dynamic based on content structure
|
||||
1. Save source content (if pasted, save as `source.md`)
|
||||
2. Follow `references/analysis-framework.md` for deep content analysis
|
||||
3. Determine style (use `--style` or auto-select from signals)
|
||||
4. Detect languages (source vs. user preference)
|
||||
5. Plan slide count (`--slides` or dynamic)
|
||||
|
||||
### Step 2: Generate Outline with Style Instructions
|
||||
### Step 2: Generate Outline Variants
|
||||
|
||||
Create outline with structured STYLE_INSTRUCTIONS block:
|
||||
1. Generate 3 style variant outlines based on content analysis
|
||||
2. Follow `references/outline-template.md` for structure
|
||||
3. Save as `outline-{style}.md` for each variant
|
||||
|
||||
```markdown
|
||||
# Slide Deck Outline
|
||||
### Step 3: User Confirmation
|
||||
|
||||
**Topic**: [topic description]
|
||||
**Style**: [selected style]
|
||||
**Audience**: [target audience]
|
||||
**Language**: [output language]
|
||||
**Slide Count**: N slides
|
||||
**Generated**: YYYY-MM-DD HH:mm
|
||||
**Single AskUserQuestion with all applicable options:**
|
||||
|
||||
---
|
||||
| Question | When to Ask |
|
||||
|----------|-------------|
|
||||
| Style variant | Always (3 options + custom) |
|
||||
| Language | Only if source ≠ user language |
|
||||
|
||||
<STYLE_INSTRUCTIONS>
|
||||
Design Aesthetic: [2-3 sentence description from style file]
|
||||
After selection:
|
||||
- Copy selected `outline-{style}.md` to `outline.md`
|
||||
- Regenerate in different language if requested
|
||||
- User may edit `outline.md` for fine-tuning
|
||||
|
||||
Background:
|
||||
Color: [Name] ([Hex])
|
||||
Texture: [description]
|
||||
|
||||
Typography:
|
||||
Primary Font: [detailed description for image generation]
|
||||
Secondary Font: [detailed description for image generation]
|
||||
|
||||
Color Palette:
|
||||
Primary Text: [Name] ([Hex]) - [usage]
|
||||
Background: [Name] ([Hex]) - [usage]
|
||||
Accent 1: [Name] ([Hex]) - [usage]
|
||||
Accent 2: [Name] ([Hex]) - [usage]
|
||||
|
||||
Visual Elements:
|
||||
- [element 1 with rendering guidance]
|
||||
- [element 2 with rendering guidance]
|
||||
- ...
|
||||
|
||||
Style Rules:
|
||||
Do: [guidelines from style file]
|
||||
Don't: [anti-patterns from style file]
|
||||
</STYLE_INSTRUCTIONS>
|
||||
|
||||
---
|
||||
|
||||
## Slide 1 of N
|
||||
|
||||
**Type**: Cover
|
||||
**Filename**: 01-slide-cover.png
|
||||
|
||||
// NARRATIVE GOAL
|
||||
[What this slide achieves in the story arc]
|
||||
|
||||
// KEY CONTENT
|
||||
Headline: [main title]
|
||||
Sub-headline: [supporting tagline]
|
||||
|
||||
// VISUAL
|
||||
[Detailed visual description - specific elements, composition, mood]
|
||||
|
||||
// LAYOUT
|
||||
[Composition, hierarchy, spatial arrangement]
|
||||
|
||||
---
|
||||
|
||||
## Slide 2 of N
|
||||
|
||||
**Type**: Content
|
||||
**Filename**: 02-slide-{slug}.png
|
||||
|
||||
// NARRATIVE GOAL
|
||||
[What this slide achieves in the story arc]
|
||||
|
||||
// KEY CONTENT
|
||||
Headline: [main message - narrative, not label]
|
||||
Sub-headline: [supporting context]
|
||||
Body:
|
||||
- [point 1 with specific detail]
|
||||
- [point 2 with specific detail]
|
||||
- [point 3 with specific detail]
|
||||
|
||||
// VISUAL
|
||||
[Detailed visual description]
|
||||
|
||||
// LAYOUT
|
||||
[Composition, hierarchy, spatial arrangement]
|
||||
|
||||
---
|
||||
...
|
||||
|
||||
## Slide N of N
|
||||
|
||||
**Type**: Back Cover
|
||||
**Filename**: {NN}-slide-back-cover.png
|
||||
|
||||
// NARRATIVE GOAL
|
||||
[Meaningful closing - not just "thank you"]
|
||||
|
||||
// KEY CONTENT
|
||||
Headline: [memorable closing statement or call-to-action]
|
||||
Body: [optional summary points or next steps]
|
||||
|
||||
// VISUAL
|
||||
[Visual that reinforces the core message]
|
||||
|
||||
// LAYOUT
|
||||
[Clean, impactful composition]
|
||||
```
|
||||
|
||||
### Step 3: Save Outline
|
||||
|
||||
Save outline as `outline.md` in the output directory.
|
||||
|
||||
If `--outline-only` is specified, stop here.
|
||||
If `--outline-only`, stop here.
|
||||
|
||||
### Step 4: Generate Prompts
|
||||
|
||||
Create prompt file per slide in `prompts/` directory:
|
||||
|
||||
1. Read `references/base-prompt.md`
|
||||
2. Combine with style-specific instructions from outline
|
||||
3. Add slide-specific content from outline
|
||||
4. Save as `01-slide-cover.md`, `02-slide-{slug}.md`, etc.
|
||||
2. Combine with style instructions from outline
|
||||
3. Add slide-specific content
|
||||
4. Save to `prompts/` directory
|
||||
|
||||
### Step 5: Generate Images
|
||||
|
||||
**Image Generation Skill Selection**:
|
||||
1. Check available image generation skills
|
||||
2. If multiple skills available, ask user to choose
|
||||
|
||||
**Session Management**:
|
||||
If the image generation skill supports `--sessionId`:
|
||||
1. Generate a unique session ID at the start (e.g., `slides-{topic-slug}-{timestamp}`)
|
||||
2. Use the same session ID for all slides in the series
|
||||
3. This ensures style consistency across all generated slides
|
||||
|
||||
**Generation Flow**:
|
||||
1. Call selected image generation skill with prompt file, output path, and session ID
|
||||
2. Confirm generation success
|
||||
3. Report progress: "Generated X/N"
|
||||
4. Continue to next
|
||||
1. Select available image generation skill
|
||||
2. Generate session ID: `slides-{topic-slug}-{timestamp}`
|
||||
3. Generate each slide with same session ID
|
||||
4. Report progress: "Generated X/N"
|
||||
|
||||
### Step 6: Merge to PPTX and PDF
|
||||
|
||||
After all images are generated, merge them into PowerPoint and PDF files:
|
||||
|
||||
```bash
|
||||
npx -y bun ${SKILL_DIR}/scripts/merge-to-pptx.ts <slide-deck-dir>
|
||||
npx -y bun ${SKILL_DIR}/scripts/merge-to-pdf.ts <slide-deck-dir>
|
||||
```
|
||||
|
||||
This creates:
|
||||
- `{topic-slug}.pptx` - PowerPoint with all images as full-bleed 16:9 slides and prompt content as speaker notes
|
||||
- `{topic-slug}.pdf` - PDF with all images as full-page slides
|
||||
|
||||
### Step 7: Output Summary
|
||||
|
||||
```
|
||||
@@ -321,13 +169,11 @@ Slide Deck Complete!
|
||||
|
||||
Topic: [topic]
|
||||
Style: [style name]
|
||||
Audience: [audience type]
|
||||
Location: [directory path]
|
||||
Slides: N total
|
||||
|
||||
- 01-slide-cover.png ✓ Cover
|
||||
- 02-slide-intro.png ✓ Content
|
||||
- 03-slide-main-point.png ✓ Content
|
||||
- ...
|
||||
- {NN}-slide-back-cover.png ✓ Back Cover
|
||||
|
||||
@@ -336,62 +182,28 @@ PPTX: {topic-slug}.pptx
|
||||
PDF: {topic-slug}.pdf
|
||||
```
|
||||
|
||||
## Content Rules
|
||||
## Slide Modification
|
||||
|
||||
1. **Respect reader attention** -
|
||||
2. **Data traceability** - All statistics must include source attribution
|
||||
3. **Self-contained prompts** - Every detail in the image prompt, no external references
|
||||
4. **No placeholders** - Every element must be fully specified
|
||||
See `references/modification-guide.md` for:
|
||||
- Edit single slide workflow
|
||||
- Add new slide (with renumbering)
|
||||
- Delete slide (with renumbering)
|
||||
- File naming conventions
|
||||
|
||||
## Style Rules
|
||||
## References
|
||||
|
||||
1. **Narrative headlines** - Headlines tell the story, not label the content
|
||||
- Bad: "Key Statistics"
|
||||
- Good: "Usage doubled in 6 months"
|
||||
|
||||
2. **Avoid AI clichés** - No "dive into", "explore", "journey", "let's"
|
||||
|
||||
3. **Meaningful back cover** - Not just "Thank you"
|
||||
- Include call-to-action, key takeaway, or memorable closing
|
||||
|
||||
4. **Consistent visual language** - Same icons, colors, layouts throughout
|
||||
|
||||
## Slide Structure
|
||||
|
||||
1. **Cover (Slide 1)**: Title, visual hook, topic introduction
|
||||
2. **Content (Middle)**: Key points, data, explanations - dynamic count based on content
|
||||
3. **Back Cover (Final)**: Summary, call-to-action, or memorable closing
|
||||
|
||||
## Key Specifications
|
||||
|
||||
- **Aspect Ratio**: 16:9 (landscape)
|
||||
- **Slide Count**: Dynamic based on content
|
||||
- **Required Slides**: Cover + Back Cover minimum
|
||||
- **No slide numbers, footers, or logos**
|
||||
- **Language**: Priority order: `--lang` option → source material language → ask user if uncertain
|
||||
- **Tone**: Direct, confident language (avoid AI-sounding phrases)
|
||||
|
||||
## Style Reference Details
|
||||
|
||||
| Style | Description |
|
||||
|-------|-------------|
|
||||
| `sketch-notes` | Hand-drawn feel, soft brush strokes, warm off-white background, conceptual icons |
|
||||
| `blueprint` | Technical schematics, grid texture, precise lines, engineering blue tones |
|
||||
| `bold-editorial` | High contrast, bold typography, dark backgrounds, magazine-level impact |
|
||||
| `vector-illustration` | Flat vector, black outlines, retro colors, toy model aesthetic |
|
||||
| `minimal` | Maximum whitespace, single accent color, clean sans-serif, zen-like |
|
||||
| `storytelling` | Full-bleed imagery, cinematic compositions, emotional photography |
|
||||
| `warm` | Soft gradients, rounded shapes, wellness palette, approachable |
|
||||
| `notion` | Dashboard aesthetic, clean data viz, SaaS-inspired, productivity focus |
|
||||
| `corporate` | Navy/gold palette, structured layouts, professional iconography, business polish |
|
||||
| `playful` | Vibrant coral/teal/yellow, rounded shapes, dynamic layouts, energetic |
|
||||
|
||||
Full style specifications: `references/styles/<style>.md`
|
||||
| File | Content |
|
||||
|------|---------|
|
||||
| `references/analysis-framework.md` | Deep content analysis for presentations |
|
||||
| `references/outline-template.md` | Outline structure and STYLE_INSTRUCTIONS format |
|
||||
| `references/modification-guide.md` | Edit, add, delete slide workflows |
|
||||
| `references/content-rules.md` | Content and style guidelines |
|
||||
| `references/base-prompt.md` | Base prompt for image generation |
|
||||
| `references/styles/<style>.md` | Full style specifications |
|
||||
|
||||
## Notes
|
||||
|
||||
- Image generation typically takes 10-30 seconds per slide
|
||||
- Image generation: 10-30 seconds per slide
|
||||
- Auto-retry once on generation failure
|
||||
- Use stylized alternatives for sensitive public figures
|
||||
- Output language matches input content language (or `--lang`)
|
||||
- Maintain style consistency across all slides in deck
|
||||
- Maintain style consistency via session ID
|
||||
|
||||
@@ -0,0 +1,161 @@
|
||||
# Presentation Analysis Framework
|
||||
|
||||
Deep content analysis for effective slide deck creation.
|
||||
|
||||
## 1. Message Hierarchy
|
||||
|
||||
Identify the core message structure before designing slides.
|
||||
|
||||
### Core Message (One Sentence)
|
||||
- What is the single most important takeaway?
|
||||
- If the audience remembers only one thing, what should it be?
|
||||
- Can you state it in ≤15 words?
|
||||
|
||||
### Supporting Points (3-5 Maximum)
|
||||
- What evidence supports the core message?
|
||||
- What sub-topics must be covered?
|
||||
- Prioritize by audience relevance, not source order
|
||||
|
||||
### Call-to-Action
|
||||
- What should the audience DO after viewing?
|
||||
- Is it clear, specific, and achievable?
|
||||
- Where does it appear (slide position)?
|
||||
|
||||
## 2. Audience Decision Matrix
|
||||
|
||||
| Question | Analysis |
|
||||
|----------|----------|
|
||||
| Who is the primary audience? | [Role, expertise level, relationship to topic] |
|
||||
| What do they currently believe? | [Existing knowledge, assumptions, biases] |
|
||||
| What decision do we want them to make? | [Specific action or conclusion] |
|
||||
| What barriers exist? | [Objections, concerns, missing information] |
|
||||
| What evidence will convince them? | [Data types, credibility sources, emotional hooks] |
|
||||
|
||||
### Audience Adaptation
|
||||
|
||||
| Audience Type | Content Focus | Visual Treatment |
|
||||
|---------------|---------------|------------------|
|
||||
| Executives | Outcomes, ROI, strategic impact | High-level, clean, data highlights |
|
||||
| Technical | Architecture, implementation, specs | Detailed diagrams, code, schematics |
|
||||
| General | Benefits, stories, relatability | Visual metaphors, simple charts |
|
||||
| Investors | Market size, traction, team | Growth charts, milestones, comparisons |
|
||||
| Learners | Step-by-step, examples, practice | Progressive reveals, exercises |
|
||||
|
||||
## 3. Visual Opportunity Map
|
||||
|
||||
Identify which content benefits from visualization.
|
||||
|
||||
### Content-to-Visual Mapping
|
||||
|
||||
| Content Type | Visual Treatment | Example |
|
||||
|--------------|------------------|---------|
|
||||
| Comparisons | Side-by-side, before/after | Feature comparison table |
|
||||
| Processes | Flow diagrams, numbered steps | Workflow illustration |
|
||||
| Hierarchies | Org charts, pyramids, trees | Organizational structure |
|
||||
| Timelines | Horizontal/vertical timelines | Project milestones |
|
||||
| Statistics | Charts, highlighted numbers | Key metrics with context |
|
||||
| Concepts | Icons, metaphors, illustrations | Abstract idea visualization |
|
||||
| Relationships | Venn diagrams, networks | Ecosystem or dependencies |
|
||||
| Lists | Structured grids, icon rows | Feature bullets with icons |
|
||||
|
||||
### Visual Priority
|
||||
|
||||
Rate each piece of content:
|
||||
- **Must Visualize**: Complex data, key differentiators, memorable moments
|
||||
- **Should Visualize**: Supporting evidence, secondary points
|
||||
- **Text Only**: Simple statements, transitions, minor details
|
||||
|
||||
## 4. Presentation Flow
|
||||
|
||||
Structure for impact and retention.
|
||||
|
||||
### Opening (First 2-3 Slides)
|
||||
|
||||
| Element | Purpose |
|
||||
|---------|---------|
|
||||
| Hook | Capture attention (surprising stat, question, story) |
|
||||
| Context | Why this matters now |
|
||||
| Preview | What audience will learn/gain |
|
||||
|
||||
### Middle (Content Slides)
|
||||
|
||||
| Pattern | When to Use |
|
||||
|---------|-------------|
|
||||
| Problem → Solution | Introducing new products/ideas |
|
||||
| Situation → Complication → Resolution | Complex business cases |
|
||||
| What → Why → How | Educational content |
|
||||
| Past → Present → Future | Transformation stories |
|
||||
| Claim → Evidence → Implication | Data-driven arguments |
|
||||
|
||||
### Closing (Final 2-3 Slides)
|
||||
|
||||
| Element | Purpose |
|
||||
|---------|---------|
|
||||
| Synthesis | Tie back to core message |
|
||||
| Call-to-Action | Clear next steps |
|
||||
| Memorable Close | Resonant quote, image, or statement |
|
||||
|
||||
### Transitions
|
||||
|
||||
- Each slide should answer: "What comes next?"
|
||||
- Use narrative connectors between sections
|
||||
- Build logical progression, not topic jumps
|
||||
|
||||
## 5. Content Adaptation
|
||||
|
||||
Decide what to keep, transform, or omit.
|
||||
|
||||
### Keep (High Value)
|
||||
- Core arguments and evidence
|
||||
- Unique insights or data
|
||||
- Audience-relevant examples
|
||||
- Memorable quotes or statistics
|
||||
|
||||
### Simplify (Medium Value)
|
||||
- Technical details → Visual summaries
|
||||
- Long explanations → Bullet hierarchies
|
||||
- Multiple examples → Best 1-2 examples
|
||||
- Background context → Brief framing
|
||||
|
||||
### Visualize (Transform)
|
||||
- Data tables → Charts or highlighted numbers
|
||||
- Process descriptions → Flow diagrams
|
||||
- Comparisons in text → Side-by-side visuals
|
||||
- Abstract concepts → Concrete metaphors
|
||||
|
||||
### Omit (Low Value)
|
||||
- Tangential information
|
||||
- Redundant examples
|
||||
- Excessive caveats
|
||||
- Background the audience already knows
|
||||
|
||||
## 6. Analysis Checklist
|
||||
|
||||
Before outline creation, confirm:
|
||||
|
||||
### Message Clarity
|
||||
- [ ] Core message stated in one sentence
|
||||
- [ ] 3-5 supporting points identified
|
||||
- [ ] Call-to-action defined
|
||||
|
||||
### Audience Fit
|
||||
- [ ] Primary audience identified
|
||||
- [ ] Existing beliefs mapped
|
||||
- [ ] Desired decision clear
|
||||
- [ ] Evidence matches audience needs
|
||||
|
||||
### Visual Planning
|
||||
- [ ] Key visualizations identified
|
||||
- [ ] Chart/diagram types selected
|
||||
- [ ] Visual priority assigned
|
||||
|
||||
### Flow Design
|
||||
- [ ] Opening hook defined
|
||||
- [ ] Middle pattern selected
|
||||
- [ ] Closing approach planned
|
||||
- [ ] Transitions considered
|
||||
|
||||
### Content Decisions
|
||||
- [ ] Keep/simplify/visualize/omit applied
|
||||
- [ ] Source material fully processed
|
||||
- [ ] No important content overlooked
|
||||
@@ -0,0 +1,95 @@
|
||||
# Content & Style Rules
|
||||
|
||||
Guidelines for slide deck content quality and style consistency.
|
||||
|
||||
## Content Rules
|
||||
|
||||
### 1. Respect Reader Attention
|
||||
- Each slide should communicate ONE main idea
|
||||
- Remove redundant information
|
||||
- Prioritize clarity over comprehensiveness
|
||||
|
||||
### 2. Data Traceability
|
||||
- All statistics must include source attribution
|
||||
- Cite sources directly on slides with data
|
||||
- Use specific numbers over vague claims
|
||||
|
||||
### 3. Self-Contained Prompts
|
||||
- Every detail must be in the image prompt
|
||||
- No external references (e.g., "like slide 2")
|
||||
- Include all colors, layouts, and content explicitly
|
||||
|
||||
### 4. No Placeholders
|
||||
- Every element must be fully specified
|
||||
- No "[insert data here]" or "TBD"
|
||||
- All text content finalized before generation
|
||||
|
||||
## Style Rules
|
||||
|
||||
### 1. Narrative Headlines
|
||||
Headlines tell the story, not label the content.
|
||||
|
||||
| Bad | Good |
|
||||
|-----|------|
|
||||
| "Key Statistics" | "Usage doubled in 6 months" |
|
||||
| "Our Solution" | "One platform replaces five tools" |
|
||||
| "Benefits" | "Teams save 10 hours weekly" |
|
||||
|
||||
### 2. Avoid AI Clichés
|
||||
Remove these patterns:
|
||||
- "Dive into", "explore", "journey"
|
||||
- "Let's look at", "let me show you"
|
||||
- "Exciting", "amazing", "revolutionary"
|
||||
- "In conclusion", "to summarize"
|
||||
|
||||
### 3. Meaningful Back Cover
|
||||
Not just "Thank you" or "Questions?"
|
||||
|
||||
Include one of:
|
||||
- Clear call-to-action
|
||||
- Memorable key takeaway
|
||||
- Thought-provoking closing statement
|
||||
- Contact information with purpose
|
||||
|
||||
### 4. Consistent Visual Language
|
||||
Throughout the deck:
|
||||
- Same icon style
|
||||
- Same color usage patterns
|
||||
- Same layout grid system
|
||||
- Same typography hierarchy
|
||||
|
||||
## Slide Structure
|
||||
|
||||
| Position | Type | Purpose |
|
||||
|----------|------|---------|
|
||||
| 1 | Cover | Title, visual hook, topic introduction |
|
||||
| 2 to N-1 | Content | Key points, data, explanations |
|
||||
| N | Back Cover | Summary, call-to-action, memorable close |
|
||||
|
||||
## Key Specifications
|
||||
|
||||
| Specification | Value |
|
||||
|---------------|-------|
|
||||
| Aspect Ratio | 16:9 (landscape) |
|
||||
| Slide Count | Dynamic based on content |
|
||||
| Required Slides | Cover + Back Cover minimum |
|
||||
| Footers | None (no slide numbers, logos) |
|
||||
| Language Priority | `--lang` → source language → ask user |
|
||||
| Tone | Direct, confident (avoid AI phrases) |
|
||||
|
||||
## Style Quick Reference
|
||||
|
||||
| Style | Visual Summary |
|
||||
|-------|----------------|
|
||||
| `sketch-notes` | Hand-drawn, warm off-white, conceptual icons |
|
||||
| `blueprint` | Technical schematics, grid texture, blue tones |
|
||||
| `bold-editorial` | High contrast, dark backgrounds, magazine impact |
|
||||
| `vector-illustration` | Flat vector, black outlines, retro colors |
|
||||
| `minimal` | Maximum whitespace, single accent, zen-like |
|
||||
| `storytelling` | Full-bleed imagery, cinematic, emotional |
|
||||
| `warm` | Soft gradients, rounded shapes, wellness palette |
|
||||
| `notion` | Dashboard aesthetic, clean data viz, SaaS-inspired |
|
||||
| `corporate` | Navy/gold, structured layouts, business polish |
|
||||
| `playful` | Vibrant coral/teal/yellow, dynamic, energetic |
|
||||
|
||||
Full style specifications: `references/styles/<style>.md`
|
||||
@@ -0,0 +1,85 @@
|
||||
# Slide Modification Guide
|
||||
|
||||
Workflows for modifying individual slides after initial generation.
|
||||
|
||||
## Edit Single Slide
|
||||
|
||||
Regenerate a specific slide with modified content:
|
||||
|
||||
1. Identify slide to edit (e.g., `03-slide-key-findings.png`)
|
||||
2. Update prompt in `prompts/03-slide-key-findings.md`
|
||||
3. If content changes significantly, update slug in filename
|
||||
4. Regenerate image using same session ID
|
||||
5. Regenerate PPTX and PDF
|
||||
|
||||
## Add New Slide
|
||||
|
||||
Insert a new slide at specified position:
|
||||
|
||||
1. Specify insertion position (e.g., after slide 3)
|
||||
2. Create new prompt with appropriate slug (e.g., `04-slide-new-section.md`)
|
||||
3. Generate new slide image
|
||||
4. **Renumber files**: All subsequent slides increment NN by 1
|
||||
- `04-slide-conclusion.png` → `05-slide-conclusion.png`
|
||||
- Slugs remain unchanged
|
||||
5. Update `outline.md` with new slide entry
|
||||
6. Regenerate PPTX and PDF
|
||||
|
||||
## Delete Slide
|
||||
|
||||
Remove a slide and renumber:
|
||||
|
||||
1. Identify slide to delete (e.g., `03-slide-key-findings.png`)
|
||||
2. Remove image file and prompt file
|
||||
3. **Renumber files**: All subsequent slides decrement NN by 1
|
||||
- `04-slide-conclusion.png` → `03-slide-conclusion.png`
|
||||
- Slugs remain unchanged
|
||||
4. Update `outline.md` to remove slide entry
|
||||
5. Regenerate PPTX and PDF
|
||||
|
||||
## File Naming Convention
|
||||
|
||||
Files use meaningful slugs for better readability:
|
||||
|
||||
```
|
||||
NN-slide-[slug].png
|
||||
NN-slide-[slug].md (in prompts/)
|
||||
```
|
||||
|
||||
Examples:
|
||||
- `01-slide-cover.png`
|
||||
- `02-slide-problem-statement.png`
|
||||
- `03-slide-key-findings.png`
|
||||
- `04-slide-back-cover.png`
|
||||
|
||||
## Slug Rules
|
||||
|
||||
| Rule | Description |
|
||||
|------|-------------|
|
||||
| Format | Kebab-case (lowercase, hyphens) |
|
||||
| Source | Derived from slide title/content |
|
||||
| Uniqueness | Must be unique within the deck |
|
||||
| Updates | Change slug when content changes significantly |
|
||||
|
||||
## Renumbering Rules
|
||||
|
||||
| Scenario | Action |
|
||||
|----------|--------|
|
||||
| Add slide | Increment NN for all subsequent slides |
|
||||
| Delete slide | Decrement NN for all subsequent slides |
|
||||
| Reorder slides | Update NN to match new positions |
|
||||
| Edit slide | NN unchanged, update slug if needed |
|
||||
|
||||
**Important**: Slugs remain unchanged during renumbering. Only the NN prefix changes.
|
||||
|
||||
## Post-Modification Checklist
|
||||
|
||||
After any modification:
|
||||
|
||||
- [ ] Image file renamed/created correctly
|
||||
- [ ] Prompt file renamed/created correctly
|
||||
- [ ] Subsequent files renumbered (if add/delete)
|
||||
- [ ] `outline.md` updated to reflect changes
|
||||
- [ ] PPTX regenerated
|
||||
- [ ] PDF regenerated
|
||||
- [ ] Slide count in outline header updated
|
||||
@@ -0,0 +1,164 @@
|
||||
# Outline Template
|
||||
|
||||
Standard structure for slide deck outlines with style instructions.
|
||||
|
||||
## Outline Format
|
||||
|
||||
```markdown
|
||||
# Slide Deck Outline
|
||||
|
||||
**Topic**: [topic description]
|
||||
**Style**: [selected style]
|
||||
**Audience**: [target audience]
|
||||
**Language**: [output language]
|
||||
**Slide Count**: N slides
|
||||
**Generated**: YYYY-MM-DD HH:mm
|
||||
|
||||
---
|
||||
|
||||
<STYLE_INSTRUCTIONS>
|
||||
Design Aesthetic: [2-3 sentence description from style file]
|
||||
|
||||
Background:
|
||||
Color: [Name] ([Hex])
|
||||
Texture: [description]
|
||||
|
||||
Typography:
|
||||
Primary Font: [detailed description for image generation]
|
||||
Secondary Font: [detailed description for image generation]
|
||||
|
||||
Color Palette:
|
||||
Primary Text: [Name] ([Hex]) - [usage]
|
||||
Background: [Name] ([Hex]) - [usage]
|
||||
Accent 1: [Name] ([Hex]) - [usage]
|
||||
Accent 2: [Name] ([Hex]) - [usage]
|
||||
|
||||
Visual Elements:
|
||||
- [element 1 with rendering guidance]
|
||||
- [element 2 with rendering guidance]
|
||||
- ...
|
||||
|
||||
Style Rules:
|
||||
Do: [guidelines from style file]
|
||||
Don't: [anti-patterns from style file]
|
||||
</STYLE_INSTRUCTIONS>
|
||||
|
||||
---
|
||||
|
||||
[Slide entries follow...]
|
||||
```
|
||||
|
||||
## Cover Slide Template
|
||||
|
||||
```markdown
|
||||
## Slide 1 of N
|
||||
|
||||
**Type**: Cover
|
||||
**Filename**: 01-slide-cover.png
|
||||
|
||||
// NARRATIVE GOAL
|
||||
[What this slide achieves in the story arc]
|
||||
|
||||
// KEY CONTENT
|
||||
Headline: [main title]
|
||||
Sub-headline: [supporting tagline]
|
||||
|
||||
// VISUAL
|
||||
[Detailed visual description - specific elements, composition, mood]
|
||||
|
||||
// LAYOUT
|
||||
[Composition, hierarchy, spatial arrangement]
|
||||
```
|
||||
|
||||
## Content Slide Template
|
||||
|
||||
```markdown
|
||||
## Slide X of N
|
||||
|
||||
**Type**: Content
|
||||
**Filename**: {NN}-slide-{slug}.png
|
||||
|
||||
// NARRATIVE GOAL
|
||||
[What this slide achieves in the story arc]
|
||||
|
||||
// KEY CONTENT
|
||||
Headline: [main message - narrative, not label]
|
||||
Sub-headline: [supporting context]
|
||||
Body:
|
||||
- [point 1 with specific detail]
|
||||
- [point 2 with specific detail]
|
||||
- [point 3 with specific detail]
|
||||
|
||||
// VISUAL
|
||||
[Detailed visual description]
|
||||
|
||||
// LAYOUT
|
||||
[Composition, hierarchy, spatial arrangement]
|
||||
```
|
||||
|
||||
## Back Cover Slide Template
|
||||
|
||||
```markdown
|
||||
## Slide N of N
|
||||
|
||||
**Type**: Back Cover
|
||||
**Filename**: {NN}-slide-back-cover.png
|
||||
|
||||
// NARRATIVE GOAL
|
||||
[Meaningful closing - not just "thank you"]
|
||||
|
||||
// KEY CONTENT
|
||||
Headline: [memorable closing statement or call-to-action]
|
||||
Body: [optional summary points or next steps]
|
||||
|
||||
// VISUAL
|
||||
[Visual that reinforces the core message]
|
||||
|
||||
// LAYOUT
|
||||
[Clean, impactful composition]
|
||||
```
|
||||
|
||||
## STYLE_INSTRUCTIONS Block
|
||||
|
||||
The `<STYLE_INSTRUCTIONS>` block contains all style-specific guidance for image generation:
|
||||
|
||||
| Section | Content |
|
||||
|---------|---------|
|
||||
| Design Aesthetic | Overall visual direction from style file |
|
||||
| Background | Base color and texture details |
|
||||
| Typography | Font descriptions for Gemini (no font names, describe appearance) |
|
||||
| Color Palette | Named colors with hex codes and usage guidance |
|
||||
| Visual Elements | Specific graphic elements with rendering instructions |
|
||||
| Style Rules | Do/Don't guidelines from style file |
|
||||
|
||||
**Important**: Typography descriptions must describe the visual appearance (e.g., "rounded sans-serif", "bold geometric") since image generators cannot use font names.
|
||||
|
||||
## Section Dividers
|
||||
|
||||
Use `---` (horizontal rule) between:
|
||||
- Header metadata and STYLE_INSTRUCTIONS
|
||||
- STYLE_INSTRUCTIONS and first slide
|
||||
- Each slide entry
|
||||
|
||||
## Slide Numbering
|
||||
|
||||
- Cover is always Slide 1
|
||||
- Content slides use sequential numbers
|
||||
- Back Cover is always final slide (N)
|
||||
- Filename prefix matches slide position: `01-`, `02-`, etc.
|
||||
|
||||
## Filename Slugs
|
||||
|
||||
Generate meaningful slugs from slide content:
|
||||
|
||||
| Slide Type | Slug Pattern | Example |
|
||||
|------------|--------------|---------|
|
||||
| Cover | `cover` | `01-slide-cover.png` |
|
||||
| Content | `{topic-slug}` | `02-slide-problem-statement.png` |
|
||||
| Back Cover | `back-cover` | `10-slide-back-cover.png` |
|
||||
|
||||
Slug rules:
|
||||
- Kebab-case (lowercase, hyphens)
|
||||
- Derived from headline or main topic
|
||||
- Maximum 30 characters
|
||||
- Unique within deck
|
||||
Reference in New Issue
Block a user