hashgraph-online/awesome-codex-plugins / plugins/beefiker/superloopy/skills/superloopy-slides
superloopy-slides
VerifiedUse when the user asks to create, convert, style, animate, export, share, or deploy HTML slide decks, presentations, pitch decks, talks, or keynotes; including zero-dependency or single-file output, PowerPoint/PPT/PPTX input, PDF export, browser delivery, visual style exploration, or "loopy slides". Not for general web pages or landing pages.
viewport-base.css
View on GitHub/* ===========================================
FIXED 16:9 STAGE: MANDATORY BASE STYLES
Include this ENTIRE file in every presentation.
Slides are authored at 1920×1080 and scaled as a whole.
DUAL-MODE (embed-safe + standalone-safe):
- Standalone window: JS sizes .deck-viewport to the min-fit
scale and body flex centers it — same look as a full-window
fixed deck.
- Inside an iframe (Confluence "Advanced HTML & Iframe Embed"
macro, Notion embeds, etc.): JS adds .embed to <html> and
scales by WIDTH ONLY, so the document takes a natural 16:9
height and an auto-height host grows to fit; a same-origin
fixed-height host iframe is resized directly.
NEVER base heights on vh/% in embed mode: an auto-height iframe
computes those as ~0, the host locks in the collapsed height,
and the deck stays broken. NEVER use position:fixed for the
viewport or chrome: it does not scale inside iframes.
=========================================== */
/* 1. Page: no window-filling height requirement */
html,
body {
margin: 0;
background: var(--stage-bg, #000);
}
/* 2. Standalone: fill the window and center the 16:9 box */
body {
min-height: 100vh;
display: flex;
align-items: center;
justify-content: center;
overflow: hidden;
}
/* 3. Deck viewport: JS sets explicit px width/height (scaled 16:9).
position:relative — never position:fixed. */
.deck-viewport {
position: relative;
overflow: hidden;
background: var(--stage-bg, #000);
}
/* 4. Fixed 16:9 design canvas.
JS sets transform: scale(...) only; centering comes from body flex. */
.deck-stage {
position: absolute;
left: 0;
top: 0;
width: 1920px;
height: 1080px;
overflow: hidden;
transform-origin: 0 0;
background: var(--slide-bg, #fff);
}
/* 5. Slides stack inside the fixed stage.
Content must be laid out at 1920×1080, not reflowed per device. */
.slide {
position: absolute;
inset: 0;
width: 1920px;
height: 1080px;
overflow: hidden;
display: block;
visibility: hidden;
opacity: 0;
pointer-events: none;
background: var(--slide-bg, #fff);
}
.slide.active,
.slide.visible {
visibility: visible;
opacity: 1;
pointer-events: auto;
z-index: 1;
}
/* 6. Keep media inside authored slide bounds */
img,
video,
canvas,
svg {
max-width: 100%;
max-height: 100%;
}
/* 7. Presentation chrome (controls, counter, nav dots) lives INSIDE
.deck-stage, placed AFTER the slides in the DOM, and is authored
at 1920×1080 sizes — so it scales with the deck. Chrome kept
outside the stage does not scale in iframes and overlaps content
when the deck shrinks. */
.deck-controls {
position: absolute;
left: 0;
right: 0;
bottom: 22px;
z-index: 100;
}
/* 8. Embedded (iframe): drop every height base so the document takes
its natural 16:9 height. The stage-scaling JS adds .embed on
<html> when window.self !== window.top. */
html.embed,
html.embed body {
height: auto;
min-height: 0;
overflow: visible;
}
html.embed body {
display: block;
}
html.embed .deck-viewport {
margin: 0 auto;
}
/* 9. Print one fixed-size slide per page (neutralize JS inline sizes) */
@media print {
html,
body {
width: 1920px;
height: auto;
overflow: visible;
background: #fff;
display: block;
}
.deck-viewport {
position: static;
overflow: visible;
background: #fff;
width: auto !important;
height: auto !important;
}
.deck-stage {
position: static;
width: auto;
height: auto;
transform: none !important;
background: none;
}
.slide {
position: relative;
display: block !important;
visibility: visible !important;
opacity: 1 !important;
pointer-events: auto !important;
width: 1920px;
height: 1080px;
break-after: page;
page-break-after: always;
}
.slide:last-child {
break-after: auto;
page-break-after: auto;
}
.deck-controls {
display: none !important;
}
}
/* 10. Reduced motion */
@media (prefers-reduced-motion: reduce) {
*,
*::before,
*::after {
animation-duration: 0.01ms !important;
transition-duration: 0.2s !important;
}
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |