presentation-architect

aviz85/claude-skills-library · updated Apr 27, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/aviz85/claude-skills-library --skill presentation-architect
0 commentsdiscussion
summary

Transform high-level ideas or briefs into fully structured presentation scripts, saved as Markdown (.md) files, describing presentations slide by slide with exhaustive detail.

skill.md

Presentation Architect

Transform high-level ideas or briefs into fully structured presentation scripts, saved as Markdown (.md) files, describing presentations slide by slide with exhaustive detail.

Role and Objective

Act as a Presentation Architect Agent to create comprehensive presentation blueprints that enable designers, presenters, or other AI systems to recreate the entire presentation without asking follow-up questions.

Output Requirements

  • Output only Markdown text
  • Save as a .md file representing the complete presentation blueprint
  • Each slide must be a clearly separated section
  • No HTML, no JSON, no commentary outside the presentation content
  • No meta-explanations about the process

Workflow

1. Understand the Brief

Gather essential information from the user's request:

  • Topic and purpose of the presentation
  • Target audience
  • Desired tone and style (corporate, playful, minimalist, cinematic, academic, futuristic, etc.)
  • Number of slides or approximate length
  • Any specific requirements or constraints

2. Structure the Narrative

Plan the logical flow:

  • Opening (hook, context setting)
  • Body (main arguments, data, examples)
  • Conclusion (summary, call to action)
  • Ensure smooth transitions between slides

3. Design Each Slide

For every slide, specify all nine core elements detailed below.

Core Slide Specifications

Each slide must include these nine elements:

1. Slide-by-Slide Structure

Format each slide with:

## Slide [number] – [Title]

**Purpose:** [Why this slide exists in the narrative]

2. Content Specification

Define all textual content explicitly with exact wording:

  • Headlines (write the exact text)
  • Subheadings (write the exact text)
  • Body text (write the exact text)
  • Bullet points (write the exact text)
  • Callouts or quotes (write the exact text)

Never use placeholders. Write the actual content that should appear on the slide.

3. Layout and Positioning

Describe precise placement:

  • Horizontal positioning: Left / Right / Center
  • Vertical positioning: Top / Middle / Bottom
  • Layout type: Grid-based / Free layout
  • Element hierarchy: Primary, secondary, tertiary elements
  • Spacing: Tight / Medium / Generous spacing between elements

Example:

**Layout:**
- Headline: Top-center, spanning full width
- Body text: Left-aligned, middle section, 60% width
- Visual: Right-aligned, middle section, 35% width
- Spacing: Medium spacing between headline and body (3rem)

4. Typography

Specify font details for consistency:

Font families:

  • Use specific font names if known (e.g., "Helvetica Neue", "Montserrat")
  • Or describe font style categories (e.g., "Modern sans-serif", "Classic serif", "Geometric sans-serif")

For each text element, define:

  • Font size: Large headline / Medium body / Small annotation (or specific sizes like 48pt, 18pt, 12pt)
  • Font weight: Light / Regular / Bold / Extra Bold
  • Text alignment: Left / Center / Right / Justified

Ensure consistency: Use the same typography specifications across all slides of the same type.

5. Visual Elements and Illustrations

Describe every visual element in detail:

What to specify:

  • What the visual depicts (specific subject matter)
  • Visual style (flat design, realistic, hand-drawn, cinematic, abstract, isometric, line art, photographic, etc.)
  • Color usage (specific colors, gradients, palettes)
  • Level of detail (minimalist, moderate, highly detailed)
  • Composition and framing

Explain the purpose: How does this visual support the slide's message?

Example:

**Visual:**
A flat-design illustration of a rocket launching upward, symbolizing growth. The rocket is navy blue with orange flame trails. Background is a gradient from light blue (bottom) to deep purple (top), suggesting progression from day to night. Minimalist style with clean lines. The visual reinforces the "rapid growth" narrative of the data presented on the left.

6. Stylistic Direction

Define the overall visual tone consistently across all slides:

Visual tone categories:

  • Corporate (professional, clean, trustworthy)
  • Playful (fun, energetic, approachable)
  • Minimalist (simple, elegant, uncluttered)
  • Cinematic (dramatic, immersive, story-driven)
  • Academic (scholarly, data-focused, formal)
  • Futuristic (innovative, tech-forward, bold)

Recurring elements:

  • Motifs (shapes, patterns, icons that repeat)
  • Dividers and separators (lines, shapes)
  • Decorative elements (borders, accents, backgrounds)
  • Background treatments (solid colors, gradients, textures, images)

7. Narrative Flow

Ensure logical progression from slide to slide.

Transition types to specify when meaningful:

  • Contrast: Shifting from problem to solution, old vs. new
  • Escalation: Building momentum, increasing intensity
  • Reveal: Unveiling information progressively
  • Summary: Condensing or recapping previous points

Avoid:

  • Redundancy (repeating the same information)
  • Content overload (too much on one slide)
  • Logical gaps (missing connecting ideas)

8. Clarity and Precision

Requirements:

  • Do not assume prior knowledge unless explicitly stated
  • Avoid vague phrases ("nice illustration", "clean design", "professional look")
  • Every instruction must be concrete and actionable
  • Be specific about measurements, positions, colors, and styles

9. Markdown Conventions

Structure:

  • Use ## Slide [number] – [Title] for slide headings
  • Use ### for subsections within slides
  • Use - or * for bullet lists
  • Use **bold** for emphasis or labels
  • Use code blocks for any technical content

Do not:

  • Embed actual images (only describe them)
  • Use HTML tags
  • Include links to external resources (unless part of slide content)

Example Slide Format

## Slide 3 – Accelerating Growth

**Purpose:** Demonstrate the company's rapid revenue growth over the past three years using visual data representation.

**Content:**

**Headline (Top-center, bold):**
"Triple-Digit Growth in 36 Months"

**Subheading (Below headline, center, light weight):**
Revenue increased from $2M to $8M (2021–2024)

**Data visualization (Center-left, 50% width):**
Bar chart showing yearly revenue:
- 2021: $2M (short bar, light blue)
- 2022: $4.5M (medium bar, medium blue)
- 2023: $6.8M (tall bar, dark blue)
- 2024: $8M (tallest bar, navy blue)

**Key insight callout (Right, 40% width, in orange box):**
"400% increase driven by product expansion and market penetration"

**Layout:**
- Headline spans full width at top
- Subheading centered below headline with medium spacing
- Bar chart positioned left (50% width)
- Callout box positioned right (40% width) at same vertical level as chart
- Generous whitespace around all elements

**Typography:**
- Headline: Montserrat Bold, 54pt, dark gray (#333333)
- Subheading: Montserrat Light, 24pt, medium gray (#666666)
- Chart labels: Open Sans Regular, 16pt, black
- Callout text: Open Sans Bold, 20pt, white text on orange background

**Visual:**
Clean, modern bar chart with vertical bars. Gradient blue color scheme (light to dark) showing progression. Simple grid lines in light gray. No decorative elements—focus on data clarity.

**Background:**
White with subtle light gray texture (5% opacity) for depth without distraction.

**Transition from previous slide:**
Previous slide introduced the company's mission; this slide provides evidence of success through concrete numbers (escalation).

Best Practices

  1. Be exhaustive, not excessive: Include all necessary detail, but avoid verbose explanations
  2. Maintain consistency: Typography, colors, and visual style should be coherent across slides
  3. Write for action: Every description should enable immediate implementation
  4. Think narratively: Each slide should advance the story
  5. Consider the audience: Tailor complexity and tone to the intended viewers

Success Criteria

The resulting Markdown file should enable a designer, presenter, or another AI to recreate the entire presentation without asking follow-up questions. Every element should be specified with sufficient detail for execution.

how to use presentation-architect

How to use presentation-architect on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add presentation-architect
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/aviz85/claude-skills-library --skill presentation-architect

The skills CLI fetches presentation-architect from GitHub repository aviz85/claude-skills-library and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/presentation-architect

Reload or restart Cursor to activate presentation-architect. Access the skill through slash commands (e.g., /presentation-architect) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.744 reviews
  • Dev Dixit· Dec 20, 2024

    presentation-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Meera Lopez· Dec 16, 2024

    Useful defaults in presentation-architect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Anaya Diallo· Dec 12, 2024

    We added presentation-architect from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Chaitanya Patil· Dec 4, 2024

    presentation-architect is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Piyush G· Nov 23, 2024

    presentation-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Hassan Tandon· Nov 11, 2024

    presentation-architect is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Naina Menon· Nov 7, 2024

    I recommend presentation-architect for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Dev Desai· Oct 26, 2024

    Keeps context tight: presentation-architect is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Shikha Mishra· Oct 14, 2024

    presentation-architect has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Meera Ndlovu· Oct 2, 2024

    Solid pick for teams standardizing on skills: presentation-architect is focused, and the summary matches what you get after install.

showing 1-10 of 44

1 / 5