landing-to-powerpoint

name	landing-to-powerpoint
description	Turn a landing page URL, local HTML file, or captured landing page into a polished PowerPoint deck of at most 8 slides, with a matching downloadable PDF and an integrated-browser preview. Use when the user asks to explain what a landing page, SaaS, app, product, or website does through a short presentation, pitch deck, executive summary deck, or PDF.

Landing To PowerPoint

Goal

Create a beautiful, concise presentation that explains a landing page in at most 8 slides. Always produce:

• .pptx source deck
• .pdf export when local tooling supports it
• browser-openable preview, preferably the PDF or a simple HTML handoff page linking both files

Workflow

1. Collect page evidence

   • If the user provides a URL, open it with the in-app Browser when available.
   • Capture at least one desktop screenshot. Capture mobile too when responsive positioning or product clarity matters.
   • Extract the page title, headline, subheadline, CTA, product claims, feature sections, pricing/trust signals, and visible brand style.
   • If the URL is inaccessible, ask for a screenshot or pasted page copy.

2. Synthesize the story

   • Identify what the product/site is, who it is for, what problem it solves, how it works, and why someone should care.
   • Keep claims grounded in visible page evidence. If something is inferred, phrase it as an inference.
   • Do not fabricate pricing, customers, metrics, integrations, or guarantees.

3. Create max 8 slides

   • Use 6-8 slides by default. Never exceed 8 unless the user explicitly overrides the max.
   • Recommended structure:
     1. Cover: product name, short explanation, landing screenshot crop.
     2. What it is: one-sentence definition and context.
     3. Problem: pain point or customer need the landing targets.
     4. Solution: how the product addresses the problem.
     5. Key features: 3-5 strongest visible capabilities.
     6. Audience and positioning: ideal users, market/category, differentiation.
     7. Conversion path: CTA, offer, pricing/trial, trust signals.
     8. Takeaway: concise summary and next action.
   • Merge or omit slides when the page is simple.

4. Design standards

   • Make the deck feel premium and specific to the landing page, not generic.
   • Reuse the landing page's actual color, typography mood, screenshots, logo/wordmark where visible, and product imagery.
   • Prefer large screenshots, strong titles, dense-but-readable bullets, and clear section labels.
   • Avoid filler icons, fake charts, invented logos, and decorative clutter.
   • Use tasteful motion only if the generation stack supports it reliably. If rich PowerPoint animations are not supported, use visual sequencing, slide transitions, or speaker-note animation suggestions instead of fragile XML hacks.

5. Generate artifacts

   • Prefer the Presentations skill/plugin for .pptx generation and rendering.
   • Export a .pdf version. If direct PDF export is unavailable, render slide images or use the local office/conversion tooling available in the workspace.
   • Create an index.html preview page beside the deck that links to the .pptx and .pdf, embeds the PDF when possible, and shows basic metadata.

6. Verify

   • Render or preview the final deck before responding.
   • Check that there are no more than 8 slides.
   • Check visual fit: no overlapping text, no illegible tiny body copy, no broken images.
   • Open the preview/PDF in the integrated Browser if the Browser plugin is available.

Output Convention

Save artifacts in a clearly named folder under the current workspace or /private/tmp, for example:

landing-deck-<slug>/

Return the absolute paths to:

• PowerPoint file
• PDF file, if successfully exported
• HTML preview file

If the integrated Browser was opened, include the preview URL. If PDF export or Browser opening failed, say exactly what failed and still provide the .pptx.