[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D97R1PDK72H0DFA7EDHTJ6":3,"skill-same:01M7D97R1PDK72H0DFA7EDHTJ6":71},{"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":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M7D97R1PDK72H0DFA7EDHTJ6","magazine-web-ppt",null,"For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query \"annual-marketing-plan\", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.","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\u002Fdesign-templates\u002Fguizang-ppt\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: magazine-web-ppt\nen_name: \"Write a Brand-to-Revenue Story like a Growth Strategy Lead\"\nzh_name: \"像增长策略负责人一样写品牌到收入故事\"\ndescription: |\n  For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query \"annual-marketing-plan\", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.\nen_description: |\n  For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query \"annual-marketing-plan\", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.\nzh_description: |\n  市场\u002F增长\u002FGTM场景：围绕 core query「annual-marketing-plan」把粗糙材料整理成“像增长策略负责人一样写品牌到收入故事”这类可购买、可复用的专业 Deck；突出受众、决策目标、证据链、风险取舍和评审标准。\ntags:\n  - \"marketing-gtm\"\n  - \"annual-marketing-plan\"\n  - \"launch\"\n  - \"campaign\"\n  - \"pipeline\"\n  - \"marketing\"\n  - \"decision-deck\"\n  - \"commercial-slide-agent\"\n  - \"guizang-ppt\"\ntriggers:\n  - \"annual-marketing-plan\"\n  - \"marketing-gtm\"\n  - \"Write a Brand-to-Revenue Story like a Growth Strategy Lead\"\n  - \"像增长策略负责人一样写品牌到收入故事\"\n  - \"launch\"\n  - \"campaign\"\n  - \"pipeline\"\n  - \"html deck\"\n  - \"html slides\"\nod:\n  mode: deck\n  default_for: deck\n  upstream: \"https:\u002F\u002Fgithub.com\u002Fop7418\u002Fguizang-ppt-skill\"\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: false\n  scenario: \"marketing\"\n  example_prompt: \"Create \\\"Write a Brand-to-Revenue Story like a Growth Strategy Lead\\\" as a Marketing and GTM deck in the Guizang Ppt visual system. Scene: annual-marketing-plan. 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 the plan connect creative choices to measurable growth.\"\n---\n\n# Magazine Web Ppt\n\n## What this skill does\n\nGenerates a **single-file HTML** horizontal-swipe deck with a visual tone of:\n\n- A **electronic magazine + electronic ink** hybrid style\n- A **WebGL fluid \u002F contour \u002F dispersion background** (visible on hero pages)\n- **Serif headlines (Noto Serif SC + Playfair Display) + sans-serif body (Noto Sans SC + Inter) + monospace metadata (IBM Plex Mono)**\n- **Lucide line icons** (no emoji)\n- **Horizontal left\u002Fright paging** (keyboard ← →, scroll wheel, touch swipe, bottom dots, ESC index)\n- **Smooth theme interpolation**: when you flip to a hero page, the colors and shader transition softly\n\nThis skill's aesthetic is not \"corporate PPT,\" nor \"consumer-internet UI\": it looks like *Monocle* magazine after code was stitched onto it.\n\n## When to use\n\n**Suitable scenarios**:\n- Offline talks \u002F internal industry talks \u002F private salons\n- AI new-product launches \u002F demo day\n- Talks with a strong personal style\n- A web version of slides that you \"make once, with no paging tool needed\"\n\n**Unsuitable scenarios**:\n- Long stretches of tabular data, stacked charts (use a regular PPT)\n- Training courseware (information density too low)\n- Multi-person collaborative editing (this is static HTML)\n\n## Workflow\n\n### Step 0 · Infer a direction; ask only when comparison is requested\n\nInfer one of the 5 magazine directions from the brief, audience, content, and\nknown context. Each direction packages its theme color, recommended layouts,\nchrome style, and slide count. Use the closest fit and continue without asking.\n\nOnly when the user explicitly asks to see or compare direction options, open\n`references\u002Fstyles.md` and present the 1-line summaries in one\n`direction-cards` question form:\n\n```\n1. Monocle Editorial · International magazine style ✦ default\n2. WIRED Tech · Data + engineering\n3. Kinfolk Slow · Slow living \u002F humanist\n4. Domus Architectural · Architecture \u002F sense of space\n5. Lab \u002F Reference · Academic + craft manual\n```\n\nIf the user says \"I don't know, you recommend\" or provides no direction cue:\n**default to Monocle Editorial** without asking, because it has the lowest\nfailure probability. If the user mentions \"AI \u002F benchmark \u002F technical launch\":\nchoose WIRED; \"reading \u002F private \u002F social circle\": choose Kinfolk; \"design \u002F\narchitecture \u002F portfolio\": choose Domus; \"research \u002F academic \u002F methodology\":\nchoose Lab.\n\nAfter picking a direction, create or update `项目记录.md` (Project Record) in the project folder, with the first line clearly stating direction + theme color + audience + duration (see the template at the end of `styles.md`). **Do not change direction at any point**: switching midway = everything before is wasted.\n\n### Step 1 · Resolve intent\n\n**If the user has already given a complete outline + images**, you can skip straight to Step 2.\n\nInfer the checklist below from the brief, project metadata, supplied content,\nand conversation. If a missing answer would materially change the deck and no\nsafe default exists, ask only those unresolved fields in one consolidated\nquestion form. Do not ask the checklist one by one.\n\n#### 6-question clarifying checklist\n\n> Direction and theme color are inferred in Step 0 unless the user explicitly\n> asks to compare options.\n\n| # | Question | Why ask it |\n|---|------|-----------|\n| 1 | **Who is the audience? Sharing scenario?** (internal industry \u002F commercial launch \u002F demo day \u002F private salon) | determines the language style and depth |\n| 2 | **Talk duration?** | 15 min ≈ 10 pages, 30 min ≈ 20 pages, 45 min ≈ 25-30 pages (see each direction's recommended range in `styles.md`) |\n| 3 | **Any source material?** (documents \u002F data \u002F old PPT \u002F article links) | with material, build on it; without, help them build |\n| 4 | **Any images? Where are they?** | see the \"Image convention\" below |\n| 5 | ~~**Which theme color do you want?**~~ | ✓ already decided by the direction in Step 0 |\n| 6 | **Any hard constraints?** (must include XX data \u002F must not show YY) | avoids rework |\n\n#### Outline assistance (if the user has no outline)\n\nUse the \"narrative arc\" template to build the skeleton, then fill in content:\n\n```\nHook       → 1 page   : throw out a contrast \u002F question \u002F hard number that makes people stop\nContext    → 1-2 pages : explain the background \u002F who you are \u002F why this topic\nCore       → 3-5 pages : the core content, interleaving Layouts 4\u002F5\u002F6\u002F9\u002F10\nShift      → 1 page    : break the expectation \u002F propose a new view\nTakeaway   → 1-2 pages : a punchline \u002F a suspenseful question \u002F a call to action\n```\n\nNarrative arc + page-count plan + theme rhythm table (see `layouts.md`); **align all three tables** before moving to Step 2.\n\nIt's best to save the outline as `项目记录.md` (Project Record) or `大纲-v1.md` (Outline v1) for later iteration.\n\n#### Image convention (tell the user)\n\nMake these clear to the user before starting:\n\n- **Folder location**: under `项目\u002FXXX\u002Fppt\u002Fimages\u002F` (sibling to `index.html`)\n- **Naming convention**: `{page number}-{semantic}.{ext}`, e.g. `01-cover.jpg` \u002F `03-figma.jpg` \u002F `05-dashboard.png`\n  - Pad the page number with zeros for easy sorting\n  - Use English for the semantic part, short, specific, matching the content\n- **Spec recommendations**:\n  - Each image ≥ 1600px wide (avoid blur on large screens)\n  - JPG for photos\u002Fscreenshots, PNG for transparent UI\u002Fcharts\n  - Keep total size under 10MB (affects paging smoothness)\n- **How to replace**: **same-name overwrite** is the most stable (no need to change the path in the HTML); if the filename changes, remember to globally search `images\u002Foldname` and change it to the new name\n- **What if there are no images**: align with the user; you can generate the structure with placeholder color blocks first and fill in the images later, but tell them that image-text mix pages like layouts 4\u002F5\u002F10 can't have their visuals verified without images\n\n### Step 2 · Copy the template\n\nCopy `assets\u002Ftemplate.html` to the target location (usually `项目\u002FXXX\u002Fppt\u002Findex.html`), and create an `images\u002F` folder as a sibling, ready to receive images.\n\n```bash\nmkdir -p \"项目\u002FXXX\u002Fppt\u002Fimages\"\ncp \"\u003CSKILL_ROOT>\u002Fassets\u002Ftemplate.html\" \"项目\u002FXXX\u002Fppt\u002Findex.html\"\n```\n\n`template.html` is a **complete, runnable** file: CSS, WebGL shader, paging JS, font\u002Ficon CDNs are all preset; only inside `\u003Cmain id=\"deck\">` are there 3 example slides (cover, act divider, blank filler page).\n\n#### 2.1 · Placeholders you must change (**easy to miss**)\n\nRight after copying, change the placeholders below, or the browser tab will show awkward text like \"[必填] replace with the PPT title\":\n\n| Location | Original | Change to |\n|------|------|--------|\n| `\u003Ctitle>` | `[必填] 替换为 PPT 标题 · Deck Title` | the actual deck title (e.g. `一种新的工作方式 · Luke Wroblewski`) |\n\nThe first thing to do every time you finish copying template.html: grep for \"[必填]\" to confirm everything is replaced.\n\n#### 2.2 · Choose the theme color (5 presets · no customization allowed)\n\nThis skill **only allows picking one of 5 carefully tuned presets**; it does not accept user-defined hex values: a wrong color pairing makes the visuals ugly in an instant, and protecting the aesthetic matters more than offering freedom.\n\n| # | Theme | Best for |\n|---|------|------|\n| 1 | 🖋 Ink Classic | general \u002F commercial launch \u002F the default when you don't know what to pick |\n| 2 | 🌊 Indigo Porcelain | tech \u002F research \u002F data \u002F technical keynotes |\n| 3 | 🌿 Forest Ink | nature \u002F sustainability \u002F culture \u002F non-fiction |\n| 4 | 🍂 Kraft Paper | nostalgic \u002F humanist \u002F literary \u002F indie magazines |\n| 5 | 🌙 Dune | art \u002F design \u002F creative \u002F gallery |\n\n**How to do it**:\n1. Recommend one based on the content theme, or just ask the user which one to pick\n2. Open `references\u002Fthemes.md` and find the `:root` block for the corresponding theme\n3. **Replace as a whole** the lines marked with the \"theme color\" comment in the opening `:root{` block of `assets\u002Ftemplate.html` (the copied version): `--ink` \u002F `--ink-rgb` \u002F `--paper` \u002F `--paper-rgb` \u002F `--paper-tint` \u002F `--ink-tint`\n4. All other CSS flows through `var(--...)`, no other changes needed\n\n**Hard rules**:\n- A deck uses only one theme, don't change colors midway\n- Don't accept an arbitrary hex value from the user: gently decline and show the 5 presets to pick from\n- Don't mix and match (e.g. take ink from Ink Classic and paper from Dune): it clashes completely\n\n### Step 3 · Fill in content\n\n#### 3.0 · Pre-check: class names must be defined in template.html (**most important**)\n\n**This is the source of all generation problems**. The layouts.md skeletons use many class names (`h-hero` \u002F `h-xl` \u002F `stat-card` \u002F `pipeline` \u002F `grid-2-7-5`, etc.); if `assets\u002Ftemplate.html`'s `\u003Cstyle>` has no corresponding definition, the browser falls back to default styles: the big title turns sans-serif, the data cards squeeze into a clump, the pipeline mushes into one line, the images pile up at the bottom of the page.\n\n**Before writing any slide code:**\n\n1. **First Read `assets\u002Ftemplate.html`** (at least through the end of the `\u003Cstyle>` block)\n2. **Against layouts.md's Pre-flight list**, confirm that every class you're going to use exists in the `\u003Cstyle>`\n3. If a class is missing: **add it to template.html's `\u003Cstyle>`**, don't rewrite it inline on every slide\n4. **template.html is the single source of class names**: don't invent new class names; if you need a custom one, use `style=\"...\"` inline\n\nClasses commonly missed (must be confirmed to exist in advance):\n`h-hero` \u002F `h-xl` \u002F `h-sub` \u002F `h-md` \u002F `lead` \u002F `kicker` \u002F `meta-row` \u002F `stat-card` \u002F `stat-label` \u002F `stat-nb` \u002F `stat-unit` \u002F `stat-note` \u002F `pipeline-section` \u002F `pipeline-label` \u002F `pipeline` \u002F `step` \u002F `step-nb` \u002F `step-title` \u002F `step-desc` \u002F `grid-2-7-5` \u002F `grid-2-6-6` \u002F `grid-2-8-4` \u002F `grid-3-3` \u002F `grid-6` \u002F `grid-3` \u002F `grid-4` \u002F `frame` \u002F `frame-img` \u002F `img-cap` \u002F `callout` \u002F `callout-src` \u002F `chrome` \u002F `foot`\n\n#### 3.0.5 · Plan the theme rhythm (**equally important as the class pre-check**)\n\n**Before picking layouts**, you must first list the theme class for each page (`hero dark` \u002F `hero light` \u002F `light` \u002F `dark`) and write it to a document or draft to align. For detailed rules, see the \"Theme rhythm planning\" section at the top of `references\u002Flayouts.md`.\n\n**Mandatory rules**:\n\n- Every page section must carry one of `light` \u002F `dark` \u002F `hero light` \u002F `hero dark`; don't write just `hero`\n- 3+ consecutive pages on the same theme = visual fatigue, not allowed\n- 8+ pages must have ≥1 `hero dark` + ≥1 `hero light`\n- The whole deck cannot have only `light` body pages; it must have a `dark` body page to create breathing room\n- Insert 1 hero page (cover\u002Fdivider\u002Fquestion\u002Fbig quote) every 3-4 pages\n\n**Self-check after generating**: `grep 'class=\"slide' index.html` lists all themes; manually confirm the rhythm is reasonable before delivering.\n\n#### 3.1 · Pick a layout\n\n**Don't write slides from scratch**. Open `references\u002Flayouts.md`; it has 10 ready-made layout skeletons, each a complete, paste-ready `\u003Csection>` code block:\n\n| Layout | Use |\n|---|---|\n| 1. Cover | page 1 |\n| 2. Act divider | each act's opening |\n| 3. Big numbers | throw out hard data |\n| 4. Lead image + text (Quote + Image) | identity contrast \u002F story |\n| 5. Image grid | multi-image comparison \u002F screenshot evidence |\n| 6. Two-column pipeline (Pipeline) | workflow process |\n| 7. Suspenseful close \u002F question page | act close \u002F wrap-up |\n| 8. Big quote page (Big Quote) | serif punchline \u002F takeaway |\n| 9. Side-by-side comparison (Before \u002F After) | old model vs new model |\n| 10. Image + text mix (Lead Image + Side Text) | information-dense image-text pages |\n\nPick the corresponding layout, paste it in, change the copy and image paths. **Be sure to complete the 3.0 pre-check first**.\n\n#### 3.2 · Image ratio rules\n\nAlways use a **standard ratio**, never the source image's odd ratio (like `2592\u002F1798`):\n\n| Scenario | Recommended ratio |\n|------|---------|\n| Lead image + text, main image | 16:10 or 4:3 + `max-height:56vh` |\n| Image grid (multi-image comparison) | **fixed `height:26vh`**, not aspect-ratio |\n| Small image left + text right | 1:1 or 3:2 |\n| Full-screen hero visual | 16:9 + `max-height:64vh` |\n| Image + text mix, small inset | 3:2 or 3:4 |\n\n**Never use `align-self:end` on an image**: it slides to the bottom of the cell, hidden by the browser toolbar. Use a grid container + `align-items:start` (already preset in the template) so the image sticks to the top; if you want the left column to stick to the bottom, use flex column + `justify-content:space-between`.\n\nComponent details (fonts, colors, grids, icons, callout, stat-card, etc.) are in `references\u002Fcomponents.md`.\n\n### Step 4 · Self-check against the checklist\n\nAfter generating, always open `references\u002Fchecklist.md` and check item by item. It summarizes **every pitfall stepped on during real iteration**; the P0-level issues (emoji, images breaking out, title wrapping, type division of labor) must all pass.\n\nA few items to watch especially:\n\n1. **Big titles must be serif**: if it shows as sans-serif, 99% of the time the Step 3.0 pre-check wasn't done and the `h-hero` class is missing from template.html\n2. **In image grids use only `height:Nvh`, not `aspect-ratio`** (it breaks out)\n3. **Images must not pile up at the bottom of the page**: don't use `align-self:end`, use grid + `align-items:start` (see Step 3.2)\n4. **Images may only use standard ratios** (16:10 \u002F 4:3 \u002F 3:2 \u002F 1:1 \u002F 16:9), don't copy the source image's odd ratio\n5. **Chinese big titles ≤ 5 characters and `nowrap`** (avoid 1 character per line)\n6. **Use Lucide, not emoji**\n7. **Serif for titles, sans-serif for body, mono for metadata**\n\n### Step 5 · Local preview\n\nJust open `index.html` directly in the browser. On macOS:\n\n```bash\nopen \"项目\u002FXXX\u002Fppt\u002Findex.html\"\n```\n\nNo local server needed. Images use the relative path `images\u002Fxxx.png`.\n\n### Step 6 · Iterate\n\nModify based on user feedback: the template's CSS is highly parameterized, and 90% of adjustments are changing inline styles (font size `font-size:Xvw` \u002F height `height:Yvh` \u002F spacing `gap:Zvh`).\n\n---\n\n## Resource file tour\n\n```\nmagazine-web-ppt\u002F\n├── SKILL.md              ← you are reading this\n├── assets\u002F\n│   ├── template.html     ← the complete runnable template (seed file)\n│   └── example-slides.html ← a 9-page sample deck (for the Examples preview)\n└── references\u002F\n    ├── styles.md         ← the 5 magazine directions (Monocle \u002F WIRED \u002F Kinfolk \u002F Domus \u002F Lab)\n    ├── components.md     ← component handbook (fonts, color, grid, icons, callout, stat, pipeline...)\n    ├── layouts.md        ← 10 page layout skeletons (paste-ready)\n    ├── themes.md         ← 5 theme color presets (pick only, no customization)\n    └── checklist.md      ← quality checklist (P0\u002FP1\u002FP2\u002FP3 tiers)\n```\n\n**Recommended loading order**:\n1. First read through `SKILL.md` (this file) to understand the whole\n2. **When picking a direction in Step 0, read `styles.md`**: each of the 5 directions packages up theme color + recommended layouts + chrome style\n3. After clarifying intent in Step 1, if the direction needs confirmation, read `themes.md` for palette details\n4. **Before starting, Read the `\u003Cstyle>` block of `assets\u002Ftemplate.html`**: this is the single source of class names; missing classes crash the whole page's styling\n5. Read `layouts.md` to pick a layout (the top has the Pre-flight class-name list and theme rhythm planning)\n6. When tuning details, read `components.md` to look up components\n7. After generating, read `checklist.md` to self-check (the top P0-0 rule enforces the pre-check)\n\n## Core design principles (philosophy)\n\n> These principles are distilled from 5 rounds of iteration on the \"one-person company\" talk deck. Violating any one of them makes the visual feel collapse.\n\n1. **Restraint over flash**: the WebGL background only shows through on hero pages, barely visible on ordinary pages\n2. **Structure over decoration**: no shadows, no floating cards, no padding boxes; all information relies on **large type + typeface contrast + grid whitespace**\n3. **Content hierarchy is defined jointly by type size and typeface**: largest serif = main title, medium serif = subtitle, large sans = lead, small sans = body, mono = metadata\n4. **Images are first-class citizens**: images are cropped only at the bottom, keeping the top and sides intact; grids use a fixed `height:Nvh`, not `aspect-ratio` stretching\n5. **Rhythm relies on hero pages**: hero and non-hero alternate, so the eyes don't tire\n6. **Consistent terminology**: Skills is just Skills, don't mix Chinese-English translation\n\n## Reference works\n\nThis skill's visual tone references:\n\n- Guizang's \"One-Person Company: Organizations Folded by AI\" talk (2026-04-22, 27 pages)\n- The layout of *Monocle* magazine\n- The demo from YC president Garry Tan's blog post \"Thin Harness, Fat Skills\"\n\nYou can treat these as style anchors.\n","# Magazine Web Ppt\n\n## What this skill does\n\nGenerates a **single-file HTML** horizontal-swipe deck with a visual tone of:\n\n- A **electronic magazine + electronic ink** hybrid style\n- A **WebGL fluid \u002F contour \u002F dispersion background** (visible on hero pages)\n- **Serif headlines (Noto Serif SC + Playfair Display) + sans-serif body (Noto Sans SC + Inter) + monospace metadata (IBM Plex Mono)**\n- **Lucide line icons** (no emoji)\n- **Horizontal left\u002Fright paging** (keyboard ← →, scroll wheel, touch swipe, bottom dots, ESC index)\n- **Smooth theme interpolation**: when you flip to a hero page, the colors and shader transition softly\n\nThis skill's aesthetic is not \"corporate PPT,\" nor \"consumer-internet UI\": it looks like *Monocle* magazine after code was stitched onto it.\n\n## When to use\n\n**Suitable scenarios**:\n- Offline talks \u002F internal industry talks \u002F private salons\n- AI new-product launches \u002F demo day\n- Talks with a strong personal style\n- A web version of slides that you \"make once, with no paging tool needed\"\n\n**Unsuitable scenarios**:\n- Long stretches of tabular data, stacked charts (use a regular PPT)\n- Training courseware (information density too low)\n- Multi-person collaborative editing (this is static HTML)\n\n## Workflow\n\n### Step 0 · Infer a direction; ask only when comparison is requested\n\nInfer one of the 5 magazine directions from the brief, audience, content, and\nknown context. Each direction packages its theme color, recommended layouts,\nchrome style, and slide count. Use the closest fit and continue without asking.\n\nOnly when the user explicitly asks to see or compare direction options, open\n`references\u002Fstyles.md` and present the 1-line summaries in one\n`direction-cards` question form:\n\n```\n1. Monocle Editorial · International magazine style ✦ default\n2. WIRED Tech · Data + engineering\n3. Kinfolk Slow · Slow living \u002F humanist\n4. Domus Architectural · Architecture \u002F sense of space\n5. Lab \u002F Reference · Academic + craft manual\n```\n\nIf the user says \"I don't know, you recommend\" or provides no direction cue:\n**default to Monocle Editorial** without asking, because it has the lowest\nfailure probability. If the user mentions \"AI \u002F benchmark \u002F technical launch\":\nchoose WIRED; \"reading \u002F private \u002F social circle\": choose Kinfolk; \"design \u002F\narchitecture \u002F portfolio\": choose Domus; \"research \u002F academic \u002F methodology\":\nchoose Lab.\n\nAfter picking a direction, create or update `项目记录.md` (Project Record) in the project folder, with the first line clearly stating direction + theme color + audience + duration (see the template at the end of `styles.md`). **Do not change direction at any point**: switching midway = everything before is wasted.\n\n### Step 1 · Resolve intent\n\n**If the user has already given a complete outline + images**, you can skip straight to Step 2.\n\nInfer the checklist below from the brief, project metadata, supplied content,\nand conversation. If a missing answer would materially change the deck and no\nsafe default exists, ask only those unresolved fields in one consolidated\nquestion form. Do not ask the checklist one by one.\n\n#### 6-question clarifying checklist\n\n> Direction and theme color are inferred in Step 0 unless the user explicitly\n> asks to compare options.\n\n| # | Question | Why ask it |\n|---|------|-----------|\n| 1 | **Who is the audience? Sharing scenario?** (internal industry \u002F commercial launch \u002F demo day \u002F private salon) | determines the language style and depth |\n| 2 | **Talk duration?** | 15 min ≈ 10 pages, 30 min ≈ 20 pages, 45 min ≈ 25-30 pages (see each direction's recommended range in `styles.md`) |\n| 3 | **Any source material?** (documents \u002F data \u002F old PPT \u002F article links) | with material, build on it; without, help them build |\n| 4 | **Any images? Where are they?** | see the \"Image convention\" below |\n| 5 | ~~**Which theme color do you want?**~~ | ✓ already decided by the direction in Step 0 |\n| 6 | **Any hard constraints?** (must include XX data \u002F must not show YY) | avoids rework |\n\n#### Outline assistance (if the user has no outline)\n\nUse the \"narrative arc\" template to build the skeleton, then fill in content:\n\n```\nHook       → 1 page   : throw out a contrast \u002F question \u002F hard number that makes people stop\nContext    → 1-2 pages : explain the background \u002F who you are \u002F why this topic\nCore       → 3-5 pages : the core content, interleaving Layouts 4\u002F5\u002F6\u002F9\u002F10\nShift      → 1 page    : break the expectation \u002F propose a new view\nTakeaway   → 1-2 pages : a punchline \u002F a suspenseful question \u002F a call to action\n```\n\nNarrative arc + page-count plan + theme rhythm table (see `layouts.md`); **align all three tables** before moving to Step 2.\n\nIt's best to save the outline as `项目记录.md` (Project Record) or `大纲-v1.md` (Outline v1) for later iteration.\n\n#### Image convention (tell the user)\n\nMake these clear to the user before starting:\n\n- **Folder location**: under `项目\u002FXXX\u002Fppt\u002Fimages\u002F` (sibling to `index.html`)\n- **Naming convention**: `{page number}-{semantic}.{ext}`, e.g. `01-cover.jpg` \u002F `03-figma.jpg` \u002F `05-dashboard.png`\n  - Pad the page number with zeros for easy sorting\n  - Use English for the semantic part, short, specific, matching the content\n- **Spec recommendations**:\n  - Each image ≥ 1600px wide (avoid blur on large screens)\n  - JPG for photos\u002Fscreenshots, PNG for transparent UI\u002Fcharts\n  - Keep total size under 10MB (affects paging smoothness)\n- **How to replace**: **same-name overwrite** is the most stable (no need to change the path in the HTML); if the filename changes, remember to globally search `images\u002Foldname` and change it to the new name\n- **What if there are no images**: align with the user; you can generate the structure with placeholder color blocks first and fill in the images later, but tell them that image-text mix pages like layouts 4\u002F5\u002F10 can't have their visuals verified without images\n\n### Step 2 · Copy the template\n\nCopy `assets\u002Ftemplate.html` to the target location (usually `项目\u002FXXX\u002Fppt\u002Findex.html`), and create an `images\u002F` folder as a sibling, ready to receive images.\n\n```bash\nmkdir -p \"项目\u002FXXX\u002Fppt\u002Fimages\"\ncp \"\u003CSKILL_ROOT>\u002Fassets\u002Ftemplate.html\" \"项目\u002FXXX\u002Fppt\u002Findex.html\"\n```\n\n`template.html` is a **complete, runnable** file: CSS, WebGL shader, paging JS, font\u002Ficon CDNs are all preset; only inside `\u003Cmain id=\"deck\">` are there 3 example slides (cover, act divider, blank filler page).\n\n#### 2.1 · Placeholders you must change (**easy to miss**)\n\nRight after copying, change the placeholders below, or the browser tab will show awkward text like \"[必填] replace with the PPT title\":\n\n| Location | Original | Change to |\n|------|------|--------|\n| `\u003Ctitle>` | `[必填] 替换为 PPT 标题 · Deck Title` | the actual deck title (e.g. `一种新的工作方式 · Luke Wroblewski`) |\n\nThe first thing to do every time you finish copying template.html: grep for \"[必填]\" to confirm everything is replaced.\n\n#### 2.2 · Choose the theme color (5 presets · no customization allowed)\n\nThis skill **only allows picking one of 5 carefully tuned presets**; it does not accept user-defined hex values: a wrong color pairing makes the visuals ugly in an instant, and protecting the aesthetic matters more than offering freedom.\n\n| # | Theme | Best for |\n|---|------|------|\n| 1 | 🖋 Ink Classic | general \u002F commercial launch \u002F the default when you don't know what to pick |\n| 2 | 🌊 Indigo Porcelain | tech \u002F research \u002F data \u002F technical keynotes |\n| 3 | 🌿 Forest Ink | nature \u002F sustainability \u002F culture \u002F non-fiction |\n| 4 | 🍂 Kraft Paper | nostalgic \u002F humanist \u002F literary \u002F indie magazines |\n| 5 | 🌙 Dune | art \u002F design \u002F creative \u002F gallery |\n\n**How to do it**:\n1. Recommend one based on the content theme, or just ask the user which one to pick\n2. Open `references\u002Fthemes.md` and find the `:root` block for the corresponding theme\n3. **Replace as a whole** the lines marked with the \"theme color\" comment in the opening `:root{` block of `assets\u002Ftemplate.html` (the copied version): `--ink` \u002F `--ink-rgb` \u002F `--paper` \u002F `--paper-rgb` \u002F `--paper-tint` \u002F `--ink-tint`\n4. All other CSS flows through `var(--...)`, no other changes needed\n\n**Hard rules**:\n- A deck uses only one theme, don't change colors midway\n- Don't accept an arbitrary hex value from the user: gently decline and show the 5 presets to pick from\n- Don't mix and match (e.g. take ink from Ink Classic and paper from Dune): it clashes completely\n\n### Step 3 · Fill in content\n\n#### 3.0 · Pre-check: class names must be defined in template.html (**most important**)\n\n**This is the source of all generation problems**. The layouts.md skeletons use many class names (`h-hero` \u002F `h-xl` \u002F `stat-card` \u002F `pipeline` \u002F `grid-2-7-5`, etc.); if `assets\u002Ftemplate.html`'s `\u003Cstyle>` has no corresponding definition, the browser falls back to default styles: the big title turns sans-serif, the data cards squeeze into a clump, the pipeline mushes into one line, the images pile up at the bottom of the page.\n\n**Before writing any slide code:**\n\n1. **First Read `assets\u002Ftemplate.html`** (at least through the end of the `\u003Cstyle>` block)\n2. **Against layouts.md's Pre-flight list**, confirm that every class you're going to use exists in the `\u003Cstyle>`\n3. If a class is missing: **add it to template.html's `\u003Cstyle>`**, don't rewrite it inline on every slide\n4. **template.html is the single source of class names**: don't invent new class names; if you need a custom one, use `style=\"...\"` inline\n\nClasses commonly missed (must be confirmed to exist in advance):\n`h-hero` \u002F `h-xl` \u002F `h-sub` \u002F `h-md` \u002F `lead` \u002F `kicker` \u002F `meta-row` \u002F `stat-card` \u002F `stat-label` \u002F `stat-nb` \u002F `stat-unit` \u002F `stat-note` \u002F `pipeline-section` \u002F `pipeline-label` \u002F `pipeline` \u002F `step` \u002F `step-nb` \u002F `step-title` \u002F `step-desc` \u002F `grid-2-7-5` \u002F `grid-2-6-6` \u002F `grid-2-8-4` \u002F `grid-3-3` \u002F `grid-6` \u002F `grid-3` \u002F `grid-4` \u002F `frame` \u002F `frame-img` \u002F `img-cap` \u002F `callout` \u002F `callout-src` \u002F `chrome` \u002F `foot`\n\n#### 3.0.5 · Plan the theme rhythm (**equally important as the class pre-check**)\n\n**Before picking layouts**, you must first list the theme class for each page (`hero dark` \u002F `hero light` \u002F `light` \u002F `dark`) and write it to a document or draft to align. For detailed rules, see the \"Theme rhythm planning\" section at the top of `references\u002Flayouts.md`.\n\n**Mandatory rules**:\n\n- Every page section must carry one of `light` \u002F `dark` \u002F `hero light` \u002F `hero dark`; don't write just `hero`\n- 3+ consecutive pages on the same theme = visual fatigue, not allowed\n- 8+ pages must have ≥1 `hero dark` + ≥1 `hero light`\n- The whole deck cannot have only `light` body pages; it must have a `dark` body page to create breathing room\n- Insert 1 hero page (cover\u002Fdivider\u002Fquestion\u002Fbig quote) every 3-4 pages\n\n**Self-check after generating**: `grep 'class=\"slide' index.html` lists all themes; manually confirm the rhythm is reasonable before delivering.\n\n#### 3.1 · Pick a layout\n\n**Don't write slides from scratch**. Open `references\u002Flayouts.md`; it has 10 ready-made layout skeletons, each a complete, paste-ready `\u003Csection>` code block:\n\n| Layout | Use |\n|---|---|\n| 1. Cover | page 1 |\n| 2. Act divider | each act's opening |\n| 3. Big numbers | throw out hard data |\n| 4. Lead image + text (Quote + Image) | identity contrast \u002F story |\n| 5. Image grid | multi-image comparison \u002F screenshot evidence |\n| 6. Two-column pipeline (Pipeline) | workflow process |\n| 7. Suspenseful close \u002F question page | act close \u002F wrap-up |\n| 8. Big quote page (Big Quote) | serif punchline \u002F takeaway |\n| 9. Side-by-side comparison (Before \u002F After) | old model vs new model |\n| 10. Image + text mix (Lead Image + Side Text) | information-dense image-text pages |\n\nPick the corresponding layout, paste it in, change the copy and image paths. **Be sure to complete the 3.0 pre-check first**.\n\n#### 3.2 · Image ratio rules\n\nAlways use a **standard ratio**, never the source image's odd ratio (like `2592\u002F1798`):\n\n| Scenario | Recommended ratio |\n|------|---------|\n| Lead image + text, main image | 16:10 or 4:3 + `max-height:56vh` |\n| Image grid (multi-image comparison) | **fixed `height:26vh`**, not aspect-ratio |\n| Small image left + text right | 1:1 or 3:2 |\n| Full-screen hero visual | 16:9 + `max-height:64vh` |\n| Image + text mix, small inset | 3:2 or 3:4 |\n\n**Never use `align-self:end` on an image**: it slides to the bottom of the cell, hidden by the browser toolbar. Use a grid container + `align-items:start` (already preset in the template) so the image sticks to the top; if you want the left column to stick to the bottom, use flex column + `justify-content:space-between`.\n\nComponent details (fonts, colors, grids, icons, callout, stat-card, etc.) are in `references\u002Fcomponents.md`.\n\n### Step 4 · Self-check against the checklist\n\nAfter generating, always open `references\u002Fchecklist.md` and check item by item. It summarizes **every pitfall stepped on during real iteration**; the P0-level issues (emoji, images breaking out, title wrapping, type division of labor) must all pass.\n\nA few items to watch especially:\n\n1. **Big titles must be serif**: if it shows as sans-serif, 99% of the time the Step 3.0 pre-check wasn't done and the `h-hero` class is missing from template.html\n2. **In image grids use only `height:Nvh`, not `aspect-ratio`** (it breaks out)\n3. **Images must not pile up at the bottom of the page**: don't use `align-self:end`, use grid + `align-items:start` (see Step 3.2)\n4. **Images may only use standard ratios** (16:10 \u002F 4:3 \u002F 3:2 \u002F 1:1 \u002F 16:9), don't copy the source image's odd ratio\n5. **Chinese big titles ≤ 5 characters and `nowrap`** (avoid 1 character per line)\n6. **Use Lucide, not emoji**\n7. **Serif for titles, sans-serif for body, mono for metadata**\n\n### Step 5 · Local preview\n\nJust open `index.html` directly in the browser. On macOS:\n\n```bash\nopen \"项目\u002FXXX\u002Fppt\u002Findex.html\"\n```\n\nNo local server needed. Images use the relative path `images\u002Fxxx.png`.\n\n### Step 6 · Iterate\n\nModify based on user feedback: the template's CSS is highly parameterized, and 90% of adjustments are changing inline styles (font size `font-size:Xvw` \u002F height `height:Yvh` \u002F spacing `gap:Zvh`).\n\n---\n\n## Resource file tour\n\n```\nmagazine-web-ppt\u002F\n├── SKILL.md              ← you are reading this\n├── assets\u002F\n│   ├── template.html     ← the complete runnable template (seed file)\n│   └── example-slides.html ← a 9-page sample deck (for the Examples preview)\n└── references\u002F\n    ├── styles.md         ← the 5 magazine directions (Monocle \u002F WIRED \u002F Kinfolk \u002F Domus \u002F Lab)\n    ├── components.md     ← component handbook (fonts, color, grid, icons, callout, stat, pipeline...)\n    ├── layouts.md        ← 10 page layout skeletons (paste-ready)\n    ├── themes.md         ← 5 theme color presets (pick only, no customization)\n    └── checklist.md      ← quality checklist (P0\u002FP1\u002FP2\u002FP3 tiers)\n```\n\n**Recommended loading order**:\n1. First read through `SKILL.md` (this file) to understand the whole\n2. **When picking a direction in Step 0, read `styles.md`**: each of the 5 directions packages up theme color + recommended layouts + chrome style\n3. After clarifying intent in Step 1, if the direction needs confirmation, read `themes.md` for palette details\n4. **Before starting, Read the `\u003Cstyle>` block of `assets\u002Ftemplate.html`**: this is the single source of class names; missing classes crash the whole page's styling\n5. Read `layouts.md` to pick a layout (the top has the Pre-flight class-name list and theme rhythm planning)\n6. When tuning details, read `components.md` to look up components\n7. After generating, read `checklist.md` to self-check (the top P0-0 rule enforces the pre-check)\n\n## Core design principles (philosophy)\n\n> These principles are distilled from 5 rounds of iteration on the \"one-person company\" talk deck. Violating any one of them makes the visual feel collapse.\n\n1. **Restraint over flash**: the WebGL background only shows through on hero pages, barely visible on ordinary pages\n2. **Structure over decoration**: no shadows, no floating cards, no padding boxes; all information relies on **large type + typeface contrast + grid whitespace**\n3. **Content hierarchy is defined jointly by type size and typeface**: largest serif = main title, medium serif = subtitle, large sans = lead, small sans = body, mono = metadata\n4. **Images are first-class citizens**: images are cropped only at the bottom, keeping the top and sides intact; grids use a fixed `height:Nvh`, not `aspect-ratio` stretching\n5. **Rhythm relies on hero pages**: hero and non-hero alternate, so the eyes don't tire\n6. **Consistent terminology**: Skills is just Skills, don't mix Chinese-English translation\n\n## Reference works\n\nThis skill's visual tone references:\n\n- Guizang's \"One-Person Company: Organizations Folded by AI\" talk (2026-04-22, 27 pages)\n- The layout of *Monocle* magazine\n- The demo from YC president Garry Tan's blog post \"Thin Harness, Fat Skills\"\n\nYou can treat these as style anchors.\n",{"od":24,"name":5,"tags":33,"en_name":42,"zh_name":43,"triggers":44,"description":47,"en_description":47,"zh_description":48},{"mode":25,"preview":26,"scenario":29,"upstream":30,"default_for":25,"design_system":31,"example_prompt":32},"deck",{"type":27,"entry":28},"html","index.html","marketing","https:\u002F\u002Fgithub.com\u002Fop7418\u002Fguizang-ppt-skill",{"requires":20},"Create \"Write a Brand-to-Revenue Story like a Growth Strategy Lead\" as a Marketing and GTM deck in the Guizang Ppt visual system. Scene: annual-marketing-plan. 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 the plan connect creative choices to measurable growth.",[34,35,36,37,38,29,39,40,41],"marketing-gtm","annual-marketing-plan","launch","campaign","pipeline","decision-deck","commercial-slide-agent","guizang-ppt","Write a Brand-to-Revenue Story like a Growth Strategy Lead","像增长策略负责人一样写品牌到收入故事",[35,34,42,43,36,37,38,45,46],"html deck","html slides","For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query \"annual-marketing-plan\", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.\n","市场\u002F增长\u002FGTM场景：围绕 core query「annual-marketing-plan」把粗糙材料整理成“像增长策略负责人一样写品牌到收入故事”这类可购买、可复用的专业 Deck；突出受众、决策目标、证据链、风险取舍和评审标准。\n","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fdesign-templates\u002Fguizang-ppt",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill magazine-web-ppt",{"tool":63,"command":64},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill magazine-web-ppt",{"tool":66,"command":67},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill magazine-web-ppt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fdesign-templates\u002Fguizang-ppt\u002FSKILL.md",true,[],[72,79,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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",[],[]]