[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D883X5EG8BC929BT61TM00":3,"skill-same:01M7D883X5EG8BC929BT61TM00":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":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":78},"01M7D883X5EG8BC929BT61TM00","flow-ai-chat",null,"A linked AI assistant flow: empty chat with suggested prompts, a streaming reply, an error with retry, and a result the user acts on, as one collection.","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\u002Fflow-ai-chat\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: flow-ai-chat\nzh_name: \"AI 对话流程\"\nen_name: \"AI Chat Flow\"\nemoji: \"💬\"\ndescription: \"A linked AI assistant flow: empty chat with suggested prompts, a streaming reply, an error with retry, and a result the user acts on, as one collection.\"\nen_description: \"A linked AI assistant flow: empty chat with suggested prompts, a streaming reply, an error with retry, and a result the user acts on, as one collection.\"\ncategory: app\nscenario: design\ntags: [\"ai chat\", \"assistant\", \"chatbot\", \"copilot\", \"streaming\", \"AI 助手\", \"聊天\"]\ntriggers:\n  - \"ai chat\"\n  - \"chat screen\"\n  - \"assistant screen\"\n  - \"chatbot ui\"\n  - \"copilot ui\"\nod:\n  mode: prototype\n  craft:\n    requires:\n      - product-ui\n      - state-coverage\n      - action-states\n      - ux-writing\n  surface: web\n  platform: desktop\n  scenario: design\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: true\n  example_prompt: \"The AI assistant inside a travel-planning app: empty chat with suggestions, a streaming answer, a network error with retry, and an itinerary card the user can save.\"\n---\n\n\u003C!-- Kit skill (openspec add-app-screens). -->\n# AI Chat Flow\n\nA flow pack: one collection of linked screens, each with its branches, made in one ask. Build every screen from the app screen patterns' shell and rules (below), one artifact per screen.\n\n## Screens\n\n| Screen id | Title | What it holds |\n|---|---|---|\n| `chat-empty` | Ask anything | what the assistant can do here in one line; three or four suggested prompts from the brief's domain; the composer |\n| `chat-streaming` | Answering | the user message, the reply arriving with a visible \"Stop\" control and the composer locked |\n| `chat-error` | Something failed | the failed reply with a plain cause and \"Try again\"; the user's message kept |\n| `chat-result` | Result | the reply as a structured card the user can act on (save, share, edit); feedback controls; ends the flow |\n\nMain path: `chat-empty` → `chat-streaming` → `chat-error` → `chat-result`. Add the branches each screen lists as its own `data-od-state` frames or, when a branch is a whole screen, as a screen.\n\n## Workflow\n\n1. **Ask once, at most three questions, together:** which branches to include, which platform (web app, iPhone, Android), and the product name if the brief doesn't give it. Accept \"you pick\". Never more than eight screens.\n2. **Plan the flow before the first screen.** Pass `flow` to `prepare_open_design_brief` on every screen: the screens above (trimmed to the user's choice), the links between them (from, trigger label, to) and the shared navigation if the flow has one. Use the same `collectionId` and the screen id as `screenRole`.\n3. **Build each screen** with its own `prepare_open_design_brief` call, then register it with the same `collectionId`, `screenRole` and `flow`.\n4. **Check the collection** with `check_open_design_artifact` and `collectionId`, fix flow findings (broken links, dead ends, unfilled screens, navigation drift, store rules), then show the flow map.\n\n## Rules for this flow\n\n- Say what the assistant can't do and where its information comes from; show sources when it cites any.\n- Long replies keep the composer reachable; the newest message stays in view.\n- Mark the result screen with `data-od-end`.\n\n## Markup contract (shared by every app screen)\n\n- **States.** Each state of the screen is a sibling `\u003Csection data-od-state=\"…\">`: `default` (populated), and the ones this pattern lists below from `empty`, `loading`, `error`, `success`, `no-access`, `long-content`. Only `default` is visible; the others carry `hidden`. The kit's check renders every state, and the preview shows them side by side.\n- **Slots.** Keep the seed's `data-od-slot` names (`nav`, `toolbar`, `content`, `empty`, `loading`) so states, links and comments line up.\n- **Links between screens.** When this screen is part of a planned flow, link to another screen with its entry path in `href` and its screen id in `data-od-goto`, and use the shared navigation the brief gives instead of drawing your own.\n- **The app's own components.** When the brief lists the app's components, build each part from one of them and mark it `data-od-component=\"\u003CName>\"`; mark a part with no match `data-od-component=\"new:\u003CName>\"`.\n- **Sample data.** Records come from the data file the brief describes, never typed into the markup row by row: one template row or card with `data-od-repeat=\"\u003Clist>\"` and `data-od-bind=\".\u003Cfield>\"` inside it, single values with `data-od-bind=\"\u003Clist>[n].\u003Cfield>\"`, and `data-od-format` for money, dates and numbers. Every screen that shows the same record binds to the same one.\n- **Tokens only.** Every colour, size, radius and shadow comes from the design system's `:root` variables. No raw hex outside `:root`.\n- **Platform.** Web app: the shell as given. iPhone, Android, tablet or desktop app: put `data-od-device` on `\u003Cbody>` (`iphone`, `android`, `tablet` with `data-od-orientation`, or `desktop-app` with `data-od-window=\"mac\"` or `\"windows\"`); the kit draws the device frame, status bar and home indicator around the screen, so never draw them yourself. iPhone or Android: a single column 390 px (iPhone) or 412 px (Android) wide, with a bottom tab bar instead of the side nav, a top bar with the title and a back button on inner screens, and 44 px (iPhone) or 48 px (Android) touch targets. Android screens use Material patterns (top app bar, floating action button where there is one main create action). Tablet: the sidebar collapses to an icon rail with labels in a tooltip, content in two columns where the pattern has a detail pane.\n- **Density.** Use the density the brief gives (compact, medium or airy) with the numbers from the product UI craft rules.\n\n## Seed\n\nStart from this shell (one HTML file, inline CSS). Replace the comments; keep the structure.\n\n\u003C!-- od:app-shell:start -->\n```html\n\u003C!doctype html>\n\u003Chtml lang=\"en\">\n\u003Chead>\n\u003Cmeta charset=\"utf-8\">\n\u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n\u003Ctitle>Screen title · Product\u003C\u002Ftitle>\n\u003Cstyle>\n\u002F* Paste the active design system's :root block here, then use only var(--…). *\u002F\n*,*::before,*::after{box-sizing:border-box}\nbody{margin:0;background:var(--bg);color:var(--fg);font:var(--text-base)\u002Fvar(--leading-body) var(--font-body)}\n.app{display:grid;grid-template-columns:1fr;min-height:100dvh}\n.app-nav{display:flex;gap:var(--space-1);padding:var(--space-2) var(--space-4);border-bottom:1px solid var(--border);overflow-x:auto}\n.app-nav a{display:flex;align-items:center;gap:var(--space-2);min-height:44px;padding:0 var(--space-3);border-radius:var(--radius-md);color:var(--muted);text-decoration:none;white-space:nowrap}\n.app-nav a[aria-current=\"page\"]{background:var(--surface);color:var(--fg);box-shadow:var(--elev-ring)}\n.app-main{min-width:0;padding:var(--space-4)}\n.app-toolbar{display:flex;flex-wrap:wrap;align-items:center;gap:var(--space-3);margin-bottom:var(--space-4)}\n.app-toolbar h1{margin:0 auto 0 0;font:600 var(--text-xl)\u002Fvar(--leading-tight) var(--font-display)}\n[data-od-state][hidden]{display:none}\n@media (min-width:64rem){\n  .app{grid-template-columns:260px 1fr}\n  .app-nav{flex-direction:column;border-bottom:0;border-right:1px solid var(--border);padding:var(--space-4)}\n  .app-main{padding:var(--space-6) var(--space-8)}\n}\n\u003C\u002Fstyle>\n\u003C\u002Fhead>\n\u003Cbody>\n\u003Cdiv class=\"app\">\n  \u003Cnav class=\"app-nav\" aria-label=\"Main\" data-od-slot=\"nav\">\n    \u003Ca href=\"#\" aria-current=\"page\">Current place\u003C\u002Fa>\n    \u003Ca href=\"#\">Another place\u003C\u002Fa>\n  \u003C\u002Fnav>\n  \u003Cmain class=\"app-main\">\n    \u003Cheader class=\"app-toolbar\" data-od-slot=\"toolbar\">\n      \u003Ch1>Screen title\u003C\u002Fh1>\n    \u003C\u002Fheader>\n    \u003Csection data-od-state=\"default\" data-od-slot=\"content\">\u003C!-- the populated screen -->\u003C\u002Fsection>\n    \u003Csection data-od-state=\"empty\" data-od-slot=\"empty\" hidden>\u003C!-- what will be here, why it is empty, the first action -->\u003C\u002Fsection>\n    \u003Csection data-od-state=\"loading\" data-od-slot=\"loading\" hidden aria-busy=\"true\">\u003C!-- a skeleton shaped like the content -->\u003C\u002Fsection>\n  \u003C\u002Fmain>\n\u003C\u002Fdiv>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\u003C!-- od:app-shell:end -->\n","\u003C!-- Kit skill (openspec add-app-screens). -->\n# AI Chat Flow\n\nA flow pack: one collection of linked screens, each with its branches, made in one ask. Build every screen from the app screen patterns' shell and rules (below), one artifact per screen.\n\n## Screens\n\n| Screen id | Title | What it holds |\n|---|---|---|\n| `chat-empty` | Ask anything | what the assistant can do here in one line; three or four suggested prompts from the brief's domain; the composer |\n| `chat-streaming` | Answering | the user message, the reply arriving with a visible \"Stop\" control and the composer locked |\n| `chat-error` | Something failed | the failed reply with a plain cause and \"Try again\"; the user's message kept |\n| `chat-result` | Result | the reply as a structured card the user can act on (save, share, edit); feedback controls; ends the flow |\n\nMain path: `chat-empty` → `chat-streaming` → `chat-error` → `chat-result`. Add the branches each screen lists as its own `data-od-state` frames or, when a branch is a whole screen, as a screen.\n\n## Workflow\n\n1. **Ask once, at most three questions, together:** which branches to include, which platform (web app, iPhone, Android), and the product name if the brief doesn't give it. Accept \"you pick\". Never more than eight screens.\n2. **Plan the flow before the first screen.** Pass `flow` to `prepare_open_design_brief` on every screen: the screens above (trimmed to the user's choice), the links between them (from, trigger label, to) and the shared navigation if the flow has one. Use the same `collectionId` and the screen id as `screenRole`.\n3. **Build each screen** with its own `prepare_open_design_brief` call, then register it with the same `collectionId`, `screenRole` and `flow`.\n4. **Check the collection** with `check_open_design_artifact` and `collectionId`, fix flow findings (broken links, dead ends, unfilled screens, navigation drift, store rules), then show the flow map.\n\n## Rules for this flow\n\n- Say what the assistant can't do and where its information comes from; show sources when it cites any.\n- Long replies keep the composer reachable; the newest message stays in view.\n- Mark the result screen with `data-od-end`.\n\n## Markup contract (shared by every app screen)\n\n- **States.** Each state of the screen is a sibling `\u003Csection data-od-state=\"…\">`: `default` (populated), and the ones this pattern lists below from `empty`, `loading`, `error`, `success`, `no-access`, `long-content`. Only `default` is visible; the others carry `hidden`. The kit's check renders every state, and the preview shows them side by side.\n- **Slots.** Keep the seed's `data-od-slot` names (`nav`, `toolbar`, `content`, `empty`, `loading`) so states, links and comments line up.\n- **Links between screens.** When this screen is part of a planned flow, link to another screen with its entry path in `href` and its screen id in `data-od-goto`, and use the shared navigation the brief gives instead of drawing your own.\n- **The app's own components.** When the brief lists the app's components, build each part from one of them and mark it `data-od-component=\"\u003CName>\"`; mark a part with no match `data-od-component=\"new:\u003CName>\"`.\n- **Sample data.** Records come from the data file the brief describes, never typed into the markup row by row: one template row or card with `data-od-repeat=\"\u003Clist>\"` and `data-od-bind=\".\u003Cfield>\"` inside it, single values with `data-od-bind=\"\u003Clist>[n].\u003Cfield>\"`, and `data-od-format` for money, dates and numbers. Every screen that shows the same record binds to the same one.\n- **Tokens only.** Every colour, size, radius and shadow comes from the design system's `:root` variables. No raw hex outside `:root`.\n- **Platform.** Web app: the shell as given. iPhone, Android, tablet or desktop app: put `data-od-device` on `\u003Cbody>` (`iphone`, `android`, `tablet` with `data-od-orientation`, or `desktop-app` with `data-od-window=\"mac\"` or `\"windows\"`); the kit draws the device frame, status bar and home indicator around the screen, so never draw them yourself. iPhone or Android: a single column 390 px (iPhone) or 412 px (Android) wide, with a bottom tab bar instead of the side nav, a top bar with the title and a back button on inner screens, and 44 px (iPhone) or 48 px (Android) touch targets. Android screens use Material patterns (top app bar, floating action button where there is one main create action). Tablet: the sidebar collapses to an icon rail with labels in a tooltip, content in two columns where the pattern has a detail pane.\n- **Density.** Use the density the brief gives (compact, medium or airy) with the numbers from the product UI craft rules.\n\n## Seed\n\nStart from this shell (one HTML file, inline CSS). Replace the comments; keep the structure.\n\n\u003C!-- od:app-shell:start -->\n```html\n\u003C!doctype html>\n\u003Chtml lang=\"en\">\n\u003Chead>\n\u003Cmeta charset=\"utf-8\">\n\u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n\u003Ctitle>Screen title · Product\u003C\u002Ftitle>\n\u003Cstyle>\n\u002F* Paste the active design system's :root block here, then use only var(--…). *\u002F\n*,*::before,*::after{box-sizing:border-box}\nbody{margin:0;background:var(--bg);color:var(--fg);font:var(--text-base)\u002Fvar(--leading-body) var(--font-body)}\n.app{display:grid;grid-template-columns:1fr;min-height:100dvh}\n.app-nav{display:flex;gap:var(--space-1);padding:var(--space-2) var(--space-4);border-bottom:1px solid var(--border);overflow-x:auto}\n.app-nav a{display:flex;align-items:center;gap:var(--space-2);min-height:44px;padding:0 var(--space-3);border-radius:var(--radius-md);color:var(--muted);text-decoration:none;white-space:nowrap}\n.app-nav a[aria-current=\"page\"]{background:var(--surface);color:var(--fg);box-shadow:var(--elev-ring)}\n.app-main{min-width:0;padding:var(--space-4)}\n.app-toolbar{display:flex;flex-wrap:wrap;align-items:center;gap:var(--space-3);margin-bottom:var(--space-4)}\n.app-toolbar h1{margin:0 auto 0 0;font:600 var(--text-xl)\u002Fvar(--leading-tight) var(--font-display)}\n[data-od-state][hidden]{display:none}\n@media (min-width:64rem){\n  .app{grid-template-columns:260px 1fr}\n  .app-nav{flex-direction:column;border-bottom:0;border-right:1px solid var(--border);padding:var(--space-4)}\n  .app-main{padding:var(--space-6) var(--space-8)}\n}\n\u003C\u002Fstyle>\n\u003C\u002Fhead>\n\u003Cbody>\n\u003Cdiv class=\"app\">\n  \u003Cnav class=\"app-nav\" aria-label=\"Main\" data-od-slot=\"nav\">\n    \u003Ca href=\"#\" aria-current=\"page\">Current place\u003C\u002Fa>\n    \u003Ca href=\"#\">Another place\u003C\u002Fa>\n  \u003C\u002Fnav>\n  \u003Cmain class=\"app-main\">\n    \u003Cheader class=\"app-toolbar\" data-od-slot=\"toolbar\">\n      \u003Ch1>Screen title\u003C\u002Fh1>\n    \u003C\u002Fheader>\n    \u003Csection data-od-state=\"default\" data-od-slot=\"content\">\u003C!-- the populated screen -->\u003C\u002Fsection>\n    \u003Csection data-od-state=\"empty\" data-od-slot=\"empty\" hidden>\u003C!-- what will be here, why it is empty, the first action -->\u003C\u002Fsection>\n    \u003Csection data-od-state=\"loading\" data-od-slot=\"loading\" hidden aria-busy=\"true\">\u003C!-- a skeleton shaped like the content -->\u003C\u002Fsection>\n  \u003C\u002Fmain>\n\u003C\u002Fdiv>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\u003C!-- od:app-shell:end -->\n",{"od":24,"name":5,"tags":41,"emoji":49,"en_name":50,"zh_name":51,"category":52,"scenario":37,"triggers":53,"description":7,"en_description":7},{"mode":25,"craft":26,"preview":32,"surface":35,"platform":36,"scenario":37,"design_system":38,"example_prompt":40},"prototype",{"requires":27},[28,29,30,31],"product-ui","state-coverage","action-states","ux-writing",{"type":33,"entry":34},"html","index.html","web","desktop","design",{"requires":39},true,"The AI assistant inside a travel-planning app: empty chat with suggestions, a streaming answer, a network error with retry, and an itinerary card the user can save.",[42,43,44,45,46,47,48],"ai chat","assistant","chatbot","copilot","streaming","AI 助手","聊天","💬","AI Chat Flow","AI 对话流程","app",[42,54,55,56,57],"chat screen","assistant screen","chatbot ui","copilot ui","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fskills\u002Fflow-ai-chat",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":67,"prompt":77,"zipAvailable":39},[68,71,74],{"tool":69,"command":70},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill flow-ai-chat",{"tool":72,"command":73},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill flow-ai-chat",{"tool":75,"command":76},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill flow-ai-chat","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fcontent\u002Fassets\u002Fopen-design\u002Fskills\u002Fflow-ai-chat\u002FSKILL.md",[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\u002Fcontent\u002Fassets\u002Fopen-design\u002Fskills\u002Fflow-ai-chat\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",[],[]]