[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DDH8ZEP0TNJZ4EVZFKNDFK":3,"skill-same:01M7DDH8ZEP0TNJZ4EVZFKNDFK":95},{"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":74,"commitSha":75,"skillDirectory":76,"forksCount":77,"repositoryHtmlUrl":78,"repositoryHomepageUrl":79,"ownerHtmlUrl":80,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":81,"install":82,"resources":94},"01M7DDH8ZEP0TNJZ4EVZFKNDFK","reference-design-contract",null,"Turn vague taste, screenshots, URLs, product notes, or \"make it feel like this\"\nreferences into a grounded DESIGN.md plus an implementation handoff. Use it\nbefore prototypes, decks, redesigns, or image remix work when the user needs\na reusable visual direction rather than a one-off prompt.","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\u002Fskills\u002Freference-design-contract\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: reference-design-contract\nzh_name: \"参考转设计合约\"\nen_name: \"Reference Design Contract\"\ndescription: |\n  Turn vague taste, screenshots, URLs, product notes, or \"make it feel like this\"\n  references into a grounded DESIGN.md plus an implementation handoff. Use it\n  before prototypes, decks, redesigns, or image remix work when the user needs\n  a reusable visual direction rather than a one-off prompt.\ntriggers:\n  - \"design contract\"\n  - \"reference design brief\"\n  - \"style contract\"\n  - \"visual direction handoff\"\n  - \"turn references into DESIGN.md\"\n  - \"make it feel like this\"\n  - \"做同款但不照抄\"\n  - \"把参考图转成设计规范\"\nod:\n  mode: design-system\n  platform: desktop\n  scenario: planning\n  category: design-systems\n  preview:\n    type: html\n    entry: example.html\n  design_system:\n    requires: false\n    generates: true\n    sections: [visual-theme, color, typography, spacing, layout, components, motion, voice, anti-patterns]\n  craft:\n    requires:\n      - typography\n      - color\n      - anti-ai-slop\n  inputs:\n    - name: brief\n      type: string\n      required: true\n      description: \"Goal, audience, references, or the style problem to resolve\"\n  outputs:\n    primary: DESIGN.md\n    secondary:\n      - design-contract.md\n      - implementation-handoff.md\n      - example.html\n  capabilities_required:\n    - file_write\n  example_prompt: \"Create a reference design contract for a developer-notes app. The direction should feel editorial, calm, tactile, and serious, but not copy any specific product. Produce DESIGN.md and an implementation handoff.\"\n  example_prompt_i18n:\n    zh-CN: \"为一个开发者笔记应用创建「参考转设计合约」。方向要有编辑感、安静、触感强、认真，但不要照抄任何具体产品。输出 DESIGN.md 和实现交接说明。\"\n---\n\n# Reference Design Contract\n\nUse this skill when the user has taste signals, references, or a rough \"like\nthis\" request and needs a reusable design contract before generation. The goal\nis not to write a longer prompt. The goal is to make design decisions explicit\nenough that a later prototype, deck, redesign, or image-remix run can execute\nwithout guessing.\n\n## What this skill produces\n\nCreate three files:\n\n1. `DESIGN.md` — the reusable visual direction, following OpenDesign's\n   standard nine-section design-system shape.\n2. `design-contract.md` — the decision record: evidence used, keep\u002Fchange\n   boundaries, rationale, risks, and quality gate.\n3. `implementation-handoff.md` — concise build instructions for the next\n   artifact-producing skill or coding agent.\n\nIf a preview is useful, also create `example.html` as a small hand-built\ncontract preview. Do not make it the main deliverable.\n\n## Workflow\n\n1. **Lock the job.** Identify target artifact type, audience, brand\u002Fproduct\n   context, references, and constraints. Ask at most two questions only when a\n   missing answer would change the direction. Otherwise choose a sensible\n   default and label it as inferred.\n2. **Read evidence.** Use provided screenshots, URLs, existing `DESIGN.md`,\n   brand docs, image artifacts, or user notes. If evidence is missing, say so\n   and base the contract on the brief only; do not invent brand facts.\n3. **Separate reference semantics.** For every reference, split it into:\n   - `Keep`: qualities to preserve, such as density, composition, material,\n     typography rhythm, color temperature, or motion attitude.\n   - `Change`: subject matter, copy, brand marks, exact layout, protected\n     assets, and anything the user wants adapted.\n   - `Do not copy`: literal screenshots, logos, claims, pricing, proprietary\n     UI, or exact prompt wording from examples.\n4. **Freeze the direction.** Choose one coherent visual stance. Do not provide\n   five unrelated moodboards. If there are genuinely competing directions,\n   name them briefly, pick the recommended one, and continue.\n5. **Write `DESIGN.md`.** Use these nine headings exactly:\n   - `## 1. Visual Theme & Atmosphere`\n   - `## 2. Color`\n   - `## 3. Typography`\n   - `## 4. Spacing & Grid`\n   - `## 5. Layout & Composition`\n   - `## 6. Components`\n   - `## 7. Motion & Interaction`\n   - `## 8. Voice & Brand`\n   - `## 9. Anti-patterns`\n6. **Write `design-contract.md`.** Include:\n   - goal and target artifact\n   - evidence table with confidence (`observed`, `provided`, `inferred`)\n   - keep\u002Fchange\u002Fdo-not-copy table\n   - final design stance in one paragraph\n   - risks and explicit unknowns\n   - quality gate checklist\n7. **Write `implementation-handoff.md`.** Keep it short and operational:\n   - files to read\n   - token\u002Fpalette\u002Ftype\u002Flayout constraints\n   - asset rules\n   - responsive requirements\n   - \"first artifact should prove...\" acceptance notes\n8. **Validate.** Read `references\u002Fchecklist.md` and satisfy every P0 gate\n   before final handoff.\n\n## Output rules\n\n- Make every claim traceable to user input, observed reference evidence, or an\n  explicitly labeled inference.\n- Prefer concrete constraints over adjectives: \"one warm accent, no purple or\n  blue glow\" beats \"premium\".\n- Treat \"do the same style\" as \"borrow controllable qualities\", not \"clone the\n  original subject or prompt\".\n- If the user asks for immediate UI generation too, finish these contract files\n  first, then hand off to the appropriate artifact skill in the next step.\n","# Reference Design Contract\n\nUse this skill when the user has taste signals, references, or a rough \"like\nthis\" request and needs a reusable design contract before generation. The goal\nis not to write a longer prompt. The goal is to make design decisions explicit\nenough that a later prototype, deck, redesign, or image-remix run can execute\nwithout guessing.\n\n## What this skill produces\n\nCreate three files:\n\n1. `DESIGN.md` — the reusable visual direction, following OpenDesign's\n   standard nine-section design-system shape.\n2. `design-contract.md` — the decision record: evidence used, keep\u002Fchange\n   boundaries, rationale, risks, and quality gate.\n3. `implementation-handoff.md` — concise build instructions for the next\n   artifact-producing skill or coding agent.\n\nIf a preview is useful, also create `example.html` as a small hand-built\ncontract preview. Do not make it the main deliverable.\n\n## Workflow\n\n1. **Lock the job.** Identify target artifact type, audience, brand\u002Fproduct\n   context, references, and constraints. Ask at most two questions only when a\n   missing answer would change the direction. Otherwise choose a sensible\n   default and label it as inferred.\n2. **Read evidence.** Use provided screenshots, URLs, existing `DESIGN.md`,\n   brand docs, image artifacts, or user notes. If evidence is missing, say so\n   and base the contract on the brief only; do not invent brand facts.\n3. **Separate reference semantics.** For every reference, split it into:\n   - `Keep`: qualities to preserve, such as density, composition, material,\n     typography rhythm, color temperature, or motion attitude.\n   - `Change`: subject matter, copy, brand marks, exact layout, protected\n     assets, and anything the user wants adapted.\n   - `Do not copy`: literal screenshots, logos, claims, pricing, proprietary\n     UI, or exact prompt wording from examples.\n4. **Freeze the direction.** Choose one coherent visual stance. Do not provide\n   five unrelated moodboards. If there are genuinely competing directions,\n   name them briefly, pick the recommended one, and continue.\n5. **Write `DESIGN.md`.** Use these nine headings exactly:\n   - `## 1. Visual Theme & Atmosphere`\n   - `## 2. Color`\n   - `## 3. Typography`\n   - `## 4. Spacing & Grid`\n   - `## 5. Layout & Composition`\n   - `## 6. Components`\n   - `## 7. Motion & Interaction`\n   - `## 8. Voice & Brand`\n   - `## 9. Anti-patterns`\n6. **Write `design-contract.md`.** Include:\n   - goal and target artifact\n   - evidence table with confidence (`observed`, `provided`, `inferred`)\n   - keep\u002Fchange\u002Fdo-not-copy table\n   - final design stance in one paragraph\n   - risks and explicit unknowns\n   - quality gate checklist\n7. **Write `implementation-handoff.md`.** Keep it short and operational:\n   - files to read\n   - token\u002Fpalette\u002Ftype\u002Flayout constraints\n   - asset rules\n   - responsive requirements\n   - \"first artifact should prove...\" acceptance notes\n8. **Validate.** Read `references\u002Fchecklist.md` and satisfy every P0 gate\n   before final handoff.\n\n## Output rules\n\n- Make every claim traceable to user input, observed reference evidence, or an\n  explicitly labeled inference.\n- Prefer concrete constraints over adjectives: \"one warm accent, no purple or\n  blue glow\" beats \"premium\".\n- Treat \"do the same style\" as \"borrow controllable qualities\", not \"clone the\n  original subject or prompt\".\n- If the user asks for immediate UI generation too, finish these contract files\n  first, then hand off to the appropriate artifact skill in the next step.\n",{"od":24,"name":5,"en_name":62,"zh_name":63,"triggers":64,"description":73},{"mode":25,"craft":26,"inputs":31,"outputs":37,"preview":43,"category":45,"platform":46,"scenario":47,"design_system":48,"example_prompt":57,"example_prompt_i18n":58,"capabilities_required":60},"design-system",{"requires":27},[28,29,30],"typography","color","anti-ai-slop",[32],{"name":33,"type":34,"required":35,"description":36},"brief","string",true,"Goal, audience, references, or the style problem to resolve",{"primary":38,"secondary":39},"DESIGN.md",[40,41,42],"design-contract.md","implementation-handoff.md","example.html",{"type":44,"entry":42},"html","design-systems","desktop","planning",{"requires":20,"sections":49,"generates":35},[50,29,28,51,52,53,54,55,56],"visual-theme","spacing","layout","components","motion","voice","anti-patterns","Create a reference design contract for a developer-notes app. The direction should feel editorial, calm, tactile, and serious, but not copy any specific product. Produce DESIGN.md and an implementation handoff.",{"zh-CN":59},"为一个开发者笔记应用创建「参考转设计合约」。方向要有编辑感、安静、触感强、认真，但不要照抄任何具体产品。输出 DESIGN.md 和实现交接说明。",[61],"file_write","Reference Design Contract","参考转设计合约",[65,66,67,68,69,70,71,72],"design contract","reference design brief","style contract","visual direction handoff","turn references into DESIGN.md","make it feel like this","做同款但不照抄","把参考图转成设计规范","Turn vague taste, screenshots, URLs, product notes, or \"make it feel like this\"\nreferences into a grounded DESIGN.md plus an implementation handoff. Use it\nbefore prototypes, decks, redesigns, or image remix work when the user needs\na reusable visual direction rather than a one-off prompt.\n","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Freference-design-contract",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":83,"prompt":93,"zipAvailable":35},[84,87,90],{"tool":85,"command":86},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill reference-design-contract",{"tool":88,"command":89},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill reference-design-contract",{"tool":91,"command":92},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill reference-design-contract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Freference-design-contract\u002FSKILL.md",[],[96,103,110,117,124,131],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"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",[],[]]