frontend-slides
Skill0 starsChanged 26 days agoMITView on GitHub
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
- Reads credentials
- Installs packages
97 other projects use a version of this, 29 of them edited.
Adopted by
Most recently taken up by
- AlleninTaipei/my-claude-code-skillsedited, first seen Nov 15, 2026
- MJayConstantino/skillsedited, first seen Nov 15, 2026
- notque/vexjoy-agenttheir own version, first seen Nov 10, 2026
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- thensls/nsls-builder-toolkittheir own version, first seen Nov 8, 2026
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use everything-claude-code, everything-claude-code-conventions and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
InfopibeSkilleverything-claude-code
Also in 9 projects that use this
mryeastcodeSkilleverything-claude-code-conventions
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Also in 8 projects that use this
InfopibeSkillinvestor-materials
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
Also in 23 projects that use this
tpavanipradeepSkillnextjs-turbopack
Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
Also in 14 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 7 projects that use this
CodeWithBehnamSkilldmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
Also in 15 projects that use this
- +1 more from Infopibe
Other versions97 projects use a version of this.
Word for word · 0
None found.
Edited · 29
- zarazhangrui/frontend-slides★ 29k76% same
- OpenBMB/PilotDeck★ 5k30% same
- MoizIbnYousaf/marketing-cli★ 3343% same
- SZcalligrapher/slash-skills-subscription★ 3276% same
- wrg32786/aigent-os★ 2674% same
- yinqd3/workbuddy-skills★ 1075% same
- darker2016/WorkbuddySkillGroups4DSH★ 632% same
- dreamid27/frontend-slides★ 414% same
- wzh4464/claude-skills★ 354% same
- dqtx760/skills-manage★ 243% same
19 more not listed
Wrote their own version · 68
- affaan-m/ECC★ 246ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- notque/vexjoy-agent★ 450same name
- notque/claude-code-toolkit★ 448same name
- loulanyue/awesome-claude-notes★ 272same name
- hamzafarooq/claude-code-starter★ 145same name
- happycapy-ai/Happycapy-skills★ 137same name
- cohen-liel/hivemind★ 108same name
- tpavanipradeep/everything-claude-code★ 104same name
- mturac/everything-openai-codex★ 89same name
58 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- auditoriaSkill
- diagnosticoSkill
- humanizerSkill
- linkedinSkill
- newsletterSkill
- siteSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
62 rules. 1 is common, 46 are distinctive, and 15 are very specific to this project.
1
Common
Most of the 90 edited versions we read keep these.
46
Distinctive
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 13
Create zero-dependency, animation-rich HTML presentations that run entirely in the browser.
- Distinctive: line 34
Avoid generic AI-generated aesthetics:
- Distinctive: line 47
Every deck has a viewport wrapper that fills the browser window.
- Distinctive: line 48
Every slide is authored inside a fixed 1920×1080 stage.
- Distinctive: line 50
Do not use responsive breakpoints to rearrange slide content for phones.
- Distinctive: line 51
Use fixed internal slide measurements at the 1920×1080 design size.
- Very specific: line 53
Use clamp() only for non-slide UI outside the stage, or for small fallback previews where a full stage is impractical.
- Very specific: line 55
Never negate CSS functions directly (-clamp(), -min(), -max() are silently ignored) — use calc(-1 * clamp(...)) instead
- Distinctive: line 61
Ask the user whether this is primarily a reading deck or a speaking deck, then design around that answer:
- Distinctive: line 82
When enhancing existing presentations, fixed-stage fitting is the biggest risk:
- Distinctive: line 88
Proactively reorganize: If modifications will cause overflow, automatically split content and inform the user.
- Distinctive: line 105
Do you have content ready?
- Distinctive: line 117
If user has content, ask them to share it.
- Distinctive: line 121
If user selected "No images" → skip to Phase 2.
- Distinctive: line 123
If user provides an image folder:
- Distinctive: line 131
Logo in previews: If a usable logo was identified, embed it (base64) into each style preview in Phase 2 — the user sees their brand styled …
- Distinctive: line 145
Do not ask the user whether they want options or a preset picker.
- Distinctive: line 147
If the user already gave a vibe, use it.
- Distinctive: line 149
If the user explicitly names a preset or bold template, honor that as one option and generate the remaining preview slots around it.
- Very specific: line 151
Read STYLE_PRESETS.md for safe preset candidates.
- Distinctive: line 164
Do not force every expressive option to come from the template library.
- Distinctive: line 167
If bold template matches feel weak, use the wildcard as a custom design or fall back to another safe preset instead of forcing a template.
- Very specific: line 171
Follow the Design Aesthetics section above: no generic "AI slop", no default font/color/layout choices, no purple-gradient-on-white …
- Distinctive: line 174
Keep it feasible for a full deck.
- Distinctive: line 175
Use fixed 1920×1080 stage rules and pass the same preview authenticity checks as every other option.
- Distinctive: line 176
Never render "custom", "wildcard", "AI-generated", or design-process labels on the slide itself.
- Very specific: line 181
Treat best_for examples as soft signals, not strict industry filters.
- Distinctive: line 182
Keep the three previews genuinely different from each other.
- Very specific: line 183
After choosing bold template candidate(s), read only those candidate(s)' preview.md files from the preview_md paths in the selection index.
- Very specific: line 184
Use preview.md only for title-slide previews.
- Very specific: line 185
Do not read or copy template.html unless the selected final design.md is missing a critical implementation detail.
- Distinctive: line 189
Every style preview must look like a real first slide from the user's deck, not a diagnostic card.
- Very specific: line 190
Never render internal workflow text on a slide: no preview, generated from, preview.md, template, preset, style option, Option A/B/C, file …
- Distinctive: line 191
Never render template names or slug names on the slide itself.
- Distinctive: line 192
Never render user requirement notes as slide content, such as "sharp and provocative", "safe option", "bold option", "for internal …
- Distinctive: line 193
If the slide needs chrome, use real deck chrome only: the deck title, section title, date, author, company, page number, or a genuine …
- Distinctive: line 194
Before opening previews, inspect the visible text and revise if any internal metadata appears.
- Distinctive: line 205
If "Mix elements", ask for specifics.
- Distinctive: line 213
If images were provided, the slide outline already incorporates them from Step 1.2.
- Very specific: line 236
Write a spec.json mapping slide ids to prompts, then run: python scripts/gen_slide_image.py spec.json <out_dir> [flux-pro|nano].
- Distinctive: line 242
Low density / speaker-led: Use more slides with fewer ideas per slide.
- Distinctive: line 245
If the user's stated needs are mixed, choose the closer of the two modes instead of inventing a middle option: live audience persuasion …
- Distinctive: line 247
Never let high density become visual clutter.
- Very specific: line 249
If the user selected a bold template from bold-template-pack, read that one template's full design.md before generating.
- Very specific: line 253
Treat viewport-fluid values in design.md as design proportions to translate into 1920×1080 stage coordinates.
- Distinctive: line 254
Keep the output as a single self-contained Frontend Slides HTML file.
- Distinctive: line 255
Do not copy demo slide content or mimic the source template too literally.
- Very specific: line 256
Use template.html only as a last-resort implementation reference for the selected template.
- Very specific: line 257
After generating, verify both content overflow and panel overlap in rendered browser screenshots.
- Distinctive: line 259
If the user selected a self-generated custom wildcard, treat that preview's CSS and layout as the design recipe:
- Distinctive: line 264
Keep the output fixed-stage, single-file, and visually verified like every other deck.
- Distinctive: line 276
Use fonts from Fontshare or Google Fonts — never system fonts
- Distinctive: line 277
Add detailed comments explaining each section
- Very specific: line 278
Every section needs a clear /* === SECTION NAME === */ comment block
- Distinctive: line 284
When converting PowerPoint files:
- Distinctive: line 308
After delivery, ask the user: _"Would you like to share this presentation?
- Distinctive: line 317
If the user declines, stop here.
- Distinctive: line 328
If NOT logged in, explain: _"Vercel is a free hosting service.
- Distinctive: line 333
Wait for the user to confirm they're logged in before proceeding.
- Distinctive: line 368
If no output path is given, the PDF is saved next to the HTML file.
- Distinctive: line 373
All screenshots are combined into a single PDF
- Distinctive: line 378
If that fails too, it may be a network/firewall issue.
“Common” is measured: kept by at least 6 in 10 of the 90 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
name: deck description: Cria apresentações HTML de alto nível de design — arquivo único, zero dependências, palco fixo 16:9, animações, exportação em PDF e deploy — com descoberta visual de estilo (3 previews pra escolher olhando, não descrevendo) e ilustrações de IA opcionais via Replicate (metáforas sem texto por slide). Use sempre que quiser criar um deck, uma apresentação, slides pra palestra/aula/pitch, converter um PPTX pra web, ou melhorar uma apresentação HTML existente. Gatilhos: "cria um deck", "monta a apresentação", "slides pra [ocasião]", "converte esse PPT", "melhora essa apresentação". Sucessora oficial das antigas killer-decks e ultra-deck.
Frontend Slides (ultra:deck)
Create zero-dependency, animation-rich HTML presentations that run entirely in the browser.
Core Principles
- Zero Dependencies — Single HTML files with inline CSS/JS. No npm, no build tools.
- Show, Don't Tell — Generate visual previews, not abstract choices. People discover what they want by seeing it.
- Distinctive Design — No generic "AI slop." Every presentation must feel custom-crafted.
- Progressive Disclosure — Read lightweight style indexes first. For bold templates, use small preview cards for style previews and load the full
design.mdonly after the user picks that template. - Fixed 16:9 Stage (NON-NEGOTIABLE) — Every deck uses a 1920×1080 slide canvas scaled as a whole to the viewport. Slides must stay 16:9 on every screen, including phones. Do not reflow slide content to fit the device.
Design Aesthetics
You tend to converge toward generic, "on distribution" outputs. In frontend design, this creates what users call the "AI slop" aesthetic. Avoid this: make creative, distinctive frontends that surprise and delight.
Focus on:
- Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics.
- Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. Draw from IDE themes and cultural aesthetics for inspiration.
- Motion: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions.
- Backgrounds: Create atmosphere and depth rather than defaulting to solid colors. Layer CSS gradients, use geometric patterns, or add contextual effects that match the overall aesthetic.
Avoid generic AI-generated aesthetics:
- Overused font families (Inter, Roboto, Arial, system fonts)
- Cliched color schemes (particularly purple gradients on white backgrounds)
- Predictable layouts and component patterns
- Cookie-cutter design that lacks context-specific character
Interpret creatively and make unexpected choices that feel genuinely designed for the context. Vary between light and dark themes, different fonts, different aesthetics. You still tend to converge on common choices (Space Grotesk, for example) across generations. Avoid this: it is critical that you think outside the box!
Fixed Stage Rules
These invariants apply to EVERY slide in EVERY presentation:
- Every deck has a viewport wrapper that fills the browser window.
- Every slide is authored inside a fixed 1920×1080 stage.
- The stage scales uniformly to fit the viewport. It may letterbox/pillarbox; it must not re-layout content.
- Do not use responsive breakpoints to rearrange slide content for phones.
- Use fixed internal slide measurements at the 1920×1080 design size.
- Slide visibility must be controlled by
.active/.visibleusingvisibility,opacity, andpointer-eventsfromviewport-base.css. Do not usedisplay: none/display: blockfor slide switching; later layout classes such as.slide-content { display: flex; }can override them and make every slide visible at once. - Use
clamp()only for non-slide UI outside the stage, or for small fallback previews where a full stage is impractical. - Include
prefers-reduced-motionsupport - Never negate CSS functions directly (
-clamp(),-min(),-max()are silently ignored) — usecalc(-1 * clamp(...))instead
When generating, read viewport-base.css and include its full contents in every presentation.
Content Density Modes
Ask the user whether this is primarily a reading deck or a speaking deck, then design around that answer:
| Density mode | Best for | Design behavior |
| Low density / speaker-led | Public talks, keynote-style sharing, live explanation | One idea per slide, large type, strong visual hierarchy, generous negative space, 1-3 bullets max, more slides if needed |
| High density / reading-first | Reports, handouts, async review, detailed internal docs | More self-contained slides, structured grids/tables/annotations, 4-8 bullets or 4-6 cards when readable, tighter but still intentional spacing |
Baseline limits still apply: no scrolling, no overflow, no overlapping panels, and no text below comfortable reading size. If content exceeds the selected density mode, split it into more slides instead of shrinking until it becomes cramped.
Phase 0: Detect Mode
Determine what the user wants:
- Mode A: New Presentation — Create from scratch. Go to Phase 1.
- Mode B: PPT Conversion — Convert a .pptx file. Go to Phase 4.
- Mode C: Enhancement — Improve an existing HTML presentation. Read it, understand it, enhance. Follow Mode C modification rules below.
Mode C: Modification Rules
When enhancing existing presentations, fixed-stage fitting is the biggest risk:
- Before adding content: Count existing elements, check against density limits
- Adding images: Fit them inside the 1920×1080 slide canvas. If slide already has max content, split into two slides
- Adding text: Max 4-6 bullets per slide. Exceeds limits? Split into continuation slides
- After ANY modification, verify: the slide stage remains 16:9, no text overflows its card, no panels overlap, and screenshots look correct at 1280×720 plus one phone viewport
- Proactively reorganize: If modifications will cause overflow, automatically split content and inform the user. Don't wait to be asked
When adding images to existing slides: Move image to a new slide or reduce other content first. Never add images without checking if existing content already fills the 1920×1080 slide stage.
Phase 1: Content Discovery (New Presentations)
Ask ALL questions together so the user fills everything out at once. If the current environment provides a native structured-question UI, use it; otherwise ask in one concise message with clearly numbered choices:
Question 1 — Purpose (header: "Purpose"): What is this presentation for? Options: Pitch deck / Teaching-Tutorial / Conference talk / Internal presentation
Question 2 — Length (header: "Length"): Approximately how many slides? Options: Short 5-10 / Medium 10-20 / Long 20+
Question 3 — Content (header: "Content"): Do you have content ready? Options: All content ready / Rough notes / Topic only
Question 4 — Density (header: "Density"): How dense should the deck feel? Options:
- "Low density / speaker-led" — Big ideas, fewer words, more visual breathing room
- "High density / reading-first" — More self-contained detail for async reading
Do not ask about inline editing during Phase 1. Users should not have to choose editing behavior before seeing a draft. Inline editing is a post-draft affordance: include it by default unless the user explicitly asks for a locked/export-only file.
Remember the user's density choice. It affects slide count, typography scale, amount of text per slide, layout density, and whether to favor cinematic presenter slides or self-contained reading slides.
If user has content, ask them to share it.
Step 1.2: Image Evaluation (if images provided)
If user selected "No images" → skip to Phase 2.
If user provides an image folder:
- Scan — List all image files (.png, .jpg, .svg, .webp, etc.)
- Inspect each image — Use the agent's available image-understanding capability. If image reading is unavailable, use filenames/metadata and ask the user to clarify only when needed
- Evaluate — For each: what it shows, USABLE or NOT USABLE (with reason), what concept it represents, dominant colors
- Co-design the outline — Curated images inform slide structure alongside text. This is NOT "plan slides then add images" — design around both from the start (e.g., 3 screenshots → 3 feature slides, 1 logo → title/closing slide)
- Confirm the outline using the same structured-question mechanism when available: "Does this slide outline and image selection look right?" Options: Looks good / Adjust images / Adjust outline
Logo in previews: If a usable logo was identified, embed it (base64) into each style preview in Phase 2 — the user sees their brand styled three different ways.
Phase 2: Style Discovery
This is the "show, don't tell" phase. Most people can't articulate design preferences in words.
Step 2.0: Generate 3 Style Previews Directly
Based on purpose, audience, mood, and content density, generate 3 distinct single-slide HTML previews showing typography, colors, animation, and overall aesthetic.
Brand override — check this first. If the deck belongs to a locked brand system (see Brand Systems in STYLE_PRESETS.md — the section ships as a template for the user to register their own brand), skip this whole exploration step. Build straight in that system and go to Step 3. A brand is not a taste question, and re-opening it every deck is the exact friction this override exists to kill. Only fall back to previews if the user says the brand does not apply here.
Do not ask the user whether they want options or a preset picker. The default discovery experience is always visual comparison.
If the user already gave a vibe, use it. If they did not, infer the likely mood from the occasion, audience, content, and stakes. Keep the options diverse enough that the user can react visually instead of needing to articulate taste up front.
If the user explicitly names a preset or bold template, honor that as one option and generate the remaining preview slots around it.
Read STYLE_PRESETS.md for safe preset candidates. If bold-template-pack/selection-index.json exists, read that compact index too, but do not read any design.md files yet.
| Mood | Suggested Presets |
| Impressed/Confident | Bold Signal, Electric Studio, Dark Botanical |
| Excited/Energized | Creative Voltage, Neon Cyber, Split Pastel |
| Calm/Focused | Notebook Tabs, Paper & Ink, Swiss Modern |
| Inspired/Moved | Dark Botanical, Vintage Editorial, Pastel Geometry |
Preview mix rules:
- Generate 3 previews by default: 1 safe preset from
STYLE_PRESETS.md, at least 1 bold template frombold-template-pack/selection-index.json, and 1 wildcard. - The wildcard may be either a second bold template or a self-generated custom design. Choose whichever creates the strongest, most useful contrast for the user's occasion, audience, mood, and content.
- Do not force every expressive option to come from the template library. If the brief has a sharper, more specific design opportunity than the available templates, use the wildcard slot to design freely.
- For conservative or high-stakes decks, make the safe preset especially restrained; choose a calm, higher-formality bold template; make the wildcard either another restrained template or a custom design that feels authoritative rather than decorative.
- For expressive decks, keep the safe preset as a readable fallback; choose one strong bold template; make the wildcard adventurous, context-specific, and clearly different from both other previews.
- If bold template matches feel weak, use the wildcard as a custom design or fall back to another safe preset instead of forcing a template.
Custom wildcard design rules:
- Follow the Design Aesthetics section above: no generic "AI slop", no default font/color/layout choices, no purple-gradient-on-white clichés, no cookie-cutter dashboard/card look.
- Match the user's stated occasion, audience, mood/vibe, and content density. The custom design should feel authored for this deck, not merely "stylish."
- Make a deliberate visual thesis: distinctive typography, a committed palette, a recognizable layout system, and one strong atmospheric or graphic device.
- Keep it feasible for a full deck. The preview must imply a design system that can expand into section, content, quote, comparison, and closing slides.
- Use fixed 1920×1080 stage rules and pass the same preview authenticity checks as every other option.
- Never render "custom", "wildcard", "AI-generated", or design-process labels on the slide itself.
Bold template selection rules:
- Match user purpose and mood against
mood,tone,best_for,avoid_for,formality,density, andscheme. - Treat
best_forexamples as soft signals, not strict industry filters. - Keep the three previews genuinely different from each other.
- After choosing bold template candidate(s), read only those candidate(s)'
preview.mdfiles from thepreview_mdpaths in the selection index. - Use
preview.mdonly for title-slide previews. Do not read fulldesign.mdfiles until the user picks the final template. - Do not read or copy
template.htmlunless the selected finaldesign.mdis missing a critical implementation detail.
Preview authenticity rules (NON-NEGOTIABLE):
- Every style preview must look like a real first slide from the user's deck, not a diagnostic card.
- Never render internal workflow text on a slide: no
preview,generated from,preview.md,template,preset,style option,Option A/B/C, file names, paths, or source-doc labels. - Never render template names or slug names on the slide itself. Template/style names belong only in the message to the user.
- Never render user requirement notes as slide content, such as "sharp and provocative", "safe option", "bold option", "for internal sharing", or "audience: ...", unless the user explicitly wants that exact phrase to appear in the deck.
- If the slide needs chrome, use real deck chrome only: the deck title, section title, date, author, company, page number, or a genuine content phrase from the user's material.
- Before opening previews, inspect the visible text and revise if any internal metadata appears.
Save previews to .frontend-slides/slide-previews/ (style-a.html, style-b.html, style-c.html). Each should be self-contained and compact, showing one animated title slide.
Open each preview automatically for the user.
Step 2.1: User Picks
Ask (header: "Style"): Which style preview do you prefer? Options: Style A: [Name] / Style B: [Name] / Style C: [Name] / Mix elements
If "Mix elements", ask for specifics.
Phase 3: Generate Presentation
Generate the full presentation using content from Phase 1 (text, or text + curated images) and style from Phase 2.
If images were provided, the slide outline already incorporates them from Step 1.2. If not, CSS-generated visuals (gradients, shapes, patterns) provide visual interest — this is a fully supported first-class path.
AI-generated slide imagery (optional · Replicate)
For decks that deserve illustration, generate text-free visual metaphors per slide with scripts/gen_slide_image.py (inherited from the killer-decks method: the image exemplifies, the HTML writes — crisp text always comes from code, never baked into the image).
- Requires the
REPLICATE_API_TOKENenvironment variable (or a local.env). No token → offer the beginner setup below ONCE; if the user declines, stay on the CSS-visuals path; never block a deck on this.
Ativar o Replicate — passo a passo pra quem nunca fez isso
Instrução pra IA: se o usuário quiser ilustrações e o token não existir, guie este caminho com ele, um passo por vez, em linguagem leiga. Nunca peça que ele cole o token no chat — token é senha.
O Replicate (replicate.com) é um serviço que roda modelos de imagem por uso: você só paga o que gerar — na casa de US$ 0,04 por imagem no modelo padrão (flux-1.1-pro) e ~US$ 0,15 no nano (nano-banana-pro). Um deck com 10 ilustrações custa menos de meio dólar. Pra ativar:
- Criar a conta: entre em replicate.com e clique em Sign in — dá pra entrar com a conta do GitHub ou com e-mail. É grátis criar.
- Cadastrar o pagamento: em replicate.com/account/billing, adicione um cartão. Sem susto: não é assinatura — é pré-pago/por uso, e dá pra definir um limite mensal de gasto nessa mesma tela (sugestão: US$ 5 pra começar).
- Gerar a chave (o "token"): em replicate.com/account/api-tokens, clique em Create token, dê um nome (ex.: "decks") e copie o código que aparece (começa com
r8_). Essa chave é uma senha: quem tem ela gera imagens na sua conta. Não cole em chat, print ou grupo. - Guardar a chave onde a skill lê: na pasta do seu projeto, crie um arquivo chamado
.env(só isso, com o ponto) contendo uma única linha:
A IA pode criar o arquivo pra você — você só cola a chave dentro dele no seu editor, não no chat. (Alternativa de quem já usa terminal: exportarREPLICATE_API_TOKEN=r8_sua_chave_aquiREPLICATE_API_TOKENno perfil do shell.) Se o projeto usa git, confira que.envestá no.gitignore— chave não sobe pra repositório. - Testar antes do deck inteiro: gere UMA imagem de teste e confira se apareceu na pasta e se o painel do Replicate registrou a cobrança de centavos. Chave vazou? Revogue em api-tokens e gere outra — leva 30 segundos.
- Write a
spec.jsonmapping slide ids to prompts, then run:python scripts/gen_slide_image.py spec.json <out_dir> [flux-pro|nano]. Defaultflux-pro(~US$0.04/image) fits most decks;nanoacceptsrefsfor chained visual continuity. Tell the user the approximate cost before running. - Art direction rules: derive every prompt from the deck's chosen palette and mood (name the hex values and the vibe in the prompt); keep one repeated aesthetic signature across all prompts so the deck reads as one system; the script appends the no-text suffix automatically.
- Look at every generated image before using it (read the file) — check palette match, no accidental text, no broken anatomy. Regenerate the misses. Reference images from slides via relative paths (
assets/…), never base64 in the HTML.
Apply the user's density choice throughout the deck:
- Low density / speaker-led: Use more slides with fewer ideas per slide. Favor large headings, short phrases, visual metaphors, section beats, quote/statement slides, and presenter-friendly pacing.
- High density / reading-first: Make slides more self-contained. Use structured grids, comparison tables, annotated diagrams, captions, and concise explanatory copy. Keep hierarchy strong so it feels designed, not like a document pasted onto slides.
If the user's stated needs are mixed, choose the closer of the two modes instead of inventing a middle option: live audience persuasion defaults low-density; async circulation or detailed review defaults high-density.
Never let high density become visual clutter. If a high-density slide starts to overflow, split it or redesign it into a clearer structure.
If the user selected a bold template from bold-template-pack, read that one template's full design.md before generating. Do not read the other bold templates. Treat design.md as the design recipe:
- Preserve its fonts, palette, decorative vocabulary, spacing rhythm, and component grammar.
- Generate the final deck as a fixed 1920×1080 stage scaled uniformly to the viewport, regardless of whether the source template originally used
deck-stage.jsor viewport-fluid CSS. - Treat viewport-fluid values in
design.mdas design proportions to translate into 1920×1080 stage coordinates. Do not keep them as live viewport reflow rules in the final deck. - Keep the output as a single self-contained Frontend Slides HTML file.
- Do not copy demo slide content or mimic the source template too literally.
- Use
template.htmlonly as a last-resort implementation reference for the selected template. - After generating, verify both content overflow and panel overlap in rendered browser screenshots.
scrollHeightchecks alone are not enough because grid panels can visually cover each other.
If the user selected a self-generated custom wildcard, treat that preview's CSS and layout as the design recipe:
- Preserve its fonts, palette, decorative vocabulary, spacing rhythm, grid logic, and component grammar.
- Expand the same visual system across the full deck. Do not switch to a preset or bold template after the user has chosen the custom direction.
- Design any missing slide layouts from that system rather than importing patterns from another style.
- Keep the output fixed-stage, single-file, and visually verified like every other deck.
Before generating, read these supporting files:
- html-template.md — HTML architecture and JS features
- viewport-base.css — Mandatory CSS (include in full)
- animation-patterns.md — Animation reference for the chosen feeling
Key requirements:
- Single self-contained HTML file, all CSS/JS inline
- Include the FULL contents of viewport-base.css in the
<style>block - Use fonts from Fontshare or Google Fonts — never system fonts
- Add detailed comments explaining each section
- Every section needs a clear
/* === SECTION NAME === */comment block
Phase 4: PPT Conversion
When converting PowerPoint files:
- Extract content — Run
python scripts/extract-pptx.py <input.pptx> <output_dir>(install python-pptx if needed:pip install python-pptx) - Confirm with user — Present extracted slide titles, content summaries, and image counts
- Style selection — Proceed to Phase 2 for style discovery
- Generate HTML — Convert to chosen style, preserving all text, images (from assets/), slide order, and speaker notes (as HTML comments)
Phase 5: Delivery
- Clean up — Delete
.frontend-slides/slide-previews/if it exists - Open — Use
open [filename].htmlto launch in browser - Summarize — Tell the user:
- File location, style name, slide count
- Navigation: Arrow keys, Space, swipe/tap if enabled
- How to customize:
:rootCSS variables for colors, font link for typography,.revealclass for animations - Inline text editing is available: Hover top-left corner or press E to enter edit mode, click any text to edit, Ctrl+S to save
- Offer the natural post-draft actions: ask for revisions, edit text directly in the browser, or export/share
Phase 6: Share & Export (Optional)
After delivery, ask the user: "Would you like to share this presentation? I can deploy it to a live URL (works on any device including phones) or export it as a PDF."
Options:
- Deploy to URL — Shareable link that works on any device
- Export to PDF — Universal file for email, Slack, print
- Both
- No thanks
If the user declines, stop here. If they choose one or both, proceed below.
6A: Deploy to a Live URL (Vercel)
This deploys the presentation to Vercel — a free hosting platform. The link works on any device (phones, tablets, laptops) and stays live until the user takes it down.
If the user has never deployed before, guide them step by step:
- Check if Vercel CLI is installed — Run
npx vercel --version. If not found, install Node.js first (brew install nodeon macOS, or download from https://nodejs.org). - Check if user is logged in — Run
npx vercel whoami.- If NOT logged in, explain: "Vercel is a free hosting service. You need an account to deploy. Let me walk you through it:"
- Step 1: Ask user to go to https://vercel.com/signup in their browser
- Step 2: They can sign up with GitHub, Google, email — whatever is easiest
- Step 3: Once signed up, run
vercel loginand follow the prompts (it opens a browser window to authorize) - Step 4: Confirm login with
vercel whoami
- Wait for the user to confirm they're logged in before proceeding.
- If NOT logged in, explain: "Vercel is a free hosting service. You need an account to deploy. Let me walk you through it:"
Deploy — Run the deploy script:
bash scripts/deploy.sh <path-to-presentation>The script accepts either a folder (with index.html) or a single HTML file.
- Share the URL — Tell the user:
- The live URL (from the script output)
- That it works on any device — they can text it, Slack it, email it
- To take it down later: visit https://vercel.com/dashboard and delete the project
- The Vercel free tier is generous — they won't be charged
⚠ Deployment gotchas:
- Local images/videos must travel with the HTML. The deploy script auto-detects files referenced via
src="..."in the HTML and bundles them. But if the presentation references files via CSSbackground-imageor unusual paths, those may be missed. Before deploying, verify: open the deployed URL and check that all images load. If any are broken, the safest fix is to put the HTML and all its assets into a single folder and deploy the folder instead of a standalone HTML file. - Prefer folder deployments when the presentation has many assets. If the presentation lives in a folder with images alongside it (e.g.,
my-deck/index.html+my-deck/logo.png), deploy the folder directly:bash scripts/deploy.sh ./my-deck/. This is more reliable than deploying a single HTML file because the entire folder contents are uploaded as-is. - Filenames with spaces work but can cause issues. The script handles spaces in filenames, but Vercel URLs encode spaces as
%20. If possible, avoid spaces in image filenames. If the user's images have spaces, the script handles it — but if images still break, renaming files to use hyphens instead of spaces is the fix. - Redeploying updates the same URL. Running the deploy script again on the same presentation overwrites the previous deployment. The URL stays the same — no need to share a new link.
6B: Export to PDF
This captures each slide as a screenshot and combines them into a PDF. Perfect for email attachments, embedding in documents, or printing.
Note: Animations and interactivity are not preserved — the PDF is a static snapshot. This is normal and expected; mention it to the user so they're not surprised.
Run the export script:
bash scripts/export-pdf.sh <path-to-html> [output.pdf]If no output path is given, the PDF is saved next to the HTML file.
- What happens behind the scenes (explain briefly to the user):
- A headless browser opens the presentation at 1920×1080 (standard widescreen)
- It screenshots each slide one by one
- All screenshots are combined into a single PDF
- The script needs Playwright (a browser automation tool) — it will install automatically if missing
- If Playwright installation fails:
- The most common issue is Chromium not downloading. Run:
npx playwright install chromium - If that fails too, it may be a network/firewall issue. Ask the user to try on a different network.
- The most common issue is Chromium not downloading. Run:
- Deliver the PDF — The script auto-opens it. Tell the user:
- The file location and size
- That it works everywhere — email, Slack, Notion, Google Docs, print
- Animations are replaced by their final visual state (still looks great, just static)
⚠ PDF export gotchas:
- First run is slow. The script installs Playwright and downloads a Chromium browser (~150MB) into a temp directory. This happens once per run. Warn the user it may take 30-60 seconds the first time — subsequent exports within the same session are faster.
- Slides must use
class="slide". The export script finds slides by querying.slideelements. If the presentation uses a different class name, the script will report "0 slides found" and fail. All presentations generated by this skill use.slide, so this only matters for externally-created HTML. - Local images must be loadable via HTTP. The script starts a local server and loads the HTML through it (so Google Fonts and relative image paths work). If images use absolute filesystem paths (e.g.,
src="/Users/name/photo.png") instead of relative paths (e.g.,src="photo.png"), they won't load. Generated presentations always use relative paths, but converted or user-provided decks might not — check and fix if needed. - Local images appear in the PDF as long as they are in the same directory as (or relative to) the HTML file. The export script serves the HTML's parent directory over HTTP, so relative paths like
src="photo.png"resolve correctly — including filenames with spaces. If images still don't appear, check: (1) the image files actually exist at the referenced path, (2) the paths are relative, not absolute filesystem paths like/Users/name/photo.png. - Large presentations produce large PDFs. Each slide is captured as a full 1920×1080 PNG screenshot. An 18-slide deck can produce a ~20MB PDF. If the PDF exceeds 10MB, ask the user: "The PDF is [size]. Would you like me to compress it? It'll look slightly less sharp but the file will be much smaller." If yes, re-run the export with the
--compactflag:
This renders at 1280×720 instead of 1920×1080, typically cutting file size by 50-70% with minimal visual difference.bash scripts/export-pdf.sh <path-to-html> [output.pdf] --compact
Supporting Files
| File | Purpose | When to Read |
| STYLE_PRESETS.md | 12 curated visual presets + a template to register your own locked brand system, with colors, fonts, and signature elements | Phase 2 (style selection) |
| bold-template-pack/selection-index.json | Compact bold template metadata for candidate selection | Phase 2 (style selection) |
| bold-template-pack/templates/*/preview.md | Lightweight style cards for shortlisted bold title previews | Phase 2 after shortlisting |
| bold-template-pack/templates/*/design.md | Detailed design-system docs for the selected bold template only | Phase 3 after user selection |
| viewport-base.css | Mandatory fixed-stage CSS — copy into every presentation | Phase 3 (generation) |
| html-template.md | HTML structure, JS features, code quality standards | Phase 3 (generation) |
| animation-patterns.md | CSS/JS animation snippets and effect-to-feeling guide | Phase 3 (generation) |
| scripts/extract-pptx.py | Python script for PPT content extraction | Phase 4 (conversion) |
| scripts/deploy.sh | Deploy slides to Vercel for instant sharing | Phase 6 (sharing) |
| scripts/export-pdf.sh | Export slides to PDF | Phase 6 (sharing) |
| scripts/gen_slide_image.py | Text-free slide metaphors via Replicate (optional — needs REPLICATE_API_TOKEN) | Phase 3 (AI imagery) |
ultra:deck · v1 — agosto/2026. Sucessora oficial das skills killer-decks e ultra-deck (aposentadas): o método killer-decks — a imagem exemplifica, o código escreve — vive aqui na geração de ilustrações via Replicate. Por Gui Loureiro.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

