[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7WG24PR060MC0CTSFKVWQ":3,"skill-same:01M7D7WG24PR060MC0CTSFKVWQ":78},{"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":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M7D7WG24PR060MC0CTSFKVWQ","adr",null,"An architecture decision record: context, the decision, its consequences and status, with links to the records it supersedes or is superseded by.","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\u002Fcontent\u002Fassets\u002Fopen-design\u002Fskills\u002Fadr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: adr\nzh_name: \"架构决策记录 ADR\"\nen_name: \"ADR\"\nemoji: \"🧭\"\ndescription: \"An architecture decision record: context, the decision, its consequences and status, with links to the records it supersedes or is superseded by.\"\nen_description: \"An architecture decision record: context, the decision, its consequences and status, with links to the records it supersedes or is superseded by.\"\ncategory: doc\nscenario: engineering\ntags: [\"adr\", \"architecture decision\", \"decision record\", \"engineering\", \"架构决策\"]\ntriggers:\n  - \"adr\"\n  - \"architecture decision record\"\n  - \"decision record\"\n  - \"record this decision\"\n  - \"架构决策\"\nod:\n  mode: prototype\n  craft:\n    requires:\n      - typography\n      - typography-hierarchy\n      - color\n      - accessibility-baseline\n  platform: desktop\n  scenario: engineering\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: false\n  example_prompt: \"Write an ADR for the decision to lay diagrams out in the browser with CSS grid instead of a graph-layout library: context, decision, options considered, consequences and status.\"\n---\n\n# ADR\n\n**Intent.** A short, permanent record of one decision, read months later by someone asking why the system is the way it is. One decision per record.\n\n## Ground it\n\nWrite only what the sources say. Gather them yourself before writing a word:\n\n- the code that embodies the decision, and the discussion behind it (issues, PRs, design docs the user names);\n- existing ADRs in the repo (`docs\u002Fadr\u002F`, `docs\u002Fdecisions\u002F`, `adr\u002F`): match their numbering and find the ones this supersedes.\n\nKeep the list of files, commits and refs you read: they go in a **Sources** section at the bottom of the page and in `sources` when you register (`register_open_design_artifact` with kind `html`). If something the document needs isn't in the sources, ask the user, or mark it plainly as an open question. Never invent numbers, dates, names or quotes.\n\n## Structure\n\n1. **Header:** `ADR-\u003CNNNN>: \u003Cthe decision as a short statement>`, date, deciders if known, and a status banner `\u003Cp class=\"status\" data-od-status=\"proposed|accepted|deprecated|superseded\">…\u003C\u002Fp>`. If it supersedes or is superseded by another ADR, link both ways (`Supersedes ADR-0003`, `Superseded by ADR-0012`).\n2. **Context:** the forces at play: constraints, requirements, what was tried. Neutral and factual.\n3. **Decision:** one paragraph in the active voice: \"We will …\".\n4. **Options considered:** a compact table: option, pros, cons, and why it lost or won.\n5. **Consequences:** positive, negative and neutral, as three short lists. Be honest about the costs.\n6. **Sources.**\n\nKeep it to one or two screens. An ADR isn't a design doc.\n\n## Design\n\n- One readable column (`max-width` 720–780px), body 16–17px with line-height 1.55–1.65, generous space between sections. It must read well on a phone: tables sit in an `overflow-x: auto` wrapper, nothing has a fixed width wider than the screen.\n- Style from the active design system (`--bg`, `--surface`, `--fg`, `--muted`, `--border`, `--accent`); status colours are the only extra colours (green for accepted\u002Fdone, amber for proposed\u002Fin progress, red for rejected\u002Fhigh severity, grey for superseded).\n- Headings are short labels; the content does the talking. Code, paths and commands in a monospace face, with `overflow-wrap: anywhere` so long paths wrap on phones.\n- Finish with `check_open_design_artifact` and fix every error at desktop and mobile width.\n","# ADR\n\n**Intent.** A short, permanent record of one decision, read months later by someone asking why the system is the way it is. One decision per record.\n\n## Ground it\n\nWrite only what the sources say. Gather them yourself before writing a word:\n\n- the code that embodies the decision, and the discussion behind it (issues, PRs, design docs the user names);\n- existing ADRs in the repo (`docs\u002Fadr\u002F`, `docs\u002Fdecisions\u002F`, `adr\u002F`): match their numbering and find the ones this supersedes.\n\nKeep the list of files, commits and refs you read: they go in a **Sources** section at the bottom of the page and in `sources` when you register (`register_open_design_artifact` with kind `html`). If something the document needs isn't in the sources, ask the user, or mark it plainly as an open question. Never invent numbers, dates, names or quotes.\n\n## Structure\n\n1. **Header:** `ADR-\u003CNNNN>: \u003Cthe decision as a short statement>`, date, deciders if known, and a status banner `\u003Cp class=\"status\" data-od-status=\"proposed|accepted|deprecated|superseded\">…\u003C\u002Fp>`. If it supersedes or is superseded by another ADR, link both ways (`Supersedes ADR-0003`, `Superseded by ADR-0012`).\n2. **Context:** the forces at play: constraints, requirements, what was tried. Neutral and factual.\n3. **Decision:** one paragraph in the active voice: \"We will …\".\n4. **Options considered:** a compact table: option, pros, cons, and why it lost or won.\n5. **Consequences:** positive, negative and neutral, as three short lists. Be honest about the costs.\n6. **Sources.**\n\nKeep it to one or two screens. An ADR isn't a design doc.\n\n## Design\n\n- One readable column (`max-width` 720–780px), body 16–17px with line-height 1.55–1.65, generous space between sections. It must read well on a phone: tables sit in an `overflow-x: auto` wrapper, nothing has a fixed width wider than the screen.\n- Style from the active design system (`--bg`, `--surface`, `--fg`, `--muted`, `--border`, `--accent`); status colours are the only extra colours (green for accepted\u002Fdone, amber for proposed\u002Fin progress, red for rejected\u002Fhigh severity, grey for superseded).\n- Headings are short labels; the content does the talking. Code, paths and commands in a monospace face, with `overflow-wrap: anywhere` so long paths wrap on phones.\n- Finish with `check_open_design_artifact` and fix every error at desktop and mobile width.\n",{"od":24,"name":5,"tags":39,"emoji":43,"en_name":44,"zh_name":45,"category":46,"scenario":36,"triggers":47,"description":7,"en_description":7},{"mode":25,"craft":26,"preview":32,"platform":35,"scenario":36,"design_system":37,"example_prompt":38},"prototype",{"requires":27},[28,29,30,31],"typography","typography-hierarchy","color","accessibility-baseline",{"type":33,"entry":34},"html","index.html","desktop","engineering",{"requires":20},"Write an ADR for the decision to lay diagrams out in the browser with CSS grid instead of a graph-layout library: context, decision, options considered, consequences and status.",[5,40,41,36,42],"architecture decision","decision record","架构决策","🧭","ADR","架构决策记录 ADR","doc",[5,48,41,49,42],"architecture decision record","record this decision","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fskills\u002Fadr",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill adr",{"tool":64,"command":65},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill adr",{"tool":67,"command":68},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill adr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fskills\u002Fadr\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},".od-local-overlay","OTHER","其他",82,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fskills\u002Fadr\u002F.od-local-overlay",[79,86,93,100,107,114],{"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},"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":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},"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":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},"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":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},"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":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},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"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",[],[]]