[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D3WM52MTFAZRA9CTC4KBW9":3,"skill-same:01M7D3WM52MTFAZRA9CTC4KBW9":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7D3WM52MTFAZRA9CTC4KBW9","open-design-site-audit",null,"Audit a live website with Open Design's own checks — contrast, tap targets, phone layout, larger text, broken images, page weight and template looks — and get a short, plain-language report of the biggest problems with marked screenshots — use whenever the user wants a website audited, checked or reviewed for design, accessibility or mobile problems (\"audit this site\", \"what's wrong with our website\", \"find problems on example.com\", \"why does our site look bad on phones\"), or wants talking points before pitching a redesign, even if they don't mention Open Design","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\u002F.agents\u002Fskills\u002Fopen-design-site-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: open-design-site-audit\ndescription: Audit a live website with Open Design's own checks — contrast, tap targets, phone layout, larger text, broken images, page weight and template looks — and get a short, plain-language report of the biggest problems with marked screenshots — use whenever the user wants a website audited, checked or reviewed for design, accessibility or mobile problems (\"audit this site\", \"what's wrong with our website\", \"find problems on example.com\", \"why does our site look bad on phones\"), or wants talking points before pitching a redesign, even if they don't mention Open Design\n---\n\n\u003C!-- generated:open-design-agent-kit -->\n\nAudit a live website with Open Design's checks and report what a visitor runs into.\n\nRequest: the rest of the user's message (if there is none, ask the user: \"Which website should be audited?\")\n\n**How to talk to the user.** Many people using Open Design don't write code, so:\n- Use the user's own words. If they say \"artifact\", \"design tokens\" or give a file path, use those terms back; otherwise use the plain words below.\n- Keep the machinery out of replies: no tool names, no ids like `od:prototype:poster-hero`, no internal files (`.artifact.json`, `.comments.json`, `config.json`), and not the words \"register\", \"manifest\", \"sidecar\", \"entry\" or \"surface\", unless the user used them first.\n- Explain a print term the first time it comes up, in one short clause, and not again.\n- Say where a file is the way the user would find it (\"in your Open Design folder, under seed-swap-flyer\"). Give a raw path only where the user can click it (Claude Code, Claude Desktop's Code tab, VS Code) or asks for it.\n- End each reply that finishes a step with one line on what they can do next, with at most two options (\"Want it in Instagram sizes too, or is it ready to print?\").\n\n| Instead of | Say |\n|---|---|\n| artifact, entry, registered | your design, saved |\n| design system, active design system | your style (the first time: \"a saved style: colours, fonts and spacing\") |\n| surface, skill, template, recipe | kind of design, starting layout, or nothing |\n| workspace, output directory | your folder, your Open Design folder |\n| bleed | print edge (\"a few millimetres extra that the printer trims off\") |\n| trim size | final size |\n| preflight findings, errors | \"I checked it and fixed…\", \"one thing to look at:\" |\n| export | save as PDF, save as an image |\n| inline preview, MCP App | the preview above |\n\n## 1. Ask only what's missing\n\nYou need the address. Up to 3 more pages on the same site are optional (a menu, services or contact page). If the request names them, use them; otherwise audit the home page alone and ask nothing.\n\n## 2. Run the audit\n\nCall `audit_open_design_site` with `url` and `extraUrls` if there are any.\n\n- **`ok` or `partial`**: you get the top problems (`top`), the rest (`otherGroups`), page weight and the report path. `partial` means some pages were blocked; say which and why.\n- **`blocked`**: nothing could be audited (a bot check, a members-only page or an empty page). Show the screenshot, say why, and ask for another public page. Don't retry with other settings.\n- An error about the browser means none is installed: say so, and suggest installing a browser such as Chrome ([troubleshooting](https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fdocs\u002Ftroubleshooting.md) has the details).\n\n## 3. Report it\n\nTell the user the top problems in plain words, in the audit's order: the title, where (page, phone or desktop), what it costs a visitor and the fix. Point to the report (`report`) and offer to open it in the preview.\n\n- Quote only what the audit found. Don't add a score, a speed rating, SEO advice or problems you guess at from the screenshots.\n- Don't call the site a template, generic or AI-made unless `top` or `otherGroups` has \"Looks like a stock template\". A single pattern (an indigo glow, a row of identical cards) is named for what it is. Patterns listed only in `notes` are common on hand-made sites too: leave them out of the problems, or mention them as such if asked.\n- If the report found nothing, say so plainly and list what was checked.\n- The audit looks at a site the user may not own. Keep the tone factual: this is evidence for a conversation, not a verdict.\n\n## 4. Next steps\n\nOffer one next step that fits the request:\n\n- **Redesign it**: make a concept that keeps the site's real content and brand and fixes these problems. The `open-design-redesign` skill starts from this audit.\n- **Match the brand**: make a design system from the site with `open-design-design-system-from-url`.\n- **Share it**: the report is a folder (`index.html` plus images) the user can zip or publish with `open-design-publish`.\n","\u003C!-- generated:open-design-agent-kit -->\n\nAudit a live website with Open Design's checks and report what a visitor runs into.\n\nRequest: the rest of the user's message (if there is none, ask the user: \"Which website should be audited?\")\n\n**How to talk to the user.** Many people using Open Design don't write code, so:\n- Use the user's own words. If they say \"artifact\", \"design tokens\" or give a file path, use those terms back; otherwise use the plain words below.\n- Keep the machinery out of replies: no tool names, no ids like `od:prototype:poster-hero`, no internal files (`.artifact.json`, `.comments.json`, `config.json`), and not the words \"register\", \"manifest\", \"sidecar\", \"entry\" or \"surface\", unless the user used them first.\n- Explain a print term the first time it comes up, in one short clause, and not again.\n- Say where a file is the way the user would find it (\"in your Open Design folder, under seed-swap-flyer\"). Give a raw path only where the user can click it (Claude Code, Claude Desktop's Code tab, VS Code) or asks for it.\n- End each reply that finishes a step with one line on what they can do next, with at most two options (\"Want it in Instagram sizes too, or is it ready to print?\").\n\n| Instead of | Say |\n|---|---|\n| artifact, entry, registered | your design, saved |\n| design system, active design system | your style (the first time: \"a saved style: colours, fonts and spacing\") |\n| surface, skill, template, recipe | kind of design, starting layout, or nothing |\n| workspace, output directory | your folder, your Open Design folder |\n| bleed | print edge (\"a few millimetres extra that the printer trims off\") |\n| trim size | final size |\n| preflight findings, errors | \"I checked it and fixed…\", \"one thing to look at:\" |\n| export | save as PDF, save as an image |\n| inline preview, MCP App | the preview above |\n\n## 1. Ask only what's missing\n\nYou need the address. Up to 3 more pages on the same site are optional (a menu, services or contact page). If the request names them, use them; otherwise audit the home page alone and ask nothing.\n\n## 2. Run the audit\n\nCall `audit_open_design_site` with `url` and `extraUrls` if there are any.\n\n- **`ok` or `partial`**: you get the top problems (`top`), the rest (`otherGroups`), page weight and the report path. `partial` means some pages were blocked; say which and why.\n- **`blocked`**: nothing could be audited (a bot check, a members-only page or an empty page). Show the screenshot, say why, and ask for another public page. Don't retry with other settings.\n- An error about the browser means none is installed: say so, and suggest installing a browser such as Chrome ([troubleshooting](https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fdocs\u002Ftroubleshooting.md) has the details).\n\n## 3. Report it\n\nTell the user the top problems in plain words, in the audit's order: the title, where (page, phone or desktop), what it costs a visitor and the fix. Point to the report (`report`) and offer to open it in the preview.\n\n- Quote only what the audit found. Don't add a score, a speed rating, SEO advice or problems you guess at from the screenshots.\n- Don't call the site a template, generic or AI-made unless `top` or `otherGroups` has \"Looks like a stock template\". A single pattern (an indigo glow, a row of identical cards) is named for what it is. Patterns listed only in `notes` are common on hand-made sites too: leave them out of the problems, or mention them as such if asked.\n- If the report found nothing, say so plainly and list what was checked.\n- The audit looks at a site the user may not own. Keep the tone factual: this is evidence for a conversation, not a verdict.\n\n## 4. Next steps\n\nOffer one next step that fits the request:\n\n- **Redesign it**: make a concept that keeps the site's real content and brand and fixes these problems. The `open-design-redesign` skill starts from this audit.\n- **Match the brand**: make a design system from the site with `open-design-design-system-from-url`.\n- **Share it**: the report is a folder (`index.html` plus images) the user can zip or publish with `open-design-publish`.\n",{"name":5,"description":7},"main","e38061066b92c298798dbddc1decbae8c026464f",".agents\u002Fskills\u002Fopen-design-site-audit",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-site-audit",{"tool":38,"command":39},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-site-audit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-site-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopen-design-site-audit\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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",[],[]]