HTML Slideshow
Create a finished browser presentation that tells one coherent story and works without a slide platform.
Job contract
- Owns: horizontal, browser-based slide decks.
- Does not own: 1080x1350 social carousels (
instagram-carousel-maker) or reusable visual identity (brand-system-builder).
- Finished deliverable: working HTML deck, source attribution, and viewing instructions.
Workflow
- Establish audience, purpose, viewing context, duration, source material, and brand constraints.
- Create the story spine before styling: opening tension, development, proof, resolution, action.
- Choose a visual direction from the source, audience, and brand constraints. Use a small set of recurring motifs rather than a generic card-deck treatment.
- Use one idea per slide and vary composition to match the job of the slide. Cut content instead of shrinking type.
- Build semantic HTML, scoped CSS, keyboard and click navigation, slide counter, and responsive scaling.
- Avoid dependencies unless the user needs them. Keep external assets credited and legally usable.
- Test first, middle, last, overflow, keyboard controls, and common viewport sizes.
- Return the actual file, not only a storyboard.
Minimum quality bar
- Clear visual hierarchy at presentation distance.
- A visual direction that reflects the source or brand rather than an interchangeable template.
- Real examples, screenshots, diagrams, or source-specific proof when the supplied material supports them.
- Keyboard navigation with left/right arrows and space.
- No clipped text or accidental scrollbars.
- Respect
prefers-reduced-motion when animation is used.
- Source or credit factual claims and third-party media.
Delivery note
Report the deck path, slide count, how to open it, what was tested, and any external asset dependency.
Guardrails
- Never invent statistics, customer quotes, logos, or endorsements.
- Do not use copyrighted imagery without permission or a usable licence.
- Do not publish or deploy the deck unless the user explicitly approves that external action.
1---2name: html-slideshow3description: Create a responsive browser-based presentation, keynote-style HTML deck, workshop deck, pitch deck, or shareable horizontal slideshow and verify navigation and layout.4---56# HTML Slideshow78Create a finished browser presentation that tells one coherent story and works without a slide platform.910## Job contract1112- Owns: horizontal, browser-based slide decks.13- Does not own: 1080x1350 social carousels (`instagram-carousel-maker`) or reusable visual identity (`brand-system-builder`).14- Finished deliverable: working HTML deck, source attribution, and viewing instructions.1516## Workflow17181. Establish audience, purpose, viewing context, duration, source material, and brand constraints.192. Create the story spine before styling: opening tension, development, proof, resolution, action.203. Choose a visual direction from the source, audience, and brand constraints. Use a small set of recurring motifs rather than a generic card-deck treatment.214. Use one idea per slide and vary composition to match the job of the slide. Cut content instead of shrinking type.225. Build semantic HTML, scoped CSS, keyboard and click navigation, slide counter, and responsive scaling.236. Avoid dependencies unless the user needs them. Keep external assets credited and legally usable.247. Test first, middle, last, overflow, keyboard controls, and common viewport sizes.258. Return the actual file, not only a storyboard.2627## Minimum quality bar2829- Clear visual hierarchy at presentation distance.30- A visual direction that reflects the source or brand rather than an interchangeable template.31- Real examples, screenshots, diagrams, or source-specific proof when the supplied material supports them.32- Keyboard navigation with left/right arrows and space.33- No clipped text or accidental scrollbars.34- Respect `prefers-reduced-motion` when animation is used.35- Source or credit factual claims and third-party media.3637## Delivery note3839Report the deck path, slide count, how to open it, what was tested, and any external asset dependency.4041## Guardrails4243- Never invent statistics, customer quotes, logos, or endorsements.44- Do not use copyrighted imagery without permission or a usable licence.45- Do not publish or deploy the deck unless the user explicitly approves that external action.
nahiddotai