replit-deck
For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident follow-up.
Profile →npx skills add nexu-io/open-design --skill replit-deck --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Replit Deck Skill Produce a single-file horizontal-swipe HTML deck in one of eight Replit-Slides themes. Every theme is a complete visual system — do not mix tokens across themes. ## Resource map ``` replit-deck/ ├── SKILL.md ← you're reading this ├── assets/ │ └── template.html ← seed: 8 themes via [data-theme=*], proven iframe-nav script (READ FIRST) ├── references/ │ ├── themes.md ← 8 themes: when-to-pick / do / don't / primary layouts │ ├── layouts.md ← 10 paste-ready slide layouts, cross-theme │ ├── components.md ← shared primitives (eyebrow, kpi-row, image-grid, meta-bar) │ └── checklist.md ← P0/P1/P2 self-review + theme lock-in gate └── examples/ ← four reference decks across the most contrasting themes ├── example-helix.html (SaaS board update · light minimal) ├── example-holm.html (legal fintech memo · cream editorial serif) ├── example-atlas.html (quarterly history chapter · black + vermilion) └── example-bluehouse.html (real estate ROI · navy + gradient cards) ``` ## Workflow ### Step 0 — Pre-flight (mandatory reads) 1. Read `assets/template.html` end-to-end. The `[data-theme]` blocks carry the tokens; the `<script>` at the bottom solves five iframe nav bugs — **do not
- Resource map
- Workflow
- Step 0 — Pre-flight (mandatory reads)
- Step 1 — Commit to one theme
- Step 2 — Plan slide rhythm before writing HTML
- Step 3 — Copy seed, bind theme
- Step 4 — Paste layouts, fill real copy
- Step 5 — Self-check
- Step 6 — Emit artifact
- Hard rules
- When to pick replit-deck vs. peer skills
- Scope & provenance
- Browser / runtime support
- Verification
grep -E 'data-theme|style="--' index.html | head curl -s localhost:7456/api/design-templates \
What does the replit-deck skill do?
For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident follow-up.
How do I install it?
Run `npx skills add nexu-io/open-design --skill replit-deck --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.