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.
DeepseekModel
キュレーション済みスキル
品質 優秀 · 90
v1.0.0
取得
https://deepseekmodel.com/api/download.php?id=nexu-io-open-design-plugins-official-examples-replit-deck-skill-md&format=skill
ダウンロード .skill
標準形式。system_prompt と model_config を収録し、任意の Agent で利用可能
.skill ファイルの system_prompt フィールドの実際の内容。
name replit-deck en_name Write a Feature Business Case like a Principal PM zh_name 像 Principal PM 一样写功能商业论证 description 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. en_description 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. zh_description 产品/技术管理场景：围绕 core query「pm-feature-business-case-deck」把粗糙材料整理成“像 Principal PM 一样写功能商业论证”这类可购买、可复用的专业 Deck；突出受众、决策目标、证据链、风险取舍和评审标准。 tags ["product-management","pm-feature-business-case-deck","product","roadmap","architecture","decision-deck","commercial-slide-agent","replit-deck"] triggers ["pm-feature-business-case-deck","product-management","Write a Feature Business Case like a Principal PM","像 Principal PM 一样写功能商业论证","product","roadmap","architecture","html deck","html slides"] od {"mode":"deck","preview":{"type":"html","entry":"index.html"},"design_system":{"requires":false},"inputs":[{"name":"theme","type":"enum","required":true,"default":"helix","values":"[Truncated]"},{"name":"slide_count","type":"integer","default":6,"min":3,"max":20}],"scenario":"product","example_prompt":"Create \"Write a Feature Business Case like a Principal PM\" as a Product and technical management deck in the Replit Deck visual system. Scene: pm-feature-business-case-deck. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce a commercial-grade slide plan, written slides, visual direction, speaker-ready structure, and critic pass against this rubric: can cross-functional reviewers agree on the next irreversible step."} 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) 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 rewrite it . Read references/themes.md → pick one theme that matches the user's brief. If the user already picked a theme via od.inputs.theme , use that. Read references/layouts.md → you'll copy <section> blocks from here. Read references/checklist.md → P0 must pass before emit. Step 1 — Commit to one theme Write out loud (in the TodoWrite or plan section) which theme and why. Once picked, every slide uses that theme's tokens only . No swapping mid-deck. The <body data-theme="helix"> attribute is the single source of truth. Theme Pick when helix SaaS board update, product metrics, neutral modern holm Legal memo, investor pre-read, serious / institutional vance Art portfolio, design catalog, photographer / sculptor bevel Fashion campaign, lookbook, Y2K / editorial attitude world-dark Policy report, finance analysis, premium dark world-mint Lighter companion of world-dark — ESG, wellness finance, sustainability atlas Long-form narrative, chapter deck, museum / archive aesthetic bluehouse Consumer product, real estate, lifestyle, colorful cards Step 2 — Plan slide rhythm before writing HTML Default 6 slides. Write the rhythm BEFORE any HTML, for example (helix, 6 slides): 01 cover hero + title + subtitle 02 kpi-row-6 6 metrics with ▲/▼ deltas 03 split-insight left stat + right paragraph 04 chapter-plate section divider 05 three-up three parallel columns 06 closing one bold number or CTA Show this to the user. Redirecting at this stage is cheap. Step 3 — Copy seed, bind theme Copy assets/template.html to project root as index.html . Set <body data-theme="<chosen>"> . Replace <title> . Delete the placeholder slides in the body (the seed ships with 3 demo slides). Keep the chrome (counter / progress / hint). Step 4 — Paste layouts, fill real copy For each planned slide, copy the matching <section> from references/layouts.md . Replace every [REPLACE] with specific copy — never leave placeholders, never use lorem. If a slide feels empty, pick a different layout. Tag each slide with data-screen-label="01 Cover" , "02 Metrics" , etc., in presentation order. Step 5 — Self-check Run references/checklist.md silently before emit: the P0 theme-lock gate plus the five-dimension 1–5 critique (Philosophy / Hierarchy / Execution / Specificity / Restraint). Any dimension ≤ 3 → re-do before emit. The P0 theme-lock grep is non-negotiable: grep -E 'data-theme|style="--' index.html | head If any style="--accent:..." or theme override appears on individual slides, revert. One theme per deck. Step 6 — Emit artifact <artifact identifier="deck-<slug>" type="text/html" title="<Deck title>"> <!doctype html> <html>...</html> </artifact> One sentence before the artifact. Stop after </artifact> . Hard rules One theme per deck. data-theme set on <body> — never override per-slide. Numbers are real or absent. No invented metrics. Use — or a grey block as an honest placeholder. Display face follows theme. helix/world-dark/world-mint/bluehouse use the sans Display; holm/vance/atlas use the serif Display; bevel uses the Y2K display. Do not swap. (Authoritative source: the --font-display token of each theme in assets/template.html — if this list ever disagrees with the template, the template wins.) Accent appears 1–2× per slide max. Never a gradient-spam. Never rewrite the nav script. Five iframe bugs it solves are not obvious. Keep it one HTML file. Inline all CSS. No external fonts — the system stack in each theme is deliberate. data-screen-label on every slide. No Replit logo / brand lockup. These are template styles, not a Replit-brand deck. When to pick replit-deck vs. peer skills Skill Pick when simple-deck Plain, single-theme deck bound to the project's DESIGN.md tokens. When the deck should match the host brand, not assert its own. ( designSystemRequired: true .) magazine-web-ppt Editorial "magazine × e-ink" aesthetic (WebGL fluid background, serif titles, chapter plates). When the brief asks for a keynote / launch / sharing-style deck and calls out Monocle / WIRED / Kinfolk / Domus. replit-deck The brief explicitly asks for Replit-Slides gallery aesthetic, or needs one of the 8 token-frozen visual identities (SaaS board, editorial memo, gallery catalog, Y2K campaign, policy report, museum chapter, consumer cards). No dependency on DESIGN.md . If the user just says "make me a deck" without further guidance, default to simple-deck — it respects their design system. Pick replit-deck only when the brief is explicit about the aesthetic or names a theme. Scope & provenance Eight themes = the full replit.com/slides landing-page gallery at the time of snapshot. Not a curated subset — every theme card currently published on replit.com/slides is represented here (helix, holm, vance, bevel, world-dark, world-mint, atlas, bluehouse). If Replit ships a ninth template, it is not automatically reflected in this skill. Snapshot date: 2026-04-29. All hex values were sampled from the actual replit.com/slides PNGs on that date with ImageMagick — no guessed colors, no memory substitutions. See references/themes.md → Contributing a new theme for the exact sampling procedure. Maintenance: one-time snapshot, not tracked. Replit Slides is a live product and may drift. This skill does not auto-sync. If you notice Replit has updated colors or added a theme and want it reflected here, open an issue on nexu-io/open-design titled replit-deck: re-sync to replit.com/slides (YYYY-MM-DD) and attach the updated screenshots. There is no designated owner monitoring the upstream. No Replit branding. These are gallery-style templates, not a Replit-brand deck. The checklist (P0) forbids inserting a Replit logo or wordmark. Browser / runtime support Target : modern evergreen desktop browsers (Chrome 110+ / Safari 16+ / Firefox 115+) and modern mobile Safari / Chrome. Features used : CSS scroll-snap (horizontal), color-mix() , CSS custom properties, text-wrap: balance . All ≥ 93% Baseline. Not supported : IE 11, Safari < 15, any browser without color-mix() (would need a fallback --accent-soft if you want to support older Safari; out of scope for this skill). Mobile : horizontal scroll-snap works on iOS Safari 16+ and Android Chrome. Keyboard nav is desktop-only by design. Nav script behavior : reused verbatim from design-templates/simple-deck — survives iframe embedding (the daemon preview surface), dual listener races, focus loss, and position persistence across reloads. Do not rewrite it. Verification The design template auto-registers with the daemon on filesystem scan (no manual wiring). Confirmed against a running daemon on localhost:7456 after adding this template: $ curl -s localhost:7456/api/design-templates \ | node -e "const d=JSON.parse(require('fs').readFileSync(0,'utf-8')); \ console.log(JSON.stringify(d.designTemplates.find(t=>t.id==='replit-deck'), null, 2));" { "id" : "replit-deck" , "name" : "replit-deck" , "description" : "Single-file horizontal-swipe HTML deck in the style of Replit Slides's\nlanding-page template gallery. Eight distinct themes …" , "triggers" : [ "replit deck" , "replit slides" , "replit 风格 ppt" , "replit style deck" , "helix deck" , "holm memo" , "atlas chapter" , "bluehouse" , "bevel campaign" ], "mode" : "deck" , "platform" : null, "scenario" : "product" , "previewType" : "html" , "designSystemRequired" : false , "defaultFor" : [], "upstream" : null, "featured" : null, "fidelity" : null, "speakerNotes" : null, "animations" : null, "examplePrompt" : "Single-file horizontal-swipe HTML deck in the style of Replit Slides's landing-page template gallery." , "hasBody" : true } All four example decks ( examples/example-{helix,holm,atlas,bluehouse}.html ) open directly in a browser. Keyboard nav (← / → / Space / Home / End) and horizontal scroll-snap work in Chrome 129 and Safari 18.
このスキルを起動するキーワード。クリックでコピーできます。
このスキルにはトリガーワードがありません。
ダウンロードした .skill に含まれるフィールド。
| フィールド | 説明 |
|---|---|
| format | フォーマット識別子（skill/v1） |
| skill_id | スキル固有 ID |
| name | スキル名 |
| version | バージョン |
| description | 説明 |
| category | カテゴリ（配列） |
| trigger_words | トリガーワード |
| tags | タグ |
| source | ソース |
| source_url | ソース URL（本ページ） |
| exported_at | エクスポート日時（ダウンロード毎） |
| system_prompt | システムプロンプト本文 |
| model_config | モデル設定：provider / model / temperature / max_tokens / top_p |
| examples | サンプル |
| install_guide | 各プラットフォームの導入説明（Coze / Dify / Claude / カスタム） |
