[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D4D5393VX6WNSTMGJYCA1P":3,"skill-same:01M7D4D5393VX6WNSTMGJYCA1P":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},"01M7D4D5393VX6WNSTMGJYCA1P","open-design-explore",null,"Explore 2–4 deliberately different design directions for one brief, compare them side by side, then build out the one you pick — use whenever the user explicitly asks for several options, directions, alternatives or versions of a design to compare (\"show me three directions for…\", \"a few different takes on…\"), even if they don't mention Open Design; not for a single, ordinary design request","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-explore\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"open-design-explore\"\ndescription: Explore 2–4 deliberately different design directions for one brief, compare them side by side, then build out the one you pick — use whenever the user explicitly asks for several options, directions, alternatives or versions of a design to compare (\"show me three directions for…\", \"a few different takes on…\"), even if they don't mention Open Design; not for a single, ordinary design request\nargument-hint: what to design, and optionally how many directions or what should vary (e.g. \"pricing page, 3 directions\")\n---\n\n\u003C!-- generated:curated-entry -->\n\nExplore several deliberately different design directions with Open Design, compare them side by side, and take the chosen one forward.\n\nBrief: \"$ARGUMENTS\" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: \"What should we explore directions for?\")\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. Plan the directions\n\nIf the brief is empty, ask the user what to design before doing anything else.\n\nCall `list_open_design_skills` to find the skill that fits what's being designed (a landing page, a deck, a dashboard…). Then call `prepare_open_design_exploration` with that `skillId` and the brief:\n\n- `count`: the number of directions the user asked for (2–4). Default 3.\n- If the user named what should vary (\"three hero concepts\", \"different pricing layouts\"), pass `axis: \"custom\"` and `customDirections`, one `{ label, brief }` per direction.\n- Otherwise leave `axis` out. The tool picks visual styles when no design system is active, and layout or narrative structures when one is, so the brand is kept.\n- Pass `directionIds` only when the brief's tone clearly calls for specific directions, e.g. `editorial-monocle` for a magazine or `brutalist-experimental` for an art or agency site.\n\nIf the result says the active design system was set aside, tell the user.\n\n## 2. Generate each direction\n\nFor each direction in the result, follow `sharedInstructions` followed by that direction's own `instructions`. Write its file at exactly its `suggestedEntryPath`, then call `register_open_design_artifact` with the `explorationId`, the direction's `directionId`, kind, title and `sourceSkillId`.\n\nThese are **sketches**: one screen, or a cover plus two slides for a deck. Divergence matters more than polish. If you can delegate to sub-agents, generate the directions in parallel and give each one `sharedInstructions` plus its own `instructions`.\n\n## 3. Compare\n\nCall `compare_open_design_exploration` with `contactSheet: true`. If you can view images, open the contact sheet and check that the directions look clearly different (layout and hero pattern, not just colour). Regenerate any direction that resembles another, then compare again.\n\n## 4. Present\n\nGive the user the comparison page path (it opens in any browser straight from the file system and shows every direction side by side), and the contact sheet path if one was made. In one line each, say how the directions differ. Ask which one to take forward, and whether to:\n\n- **build it out** at full fidelity,\n- **merge** in parts of another direction (\"B, with A's hero\"), or\n- **save it as a design system** for later work.\n\n\u003C!-- claude-only -->\n**In Claude Desktop Chat**, call `show_open_design_artifact` with the `explorationId` to show the directions side by side, and where `show_open_design_questions` is in your tool list, ask the choice through it instead of a chat message: a `direction` question with one option per direction (`imageRef: \"artifact:\u003Cits entryPath>\"`), a `next` question (Build it out, Merge in parts of another, Save as a design system) and a short `text` question for anything to change or take from another direction. Read the `\u003C!-- od-answers {...} -->` line of the reply (`you-pick` means choose for them), then go on to step 5. If the user types their answer or taps \"Take this one\" instead, use that.\n\u003C!-- \u002Fclaude-only -->\n\n## 5. Take the choice forward\n\nCall `choose_open_design_direction` with the `explorationId`, the chosen `directionId`, `next` (`build-out`, `merge` with `mergeFrom`, or `save-design-system`) and the user's own adjustments as `notes`. Follow the returned `instructions` and register the result as they say.\n\n\u003C!-- claude-only -->\n**Artifact preview.** If you have an Artifact tool, publish the result as its private artifact preview (the built-out design, not the sketches) once it's registered: call `publish_open_design_artifact` with `provider: \"claude-artifact\"` and follow what it returns. Publish again after each round of feedback you apply; it goes to the same artifact. Give the link once, then just say the preview was updated.\n\u003C!-- \u002Fclaude-only -->\n","\u003C!-- generated:curated-entry -->\n\nExplore several deliberately different design directions with Open Design, compare them side by side, and take the chosen one forward.\n\nBrief: \"$ARGUMENTS\" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: \"What should we explore directions for?\")\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. Plan the directions\n\nIf the brief is empty, ask the user what to design before doing anything else.\n\nCall `list_open_design_skills` to find the skill that fits what's being designed (a landing page, a deck, a dashboard…). Then call `prepare_open_design_exploration` with that `skillId` and the brief:\n\n- `count`: the number of directions the user asked for (2–4). Default 3.\n- If the user named what should vary (\"three hero concepts\", \"different pricing layouts\"), pass `axis: \"custom\"` and `customDirections`, one `{ label, brief }` per direction.\n- Otherwise leave `axis` out. The tool picks visual styles when no design system is active, and layout or narrative structures when one is, so the brand is kept.\n- Pass `directionIds` only when the brief's tone clearly calls for specific directions, e.g. `editorial-monocle` for a magazine or `brutalist-experimental` for an art or agency site.\n\nIf the result says the active design system was set aside, tell the user.\n\n## 2. Generate each direction\n\nFor each direction in the result, follow `sharedInstructions` followed by that direction's own `instructions`. Write its file at exactly its `suggestedEntryPath`, then call `register_open_design_artifact` with the `explorationId`, the direction's `directionId`, kind, title and `sourceSkillId`.\n\nThese are **sketches**: one screen, or a cover plus two slides for a deck. Divergence matters more than polish. If you can delegate to sub-agents, generate the directions in parallel and give each one `sharedInstructions` plus its own `instructions`.\n\n## 3. Compare\n\nCall `compare_open_design_exploration` with `contactSheet: true`. If you can view images, open the contact sheet and check that the directions look clearly different (layout and hero pattern, not just colour). Regenerate any direction that resembles another, then compare again.\n\n## 4. Present\n\nGive the user the comparison page path (it opens in any browser straight from the file system and shows every direction side by side), and the contact sheet path if one was made. In one line each, say how the directions differ. Ask which one to take forward, and whether to:\n\n- **build it out** at full fidelity,\n- **merge** in parts of another direction (\"B, with A's hero\"), or\n- **save it as a design system** for later work.\n\n\u003C!-- claude-only -->\n**In Claude Desktop Chat**, call `show_open_design_artifact` with the `explorationId` to show the directions side by side, and where `show_open_design_questions` is in your tool list, ask the choice through it instead of a chat message: a `direction` question with one option per direction (`imageRef: \"artifact:\u003Cits entryPath>\"`), a `next` question (Build it out, Merge in parts of another, Save as a design system) and a short `text` question for anything to change or take from another direction. Read the `\u003C!-- od-answers {...} -->` line of the reply (`you-pick` means choose for them), then go on to step 5. If the user types their answer or taps \"Take this one\" instead, use that.\n\u003C!-- \u002Fclaude-only -->\n\n## 5. Take the choice forward\n\nCall `choose_open_design_direction` with the `explorationId`, the chosen `directionId`, `next` (`build-out`, `merge` with `mergeFrom`, or `save-design-system`) and the user's own adjustments as `notes`. Follow the returned `instructions` and register the result as they say.\n\n\u003C!-- claude-only -->\n**Artifact preview.** If you have an Artifact tool, publish the result as its private artifact preview (the built-out design, not the sketches) once it's registered: call `publish_open_design_artifact` with `provider: \"claude-artifact\"` and follow what it returns. Publish again after each round of feedback you apply; it goes to the same artifact. Give the link once, then just say the preview was updated.\n\u003C!-- \u002Fclaude-only -->\n",{"name":5,"description":7,"argument-hint":24},"what to design, and optionally how many directions or what should vary (e.g. \"pricing page, 3 directions\")","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-explore",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-explore",{"tool":39,"command":40},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-explore",{"tool":42,"command":43},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-explore","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-explore\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",[],[]]