[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D4CT0DNN5PJ4RYYWM2M6Y4":3,"skill-same:01M7D4CT0DNN5PJ4RYYWM2M6Y4":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7D4CT0DNN5PJ4RYYWM2M6Y4","open-design-docs",null,"Turn a folder of Markdown documents (ADRs, RFCs, runbooks, notes) into designed HTML pages, one per file, all in one style, and keep them in step when the Markdown changes — use whenever the user wants several Markdown files (a docs folder, ADRs, RFCs, runbooks, meeting notes) turned into HTML pages, or wants HTML versions of existing docs refreshed after edits","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\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"open-design-docs\"\ndescription: Turn a folder of Markdown documents (ADRs, RFCs, runbooks, notes) into designed HTML pages, one per file, all in one style, and keep them in step when the Markdown changes — use whenever the user wants several Markdown files (a docs folder, ADRs, RFCs, runbooks, meeting notes) turned into HTML pages, or wants HTML versions of existing docs refreshed after edits\nargument-hint: which files, and optionally the style (e.g. \"docs\u002Fadr\u002F*.md as ADR pages\")\n---\n\n\u003C!-- generated:curated-entry -->\n\nTurn existing Markdown documents into designed HTML pages with Open Design, one page per file.\n\nRequest: \"$ARGUMENTS\" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: \"Which Markdown files should become pages, and in what style?\")\n\n**How to talk to the user.** Many people using Open Design don't write code, so:\n- Use the user's own words. If they say \"artifact\", \"design tokens\" or give a file path, use those terms back; otherwise use the plain words below.\n- Keep the machinery out of replies: no tool names, no ids like `od:prototype:poster-hero`, no internal files (`.artifact.json`, `.comments.json`, `config.json`), and not the words \"register\", \"manifest\", \"sidecar\", \"entry\" or \"surface\", unless the user used them first.\n- Explain a print term the first time it comes up, in one short clause, and not again.\n- Say where a file is the way the user would find it (\"in your Open Design folder, under seed-swap-flyer\"). Give a raw path only where the user can click it (Claude Code, Claude Desktop's Code tab, VS Code) or asks for it.\n- End each reply that finishes a step with one line on what they can do next, with at most two options (\"Want it in Instagram sizes too, or is it ready to print?\").\n\n| Instead of | Say |\n|---|---|\n| artifact, entry, registered | your design, saved |\n| design system, active design system | your style (the first time: \"a saved style: colours, fonts and spacing\") |\n| surface, skill, template, recipe | kind of design, starting layout, or nothing |\n| workspace, output directory | your folder, your Open Design folder |\n| bleed | print edge (\"a few millimetres extra that the printer trims off\") |\n| trim size | final size |\n| preflight findings, errors | \"I checked it and fixed…\", \"one thing to look at:\" |\n| export | save as PDF, save as an image |\n| inline preview, MCP App | the preview above |\n\n## 1. Find the files\n\nResolve the folder or glob in the request with your own file tools (for example `docs\u002Fadr\u002F*.md`). List what you found.\n\n- More than 20 files: tell the user how many there are and ask whether to do all of them or a subset. Don't start until they answer.\n- No files: say so and stop.\n\n## 2. Pick one template for the set\n\nAll pages in a set share one template, so they read as one collection. Choose by what the files are, or use the style the user named:\n\n| Files | Skill |\n|---|---|\n| Architecture decisions | `od:prototype:adr` |\n| Proposals, design docs | `od:prototype:rfc` |\n| Incident write-ups | `od:prototype:postmortem` |\n| Runbooks | `od:prototype:eng-runbook` |\n| Release notes or changelogs | `od:prototype:changelog-page` |\n| Long-form notes, essays, anything else | `od:prototype:doc-kami-parchment` |\n\nDerive a `collectionId` from the folder name (for example `docs-adr`) and a readable `collectionName`.\n\n## 3. On a re-run, only redo what changed\n\nIf pages from an earlier run exist (look for artifacts in that collection, or call `get_open_design_artifact` on each), compare: a page whose `staleSources` lists its Markdown file is out of date and gets regenerated; a page that isn't stale is skipped; a file with no page yet gets one. Tell the user what you'll regenerate and what you'll skip.\n\n## 4. Build each page\n\nFor each file, in order:\n\n1. Call `read_open_design_source` with the file. Use only what it returns: never add facts the Markdown doesn't have.\n2. Call `prepare_open_design_brief` with the chosen skill, a brief naming the file, `collectionId`, `collectionName`, and `screenRole` set to the file's name.\n3. Write the page, keeping the document's own headings, structure and status (for ADRs and RFCs, its status goes in the `data-od-status` banner). Link to sibling pages in the set where the Markdown links to the sibling `.md` file.\n4. Call `register_open_design_artifact` with the same collection values and `sources: [\"\u003Cthe .md path>\"]`, so a later run can tell when the Markdown changed.\n\nCheck the first page with `check_open_design_artifact` and fix its errors before doing the rest, so mistakes aren't copied into every page. Check the others at the end.\n\n## 5. Report\n\nList each page with its source file, and anything skipped or still flagged. In VS Code, mention the Collections view, where the whole set opens with Prev\u002FNext.\n","\u003C!-- generated:curated-entry -->\n\nTurn existing Markdown documents into designed HTML pages with Open Design, one page per file.\n\nRequest: \"$ARGUMENTS\" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: \"Which Markdown files should become pages, and in what style?\")\n\n**How to talk to the user.** Many people using Open Design don't write code, so:\n- Use the user's own words. If they say \"artifact\", \"design tokens\" or give a file path, use those terms back; otherwise use the plain words below.\n- Keep the machinery out of replies: no tool names, no ids like `od:prototype:poster-hero`, no internal files (`.artifact.json`, `.comments.json`, `config.json`), and not the words \"register\", \"manifest\", \"sidecar\", \"entry\" or \"surface\", unless the user used them first.\n- Explain a print term the first time it comes up, in one short clause, and not again.\n- Say where a file is the way the user would find it (\"in your Open Design folder, under seed-swap-flyer\"). Give a raw path only where the user can click it (Claude Code, Claude Desktop's Code tab, VS Code) or asks for it.\n- End each reply that finishes a step with one line on what they can do next, with at most two options (\"Want it in Instagram sizes too, or is it ready to print?\").\n\n| Instead of | Say |\n|---|---|\n| artifact, entry, registered | your design, saved |\n| design system, active design system | your style (the first time: \"a saved style: colours, fonts and spacing\") |\n| surface, skill, template, recipe | kind of design, starting layout, or nothing |\n| workspace, output directory | your folder, your Open Design folder |\n| bleed | print edge (\"a few millimetres extra that the printer trims off\") |\n| trim size | final size |\n| preflight findings, errors | \"I checked it and fixed…\", \"one thing to look at:\" |\n| export | save as PDF, save as an image |\n| inline preview, MCP App | the preview above |\n\n## 1. Find the files\n\nResolve the folder or glob in the request with your own file tools (for example `docs\u002Fadr\u002F*.md`). List what you found.\n\n- More than 20 files: tell the user how many there are and ask whether to do all of them or a subset. Don't start until they answer.\n- No files: say so and stop.\n\n## 2. Pick one template for the set\n\nAll pages in a set share one template, so they read as one collection. Choose by what the files are, or use the style the user named:\n\n| Files | Skill |\n|---|---|\n| Architecture decisions | `od:prototype:adr` |\n| Proposals, design docs | `od:prototype:rfc` |\n| Incident write-ups | `od:prototype:postmortem` |\n| Runbooks | `od:prototype:eng-runbook` |\n| Release notes or changelogs | `od:prototype:changelog-page` |\n| Long-form notes, essays, anything else | `od:prototype:doc-kami-parchment` |\n\nDerive a `collectionId` from the folder name (for example `docs-adr`) and a readable `collectionName`.\n\n## 3. On a re-run, only redo what changed\n\nIf pages from an earlier run exist (look for artifacts in that collection, or call `get_open_design_artifact` on each), compare: a page whose `staleSources` lists its Markdown file is out of date and gets regenerated; a page that isn't stale is skipped; a file with no page yet gets one. Tell the user what you'll regenerate and what you'll skip.\n\n## 4. Build each page\n\nFor each file, in order:\n\n1. Call `read_open_design_source` with the file. Use only what it returns: never add facts the Markdown doesn't have.\n2. Call `prepare_open_design_brief` with the chosen skill, a brief naming the file, `collectionId`, `collectionName`, and `screenRole` set to the file's name.\n3. Write the page, keeping the document's own headings, structure and status (for ADRs and RFCs, its status goes in the `data-od-status` banner). Link to sibling pages in the set where the Markdown links to the sibling `.md` file.\n4. Call `register_open_design_artifact` with the same collection values and `sources: [\"\u003Cthe .md path>\"]`, so a later run can tell when the Markdown changed.\n\nCheck the first page with `check_open_design_artifact` and fix its errors before doing the rest, so mistakes aren't copied into every page. Check the others at the end.\n\n## 5. Report\n\nList each page with its source file, and anything skipped or still flagged. In VS Code, mention the Collections view, where the whole set opens with Prev\u002FNext.\n",{"name":5,"description":7,"argument-hint":24},"which files, and optionally the style (e.g. \"docs\u002Fadr\u002F*.md as ADR pages\")","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-docs",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-docs",{"tool":39,"command":40},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-docs",{"tool":42,"command":43},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-docs\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]