[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DCZJ6981JA9K8KSAGSBCXM":3,"skill-same:01M7DCZJ6981JA9K8KSAGSBCXM":85},{"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":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M7DCZJ6981JA9K8KSAGSBCXM","diagram",null,"Designed diagrams of real systems — architecture, flowchart, entity-relationship, state machine or sequence — drawn from the code you read, laid out by the browser and styled by the active design system.","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\u002Fdiagram\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: diagram\nzh_name: \"代码图表\"\nen_name: \"Diagram\"\nemoji: \"🧭\"\ndescription: \"Designed diagrams of real systems — architecture, flowchart, entity-relationship, state machine or sequence — drawn from the code you read, laid out by the browser and styled by the active design system.\"\nzh_description: \"根据真实代码绘制的架构图、流程图、ER 图、状态图和时序图, 由浏览器排版, 使用当前设计系统的样式\"\nen_description: \"Designed diagrams of real systems — architecture, flowchart, entity-relationship, state machine or sequence — drawn from the code you read, laid out by the browser and styled by the active design system.\"\ncategory: diagram\nscenario: engineering\ntags: [\"diagram\", \"architecture\", \"flowchart\", \"erd\", \"sequence\", \"state machine\", \"图表\", \"架构图\"]\ntriggers:\n  - \"diagram\"\n  - \"architecture diagram\"\n  - \"flowchart\"\n  - \"flow chart\"\n  - \"sequence diagram\"\n  - \"er diagram\"\n  - \"erd\"\n  - \"state machine\"\n  - \"system diagram\"\n  - \"how does this work\"\n  - \"架构图\"\n  - \"流程图\"\nod:\n  mode: prototype\n  craft:\n    requires:\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: \"Diagram how this repo's packages depend on each other: read each package.json and the imports, group the shared packages and the hosts, and mark build-time copies differently from runtime dependencies.\"\n---\n\n# Diagram\n\n**Intent.** One clear, designed diagram of a real system, true to the code, that someone can read in ten seconds. It is an HTML page: you write the content (nodes, links, groups) and the browser lays it out. Never hand-place coordinates.\n\n## 1. Read before you draw\n\nEvery node and link must come from something you read, never from what such systems usually look like.\n\n- **Architecture \u002F dependencies:** package manifests (`package.json`, `go.mod`, `Cargo.toml`, `pyproject.toml`), workspace config, import statements, service and deployment config (`docker-compose.yml`, Kubernetes manifests).\n- **Flowchart \u002F request flow:** the entry point and the functions it calls, route definitions, middleware, queue consumers.\n- **Entity-relationship:** schema files (`schema.prisma`, migrations, ORM models, `.sql`).\n- **State machine:** the reducer, state enum or transition table.\n- **Sequence:** one concrete call path, followed through the code in order.\n\nKeep the list of files you read: you register them as `sources`. If the user's question is broader than what you can read (another service's repo), say what you could see and draw only that.\n\n## 2. Decide the graph, then the grid\n\nPick **5–25 nodes**. Merge leaf details into their parent; split into two diagrams rather than drawing 40 boxes.\n\nEach node gets two small integers:\n- `data-rank`: its step along the flow direction (1 = first). Sources, entry points or foundations come first; things that depend on or are called by earlier nodes come later.\n- `data-lane`: its position across the flow (1 = top for `right`, left for `down`). **Order lanes so linked nodes sit next to each other**: that is what keeps links short and off other nodes. Two nodes may not share the same rank and lane.\n\nDirection: `right` for flows and dependency graphs (wide screens), `down` for hierarchies and state machines with long chains.\n\nGroups (`data-group`) mark real boundaries: a package set, a process, a network zone, a team. Members of one group should occupy a contiguous block of ranks and lanes, or the group's box will cover other nodes.\n\n## 3. Write the page\n\nOne self-contained HTML file: a title, an optional one-line subtitle saying what the diagram shows and as of when (commit or date), the diagram, a small legend when you use more than one link style, and a **Sources** footer listing the files you read.\n\n```html\n\u003Cdiv data-od-diagram data-direction=\"right\">\n  \u003Cdiv class=\"node\" data-od-node=\"api\" data-rank=\"2\" data-lane=\"1\" data-group=\"backend\" data-od-source=\"services\u002Fapi\u002Fpackage.json\">\n    \u003Cstrong>api\u003C\u002Fstrong>\u003Csmall>Express, REST\u003C\u002Fsmall>\n  \u003C\u002Fdiv>\n  …\n  \u003Ci data-od-group=\"backend\" data-label=\"Backend\" hidden>\u003C\u002Fi>\n  \u003Ci data-od-link data-from=\"web\" data-to=\"api\" data-label=\"HTTPS\" hidden>\u003C\u002Fi>\n  \u003Ci data-od-link data-from=\"api\" data-to=\"queue\" data-style=\"dashed\" hidden>\u003C\u002Fi>\n\u003C\u002Fdiv>\n```\n\n- Node content is yours: a name, optionally a one-line role, an icon drawn in inline SVG. Keep labels short (2–4 words); widths stay similar across a rank.\n- Link labels only where they add information (protocol, event name, cardinality). Use `data-style=\"dashed\"` for a second kind of link (async, optional, build-time) and explain it in the legend.\n- **Entity-relationship:** each table is a node whose content lists its key columns (primary key first, foreign keys marked); links carry the cardinality as their label (`1 — n`).\n- **State machine:** states are nodes (the initial state at rank 1), transitions are links labelled with the event; use `direction=\"down\"` when there are more than 5 states in a row.\n- **Sequence:** `\u003Cdiv data-od-diagram=\"sequence\">` with participants (`data-od-participant`, in order left to right) and messages in order (`\u003Ci data-od-message data-from data-to data-label hidden>`, `data-kind=\"return\"` for replies). Use 3–6 participants and at most 15 messages.\n\nStyle from the active design system: node background from `--surface`, border from `--border`, text from `--fg`, secondary text from `--muted`, one emphasised node at most with `--accent`. Set the link and group look on the container with the runtime's custom properties (`--od-edge-color`, `--od-edge-width`, `--od-group-border`, `--od-group-bg`, `--od-rank-gap`, `--od-lane-gap`). Don't style the generated SVG or labels any other way.\n\n## 4. Add the runtime, register, check\n\n1. Call `add_open_design_diagram_runtime` with the entry path. It inserts the layout runtime into the file. Never write, copy or edit that `\u003Cscript data-od-runtime=\"diagram\">` block yourself.\n2. Call `register_open_design_artifact` with kind `diagram`, the title, and `sources` set to the files you read in step 1.\n3. Call `check_open_design_artifact`. Fix every `diagram-error` (unknown ids, missing rank or lane). For `edge-through-node`, `node-overlap` or `group-overlap`, reorder lanes or ranks rather than nudging anything with CSS. Look at the screenshot: the main path should read left to right (or top to bottom) without the eye jumping back.\n\nWhen `stale-sources` is reported later, offer to redraw from the changed files.\n","# Diagram\n\n**Intent.** One clear, designed diagram of a real system, true to the code, that someone can read in ten seconds. It is an HTML page: you write the content (nodes, links, groups) and the browser lays it out. Never hand-place coordinates.\n\n## 1. Read before you draw\n\nEvery node and link must come from something you read, never from what such systems usually look like.\n\n- **Architecture \u002F dependencies:** package manifests (`package.json`, `go.mod`, `Cargo.toml`, `pyproject.toml`), workspace config, import statements, service and deployment config (`docker-compose.yml`, Kubernetes manifests).\n- **Flowchart \u002F request flow:** the entry point and the functions it calls, route definitions, middleware, queue consumers.\n- **Entity-relationship:** schema files (`schema.prisma`, migrations, ORM models, `.sql`).\n- **State machine:** the reducer, state enum or transition table.\n- **Sequence:** one concrete call path, followed through the code in order.\n\nKeep the list of files you read: you register them as `sources`. If the user's question is broader than what you can read (another service's repo), say what you could see and draw only that.\n\n## 2. Decide the graph, then the grid\n\nPick **5–25 nodes**. Merge leaf details into their parent; split into two diagrams rather than drawing 40 boxes.\n\nEach node gets two small integers:\n- `data-rank`: its step along the flow direction (1 = first). Sources, entry points or foundations come first; things that depend on or are called by earlier nodes come later.\n- `data-lane`: its position across the flow (1 = top for `right`, left for `down`). **Order lanes so linked nodes sit next to each other**: that is what keeps links short and off other nodes. Two nodes may not share the same rank and lane.\n\nDirection: `right` for flows and dependency graphs (wide screens), `down` for hierarchies and state machines with long chains.\n\nGroups (`data-group`) mark real boundaries: a package set, a process, a network zone, a team. Members of one group should occupy a contiguous block of ranks and lanes, or the group's box will cover other nodes.\n\n## 3. Write the page\n\nOne self-contained HTML file: a title, an optional one-line subtitle saying what the diagram shows and as of when (commit or date), the diagram, a small legend when you use more than one link style, and a **Sources** footer listing the files you read.\n\n```html\n\u003Cdiv data-od-diagram data-direction=\"right\">\n  \u003Cdiv class=\"node\" data-od-node=\"api\" data-rank=\"2\" data-lane=\"1\" data-group=\"backend\" data-od-source=\"services\u002Fapi\u002Fpackage.json\">\n    \u003Cstrong>api\u003C\u002Fstrong>\u003Csmall>Express, REST\u003C\u002Fsmall>\n  \u003C\u002Fdiv>\n  …\n  \u003Ci data-od-group=\"backend\" data-label=\"Backend\" hidden>\u003C\u002Fi>\n  \u003Ci data-od-link data-from=\"web\" data-to=\"api\" data-label=\"HTTPS\" hidden>\u003C\u002Fi>\n  \u003Ci data-od-link data-from=\"api\" data-to=\"queue\" data-style=\"dashed\" hidden>\u003C\u002Fi>\n\u003C\u002Fdiv>\n```\n\n- Node content is yours: a name, optionally a one-line role, an icon drawn in inline SVG. Keep labels short (2–4 words); widths stay similar across a rank.\n- Link labels only where they add information (protocol, event name, cardinality). Use `data-style=\"dashed\"` for a second kind of link (async, optional, build-time) and explain it in the legend.\n- **Entity-relationship:** each table is a node whose content lists its key columns (primary key first, foreign keys marked); links carry the cardinality as their label (`1 — n`).\n- **State machine:** states are nodes (the initial state at rank 1), transitions are links labelled with the event; use `direction=\"down\"` when there are more than 5 states in a row.\n- **Sequence:** `\u003Cdiv data-od-diagram=\"sequence\">` with participants (`data-od-participant`, in order left to right) and messages in order (`\u003Ci data-od-message data-from data-to data-label hidden>`, `data-kind=\"return\"` for replies). Use 3–6 participants and at most 15 messages.\n\nStyle from the active design system: node background from `--surface`, border from `--border`, text from `--fg`, secondary text from `--muted`, one emphasised node at most with `--accent`. Set the link and group look on the container with the runtime's custom properties (`--od-edge-color`, `--od-edge-width`, `--od-group-border`, `--od-group-bg`, `--od-rank-gap`, `--od-lane-gap`). Don't style the generated SVG or labels any other way.\n\n## 4. Add the runtime, register, check\n\n1. Call `add_open_design_diagram_runtime` with the entry path. It inserts the layout runtime into the file. Never write, copy or edit that `\u003Cscript data-od-runtime=\"diagram\">` block yourself.\n2. Call `register_open_design_artifact` with kind `diagram`, the title, and `sources` set to the files you read in step 1.\n3. Call `check_open_design_artifact`. Fix every `diagram-error` (unknown ids, missing rank or lane). For `edge-through-node`, `node-overlap` or `group-overlap`, reorder lanes or ranks rather than nudging anything with CSS. Look at the screenshot: the main path should read left to right (or top to bottom) without the eye jumping back.\n\nWhen `stale-sources` is reported later, offer to redraw from the changed files.\n",{"od":24,"name":5,"tags":37,"emoji":45,"en_name":46,"zh_name":47,"category":5,"scenario":34,"triggers":48,"description":7,"en_description":7,"zh_description":56},{"mode":25,"craft":26,"preview":30,"platform":33,"scenario":34,"design_system":35,"example_prompt":36},"prototype",{"requires":27},[28,29],"color","accessibility-baseline",{"type":31,"entry":32},"html","index.html","desktop","engineering",{"requires":20},"Diagram how this repo's packages depend on each other: read each package.json and the imports, group the shared packages and the hosts, and mark build-time copies differently from runtime dependencies.",[5,38,39,40,41,42,43,44],"architecture","flowchart","erd","sequence","state machine","图表","架构图","🧭","Diagram","代码图表",[5,49,39,50,51,52,40,42,53,54,44,55],"architecture diagram","flow chart","sequence diagram","er diagram","system diagram","how does this work","流程图","根据真实代码绘制的架构图、流程图、ER 图、状态图和时序图, 由浏览器排版, 使用当前设计系统的样式","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fdiagram",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill diagram",{"tool":71,"command":72},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill diagram",{"tool":74,"command":75},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill diagram","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fdiagram\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},".od-local-overlay","OTHER","其他",82,"https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fvscode\u002Fassets\u002Fopen-design\u002Fskills\u002Fdiagram\u002F.od-local-overlay",[86,93,100,107,114,121],{"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},"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":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},"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":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},"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":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},"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":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},"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"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",[],[]]