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.
bold-template-pack/README.md
View on GitHub# Bold Template Pack
This pack brings the `beautiful-html-templates` design systems into the
`frontend-slides` skill without making them the default for every deck.
## What To Read
1. Read `bold-template-pack/selection-index.json` first.
2. Shortlist candidates from metadata only:
- `mood`
- `tone`
- `best_for`
- `avoid_for`
- `formality`
- `density`
- `scheme`
3. For title-slide previews, read only the relevant candidate `preview.md`
files.
4. After the user chooses a bold template, read exactly that one template's
full `design.md`.
5. Do not read every `design.md` in the pack.
6. Do not read or copy `template.html` from the source template library unless a
selected `design.md` is missing a critical implementation detail.
The full source metadata index is not bundled in the user-facing skill. Normal
generation should use `selection-index.json` only.
## How To Use In Frontend Slides
Preview mix:
- 1 safe option from `STYLE_PRESETS.md`
- at least 1 bold option from this pack
- 1 wildcard option, which may be another bold template from this pack or a
self-generated custom design
Adjust the tone inside that default mix:
- For board, legal, regulatory, healthcare, investor-update, or highly formal
internal decks, make the safe option very restrained and choose calmer,
higher-formality bold templates. The wildcard should feel authoritative and
specific, not merely decorative.
- For bold, editorial, expressive, experimental, or highly designed decks, keep
the safe option as a readable fallback, choose one strong bold template, and
use the wildcard for either a second adventurous template or a custom design
that better matches the user's occasion and vibe.
If the wildcard is custom, it must follow Frontend Slides' no-slop aesthetics:
distinctive typography, a committed palette, a recognizable layout system, a
context-specific visual idea, fixed 16:9 stage behavior, and no visible process
labels such as "custom", "wildcard", "template", or "preview".
## Implementation Contract
`design.md` is the design-system reference. Treat it as a style recipe, not as
content to copy. `preview.md` is only a lightweight style card for generating
the three title-slide options.
Preview slides must be real title slides for the user's deck. Do not render
template names, option labels, file names, paths, `preview.md`, "generated
from", or user requirement notes on the slide itself.
When generating final slides:
- Keep `frontend-slides` output as one self-contained HTML file.
- Include the full contents of `viewport-base.css`.
- Generate every deck as a fixed 1920×1080 stage scaled uniformly to the
viewport. This applies even if the source template was originally
viewport-fluid.
- Treat `vw`, `vh`, and `clamp()` values in a source `design.md` as design
proportions to translate into fixed 1920×1080 stage coordinates.
- Preserve the selected template's fonts, palette, decorative vocabulary,
spacing rhythm, and component grammar.
- Keep the user's actual slide content primary. The template style should shape
presentation, not override message or structure.
- Verify rendered output for both text overflow and panel overlap. A card can
pass `scrollHeight` checks while still being covered by another grid panel.
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: 198k | 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 |