[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DC8XBPTHWC2XSETPWHWY8N":3,"skill-same:01M7DC8XBPTHWC2XSETPWHWY8N":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":72},"01M7DC8XBPTHWC2XSETPWHWY8N","simple-deck",null,"OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Built as a decision-grade corporate strategy deck for leadership team.","feimacode\u002Fopen-design-agent-kit","feimacode","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264390570?v=4","01M7D3HQSP5EP4Z4JECTSQ7EBD","Feima Code","01M7D3HQT72Q4EVQJP89MR9WP1",1129,"MIT","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fexamples\u002Fsimple-deck\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: simple-deck\nen_name: \"Write an Operating Review like a Disciplined COO\"\nzh_name: \"像克制的 COO 一样写经营复盘\"\ndescription: |\n  OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Built as a decision-grade corporate strategy deck for leadership team.\nen_description: |\n  OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Built as a decision-grade corporate strategy deck for leadership team.\nzh_description: |\n  像克制的 COO 一样写经营复盘——一份可商业交付的企业战略 Deck，围绕真实主题、证据链与决策目标组织。\ntags:\n  - \"corporate-strategy\"\n  - \"board-pre-read-deck\"\n  - \"strategy\"\n  - \"board\"\n  - \"business-review\"\n  - \"decision-deck\"\n  - \"commercial-slide-agent\"\n  - \"simple-deck\"\ntriggers:\n  - \"board-pre-read-deck\"\n  - \"corporate-strategy\"\n  - \"Write an Operating Review like a Disciplined COO\"\n  - \"像克制的 COO 一样写经营复盘\"\n  - \"board\"\n  - \"strategy\"\n  - \"business-review\"\n  - \"html deck\"\n  - \"html slides\"\nod:\n  mode: deck\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: true\n    sections: [color, typography, layout, components]\n  category: \"corporate-strategy\"\n  scenario: \"strategy\"\n  example_prompt: \"Create \\\"Write an Operating Review like a Disciplined COO\\\" as a decision-grade Corporate strategy deck in this template's own visual system. Subject: OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Audience: leadership team. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce the slide plan, written slides, visual direction, speaker-ready structure, and a critic pass against this rubric: would a board member know what to approve and why before page five.\"\n---\n\n# Simple Deck Skill\n\nProduce a single-file horizontal-swipe HTML deck using the seed and layout library.\n\n## Resource map\n\n```\nsimple-deck\u002F\n├── SKILL.md                ← you're reading this\n├── assets\u002F\n│   └── template.html       ← seed: tokens + slide primitives + proven nav script (READ FIRST)\n└── references\u002F\n    ├── layouts.md          ← 8 paste-ready slide layouts + theme-rhythm rules\n    └── checklist.md        ← P0\u002FP1\u002FP2 self-review (rhythm spot-check at bottom)\n```\n\n## Workflow\n\n### Step 0 — Pre-flight\n\n1. **Read `assets\u002Ftemplate.html`** end-to-end through the `\u003Cstyle>` block AND the `\u003Cscript>` block. The script solves five iframe-specific bugs (real scroller detection, dual capture-phase listeners, auto-focus, no `scrollIntoView`, position persistence) — do not rewrite it.\n2. **Read `references\u002Flayouts.md`** so you know the 8 layouts. Pay special attention to the \"Theme rhythm\" section — it's the rule that prevents the deck from feeling sleepy.\n3. **Read the active DESIGN.md** — map its tokens to the six `:root` variables in the seed.\n\n### Step 1 — Copy the seed\n\nCopy `assets\u002Ftemplate.html` to the project root as `index.html`. Replace the six `:root` variables with the active design system's tokens. Replace the page `\u003Ctitle>`.\n\n### Step 2 — Decide slide count + theme rhythm BEFORE writing any slide\n\nDefault: 6 slides unless the brief says otherwise.\n\n| Audience \u002F format | Slides |\n|---|---|\n| Product overview \u002F lightning talk (5–10 min) | 6 |\n| Pitch deck (15 min) | 8–10 |\n| Investor update \u002F longer talk (20–30 min) | 12–18 |\n\nThen write out the rhythm before any HTML — for example, 8 slides:\n\n```\n01  hero light center  Cover\n02  light              Problem\n03  hero dark center   Big stat\n04  light              Three points\n05  dark               Pipeline\n06  hero light center  Quote\n07  light              Before \u002F after\n08  hero dark center   Ask\n```\n\nA healthy sequence has:\n- No 3+ same theme in a row\n- ≥ 1 `hero dark` AND ≥ 1 `hero light` (for 8+ slides)\n- Alternating breath every 3–4 slides\n\nShow this rhythm sketch to the user *before* writing slide HTML — they can redirect cheaply.\n\n### Step 3 — Paste and fill\n\nFor each planned slide, copy the matching `\u003Csection>` from `layouts.md` into the body. Replace bracketed text with real, specific copy. **No filler \u002F no lorem.** If a slide feels empty, the layout is wrong — pick a different one.\n\nTag each slide with `data-screen-label=\"01 Cover\"`, `\"02 Problem\"`, etc., in the order you wrote them. (The seed's first three slides already do this — extend the pattern.)\n\n### Step 4 — Self-check\n\nRun through `references\u002Fchecklist.md`. The \"Theme rhythm spot-check\" at the end is non-negotiable:\n\n```bash\ngrep 'class=\"slide' index.html\n```\n\nRead the resulting class list. If you see `light × 4 in a row`, swap one to `dark`. If no `hero dark` exists in an 8+ slide deck, promote one big-stat or closing slide.\n\n### Step 5 — Write the project file\n\nWrite the completed deck HTML to `index.html`.\n\nThen send one short ordinary assistant summary naming `index.html` and\ndescribing the deck. Do not output the full HTML source in chat and do not emit\na source-code `\u003Cartifact>` block.\n\n## Hard rules\n\n- **Theme class on every slide** (`light` | `dark` | `hero light` | `hero dark`). Bare `class=\"slide\"` = regression.\n- **No 3+ same theme in a row.**\n- **Display = serif via `var(--font-display)`.** `.h-hero` \u002F `.h-xl` \u002F `.h-md` already enforce.\n- **One accent per slide, used at most twice.**\n- **Don't rewrite the nav script.** It's proven.\n- **No `scrollIntoView()`.** Breaks iframe.\n- **`data-screen-label` on every slide.**\n","# Simple Deck Skill\n\nProduce a single-file horizontal-swipe HTML deck using the seed and layout library.\n\n## Resource map\n\n```\nsimple-deck\u002F\n├── SKILL.md                ← you're reading this\n├── assets\u002F\n│   └── template.html       ← seed: tokens + slide primitives + proven nav script (READ FIRST)\n└── references\u002F\n    ├── layouts.md          ← 8 paste-ready slide layouts + theme-rhythm rules\n    └── checklist.md        ← P0\u002FP1\u002FP2 self-review (rhythm spot-check at bottom)\n```\n\n## Workflow\n\n### Step 0 — Pre-flight\n\n1. **Read `assets\u002Ftemplate.html`** end-to-end through the `\u003Cstyle>` block AND the `\u003Cscript>` block. The script solves five iframe-specific bugs (real scroller detection, dual capture-phase listeners, auto-focus, no `scrollIntoView`, position persistence) — do not rewrite it.\n2. **Read `references\u002Flayouts.md`** so you know the 8 layouts. Pay special attention to the \"Theme rhythm\" section — it's the rule that prevents the deck from feeling sleepy.\n3. **Read the active DESIGN.md** — map its tokens to the six `:root` variables in the seed.\n\n### Step 1 — Copy the seed\n\nCopy `assets\u002Ftemplate.html` to the project root as `index.html`. Replace the six `:root` variables with the active design system's tokens. Replace the page `\u003Ctitle>`.\n\n### Step 2 — Decide slide count + theme rhythm BEFORE writing any slide\n\nDefault: 6 slides unless the brief says otherwise.\n\n| Audience \u002F format | Slides |\n|---|---|\n| Product overview \u002F lightning talk (5–10 min) | 6 |\n| Pitch deck (15 min) | 8–10 |\n| Investor update \u002F longer talk (20–30 min) | 12–18 |\n\nThen write out the rhythm before any HTML — for example, 8 slides:\n\n```\n01  hero light center  Cover\n02  light              Problem\n03  hero dark center   Big stat\n04  light              Three points\n05  dark               Pipeline\n06  hero light center  Quote\n07  light              Before \u002F after\n08  hero dark center   Ask\n```\n\nA healthy sequence has:\n- No 3+ same theme in a row\n- ≥ 1 `hero dark` AND ≥ 1 `hero light` (for 8+ slides)\n- Alternating breath every 3–4 slides\n\nShow this rhythm sketch to the user *before* writing slide HTML — they can redirect cheaply.\n\n### Step 3 — Paste and fill\n\nFor each planned slide, copy the matching `\u003Csection>` from `layouts.md` into the body. Replace bracketed text with real, specific copy. **No filler \u002F no lorem.** If a slide feels empty, the layout is wrong — pick a different one.\n\nTag each slide with `data-screen-label=\"01 Cover\"`, `\"02 Problem\"`, etc., in the order you wrote them. (The seed's first three slides already do this — extend the pattern.)\n\n### Step 4 — Self-check\n\nRun through `references\u002Fchecklist.md`. The \"Theme rhythm spot-check\" at the end is non-negotiable:\n\n```bash\ngrep 'class=\"slide' index.html\n```\n\nRead the resulting class list. If you see `light × 4 in a row`, swap one to `dark`. If no `hero dark` exists in an 8+ slide deck, promote one big-stat or closing slide.\n\n### Step 5 — Write the project file\n\nWrite the completed deck HTML to `index.html`.\n\nThen send one short ordinary assistant summary naming `index.html` and\ndescribing the deck. Do not output the full HTML source in chat and do not emit\na source-code `\u003Cartifact>` block.\n\n## Hard rules\n\n- **Theme class on every slide** (`light` | `dark` | `hero light` | `hero dark`). Bare `class=\"slide\"` = regression.\n- **No 3+ same theme in a row.**\n- **Display = serif via `var(--font-display)`.** `.h-hero` \u002F `.h-xl` \u002F `.h-md` already enforce.\n- **One accent per slide, used at most twice.**\n- **Don't rewrite the nav script.** It's proven.\n- **No `scrollIntoView()`.** Breaks iframe.\n- **`data-screen-label` on every slide.**\n",{"od":24,"name":5,"tags":39,"en_name":45,"zh_name":46,"triggers":47,"description":50,"en_description":50,"zh_description":51},{"mode":25,"preview":26,"category":29,"scenario":30,"design_system":31,"example_prompt":38},"deck",{"type":27,"entry":28},"html","index.html","corporate-strategy","strategy",{"requires":32,"sections":33},true,[34,35,36,37],"color","typography","layout","components","Create \"Write an Operating Review like a Disciplined COO\" as a decision-grade Corporate strategy deck in this template's own visual system. Subject: OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Audience: leadership team. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce the slide plan, written slides, visual direction, speaker-ready structure, and a critic pass against this rubric: would a board member know what to approve and why before page five.",[29,40,30,41,42,43,44,5],"board-pre-read-deck","board","business-review","decision-deck","commercial-slide-agent","Write an Operating Review like a Disciplined COO","像克制的 COO 一样写经营复盘",[40,29,45,46,41,30,42,48,49],"html deck","html slides","OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Built as a decision-grade corporate strategy deck for leadership team.\n","像克制的 COO 一样写经营复盘——一份可商业交付的企业战略 Deck，围绕真实主题、证据链与决策目标组织。\n","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fexamples\u002Fsimple-deck",104,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit","https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=feima.open-design-agent-kit","https:\u002F\u002Fgithub.com\u002Ffeimacode","2026-11-14 17:32:48",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":32},[62,65,68],{"tool":63,"command":64},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill simple-deck",{"tool":66,"command":67},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill simple-deck",{"tool":69,"command":70},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill simple-deck","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fexamples\u002Fsimple-deck\u002FSKILL.md",[73,79,85],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"assets\u002Ftemplate.html","ASSET","资产文件",15943,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fexamples\u002Fsimple-deck\u002Fassets\u002Ftemplate.html",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"example.html","REFERENCE","参考文档",11230,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fexamples\u002Fsimple-deck\u002Fexample.html",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"open-design.json",6030,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fexamples\u002Fsimple-deck\u002Fopen-design.json",[90,97,104,111,118,125],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7DDR9C4RR6E8F46YBJ8MW64","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7DDR57XHXAFBGKX3SYTGSJB","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7DDR2RM4F3FM5642JZBGJSF","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fwpds\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7DDQX3G9QDCBV5GGZGQ1NZN","weread-year-in-review-video-template","WeRead-inspired HyperFrames video template for vertical annual reading reports,\npersonal reading dashboards, book-note recaps, and shareable year-in-review\nstories. Use when users want a 9:16 HTML-to-MP4 reading report with warm paper\ntexture, editorial Chinese typography, book-page metaphors, data highlights,\nand deterministic motion.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fweread-year-in-review-video-template\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7DDQRGJEHQST6TXDH6ZAV5G","web-design-guidelines","Review UI code for Web Interface Guidelines compliance by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M7DDQKADVPZW1Z1HTVKXY542","web-clone","网站复刻 \u002F 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互\u002FWebGL\u002FCanvas\u002FThree.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树，覆盖静态站 \u002F React-Vue-Next 内容站 \u002F WebGL-Canvas 重前端站三大分支，并强制核对任何 AI 二手分析里的可执行代码。","https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fweb-clone\u002FSKILL.md",[],[]]