[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78AKKXAVMTGAZG6C0GD4EFP":3,"skill-same:01M78AKKXAVMTGAZG6C0GD4EFP":102},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":73,"commitSha":74,"skillDirectory":75,"forksCount":13,"repositoryHtmlUrl":76,"repositoryHomepageUrl":77,"ownerHtmlUrl":78,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":79,"install":80,"resources":92},"01M78AKKXAVMTGAZG6C0GD4EFP","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.","bluesman1971\u002Fopen-design","bluesman1971","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96430007?v=4","01M788AK0TR13JE8ART2WNQZV6","01M788AK1PVB085AS9SP38WWGK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\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 Open Design'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 Open Design'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":23,"name":5,"en_name":61,"zh_name":62,"triggers":63,"description":72},{"mode":24,"craft":25,"inputs":30,"outputs":36,"preview":42,"category":44,"platform":45,"scenario":46,"design_system":47,"example_prompt":56,"example_prompt_i18n":57,"capabilities_required":59},"design-system",{"requires":26},[27,28,29],"typography","color","anti-ai-slop",[31],{"name":32,"type":33,"required":34,"description":35},"brief","string",true,"Goal, audience, references, or the style problem to resolve",{"primary":37,"secondary":38},"DESIGN.md",[39,40,41],"design-contract.md","implementation-handoff.md","example.html",{"type":43,"entry":41},"html","design-systems","desktop","planning",{"requires":19,"sections":48,"generates":34},[49,28,27,50,51,52,53,54,55],"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":58},"为一个开发者笔记应用创建「参考转设计合约」。方向要有编辑感、安静、触感强、认真，但不要照抄任何具体产品。输出 DESIGN.md 和实现交接说明。",[60],"file_write","Reference Design Contract","参考转设计合约",[64,65,66,67,68,69,70,71],"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","0467f0e19df12a6994ec7fb20ff6e9e23cd704e7","skills\u002Freference-design-contract","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design","https:\u002F\u002Fopen-design.ai","https:\u002F\u002Fgithub.com\u002Fbluesman1971","2026-07-09 04:08:20",{"source":8,"skillName":5,"commands":81,"prompt":91,"zipAvailable":34},[82,85,88],{"tool":83,"command":84},"npx","npx skills add bluesman1971\u002Fopen-design --skill reference-design-contract",{"tool":86,"command":87},"bunx","bunx skills add bluesman1971\u002Fopen-design --skill reference-design-contract",{"tool":89,"command":90},"pnpm","pnpm dlx skills add bluesman1971\u002Fopen-design --skill reference-design-contract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Freference-design-contract\u002FSKILL.md",[93,98],{"path":41,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"REFERENCE","参考文档",5848,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Freference-design-contract\u002Fexample.html",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fchecklist.md",1135,"https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Freference-design-contract\u002Freferences\u002Fchecklist.md",[103,112,120,127,134,141],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M78AMRG8NAGKWKNDQE39ZZFQ","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.","MIT","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M78AMKHTFS149JGEYNQM5AXR","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\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-clone\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fweb-clone\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":18},"01M78AMH25JH2SH3AWTRSDCM9F","venice-video","Video generation and transcription workflows via the Venice.ai API.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fvenice-video\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":18},"01M78AMF0M4FFKFWXFJ9NHTF5M","venice-image-generate","Image generation endpoints and available styles via the Venice.ai API.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fvenice-image-generate\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":18},"01M78AMCH68X46SHNZVD284KXS","threejs","Three.js skills for creating 3D elements and interactive experiences in the browser — scenes, materials, controls, and post-processing.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Fthreejs\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":18},"01M78AM7P8WSBZDNZZ42BQHGK7","taste","Brief-time anti-AI-slop taste checklist — read the room and set the\ndesign dials BEFORE generating a landing page, portfolio, or redesign,\nso the first draft doesn't need a post-generation rescue. Use at the\nstart of a visual\u002Fcreative brief, not after the artifact exists.","https:\u002F\u002Fgithub.com\u002Fbluesman1971\u002Fopen-design\u002Fblob\u002Fmain\u002Fskills\u002Ftaste\u002FSKILL.md",[],[]]