deck-builderlisted

Build or restructure polished, on-brand decks — as a self-contained HTML deck (1920×1080 fixed stage, PDF export) or as a PowerPoint .pptx. Use when creating, redesigning, de-cluttering, or fixing the layout of a deck/pitch/plaquette/presentation/slides — especially slides that feel empty, repetitive, or inconsistent, or when Léo asks for a vignette, a stat card, a slide element already seen in a reference. Léo names the output medium (« en HTML », « en pptx »); this skill never guesses it. Carries the layout doctrine shared by both media (fill the space, cross-card alignment, colour encodes category, type floor, one fact one home, assertion titles), a 34-model HTML design-system library, a measured geometry gate (overlap / overflow / dead space / balance / legibility), and a bridge to the visual-lab pattern library (~/visual-lab) — which also SOURCES free licensed photography (Pexels with the vault key, The Met without any key), downloaded and filtered by palette so a deck's images share one casting. Use it
lbachelotcapitalb/leo-bachelot-ia-skills · ★ 3 · Web & Frontend · score 76

Install: claude install-skill lbachelotcapitalb/leo-bachelot-ia-skills

# deck-builder One skill, two output media. The **doctrine below is medium-agnostic** — it governs what a good slide is, and it applies whether the slide ends up in a browser or in PowerPoint. The medium-specific kit lives in a backend reference, loaded only once the medium is known. ## Routing — Léo names the medium, never guess it | Léo says | Backend | Read | |---|---|---| | « en HTML », « slides web », « une page », « un deck à partager par lien » | HTML | `references/backend-html.md` | | « en pptx », « PowerPoint », « il faut que le client puisse éditer » | pptx | `references/backend-pptx.md` | | nothing explicit | **ask, one question** | — | Never infer the medium from the subject. A pitch deck is not more "HTML" than "pptx" — the answer depends on who receives it and what they do with it, and that is Léo's call. Two decks on the same subject in the two media is a legitimate ask, not a contradiction. For the "quick deck, mostly images, nobody will read it twice" case, the **Gamma** connector is already wired and is the right tool — HTML is for bespoke work. The two coexist; say which one you are taking and why in one line. ## Chronologie de production (Léo, verbatim) — applies to BOTH backends > 1. audit du besoin > 2. réflexion / sourcing d'idées dans la base > 3. rédaction du plan de production > 4. soumission d'une première maquette pour proposition > 5. validation ou itération avec l'humain (Léo) > 6. production This is the skeleton of every job. Concretely: