[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D4ECDM5EGC0QC479PPC9GT":3,"skill-same:01M7D4ECDM5EGC0QC479PPC9GT":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7D4ECDM5EGC0QC479PPC9GT","open-design-redesign",null,"Redesign a live website — audit it, take its brand and its real words, photos, hours and prices, and design a new home page and up to 3 inner pages as one linked site that fixes the problems found, marked as a concept until the owner agrees — use whenever the user wants an existing website redesigned, refreshed, modernized or mocked up again (\"redesign rosas.example\", \"show this bakery what a better site could look like\", \"a new version of our website\", \"pitch a redesign to this business\"), even if they don't mention Open Design; not for a new site from scratch","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\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-redesign\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"open-design-redesign\"\ndescription: Redesign a live website — audit it, take its brand and its real words, photos, hours and prices, and design a new home page and up to 3 inner pages as one linked site that fixes the problems found, marked as a concept until the owner agrees — use whenever the user wants an existing website redesigned, refreshed, modernized or mocked up again (\"redesign rosas.example\", \"show this bakery what a better site could look like\", \"a new version of our website\", \"pitch a redesign to this business\"), even if they don't mention Open Design; not for a new site from scratch\nargument-hint: the website address, and optionally up to 3 more pages (e.g. \"https:\u002F\u002Frosas.example, plus \u002Fmenu and \u002Fcontact\")\n---\n\n\u003C!-- generated:curated-entry -->\n\nRedesign a live website: keep its content and brand, fix what's wrong with it, and show it as a concept.\n\nRequest: \"$ARGUMENTS\" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: \"Which website should be redesigned?\")\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 one question at most\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 redesign the home page and pick up to 2 inner pages from its navigation.\n\nAsk only this, unless the request already answers it: **keep the brand (colours, fonts, logo) or refresh it?** Default to keep.\n\nAlso note whether the user says the site is theirs or the work is commissioned. Unless they do, treat it as a concept of someone else's site (`owned: false`). Don't ask; it only decides the ribbon.\n\n## 2. Audit the site\n\nIf `audit_open_design_site` is available, call it with `url` and `extraUrls`. Tell the user the top problems in one or two lines each; the design will fix them. If it is `blocked`, say why and stop: the same pages won't load for the content either.\n\n## 3. Take the brand and the content in one visit\n\nCall `extract_open_design_design_system` with the same `url` and `extraUrls`, and `content: true`. Add `localizeImages: true` only if the user said the site is theirs.\n\n- Pages `blocked` because robots.txt disallows them are left out. Say so and don't retry.\n- **Keep the brand**: write DESIGN.md and tokens.css from the draft, as the `open-design-design-system-from-url` skill does, and save it as a custom design system.\n- **Refresh it**: keep the logo and the brand colour, and call `recommend_open_design_design_systems` for the rest.\n\n## 4. Plan the pages\n\nPlan the home page and the inner pages as one linked flow (a `collectionId` and a `flow` plan with the site's main navigation as the shared nav). Lead with what a visitor comes for (book, call, order, find the place), and add it as the flow's task, so the check and the critic walk it.\n\n## 5. Design each page\n\nFor each page, call `prepare_open_design_brief` with:\n\n- the `web-prototype` skill, the design system, the flow, `collectionId` and `screenRole`;\n- `redesign: { site: \u003Cthe url>, owned: \u003Ctrue only if the user said so> }`;\n- `baseScreen`: that old page's desktop screenshot from the extraction bundle (`screenshots` in its result), so the check shows old and new side by side.\n\nFollow the brief's redesign section: bind the site's own words from `content.json`, mark any rewritten text with `data-od-copy-edit` and the original in `data-od-original`, and keep the concept ribbon unless the site is the user's. Don't invent facts the site doesn't have.\n\n## 6. Check and critique\n\nCall `check_open_design_artifact` on each page and fix what it reports, including `copy-edit-original-missing` and `concept-unmarked`. Then get a second opinion with `open-design-critique`: the critic checks that the audit's problems are gone.\n\n## 7. Before and after\n\nCall `compare_open_design_before_after` with the `collectionId` (or the `entryPath` for a single page). It puts each old page beside the new one, re-checks every audit problem on the new design and lists the copy edits.\n\n- Problems marked **still open** aren't fixed: fix them and run it again, or tell the user plainly which remain.\n- Then run it once more with up to 3 `summary` lines for the client, each citing the fixed findings it rests on (`{ \"text\": \"The booking button is readable and on the first phone screen.\", \"cites\": [\"F1\", \"F2\"] }`). Lines that cite nothing or an open finding are left out. Don't claim anything the page doesn't show (speed, search ranking, sales).\n\n## 8. Hand it over\n\nShow the user the before\u002Fafter page and list the copy edits. Offer next:\n\n- **Send it**: export the before\u002Fafter page as a PDF (one page per screen) for email, or publish the redesign with `open-design-publish`; a flow's published site links to the before\u002Fafter page from its map. A page with the concept band gets a warning: send the link to the business rather than posting it publicly.\n","\u003C!-- generated:curated-entry -->\n\nRedesign a live website: keep its content and brand, fix what's wrong with it, and show it as a concept.\n\nRequest: \"$ARGUMENTS\" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: \"Which website should be redesigned?\")\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 one question at most\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 redesign the home page and pick up to 2 inner pages from its navigation.\n\nAsk only this, unless the request already answers it: **keep the brand (colours, fonts, logo) or refresh it?** Default to keep.\n\nAlso note whether the user says the site is theirs or the work is commissioned. Unless they do, treat it as a concept of someone else's site (`owned: false`). Don't ask; it only decides the ribbon.\n\n## 2. Audit the site\n\nIf `audit_open_design_site` is available, call it with `url` and `extraUrls`. Tell the user the top problems in one or two lines each; the design will fix them. If it is `blocked`, say why and stop: the same pages won't load for the content either.\n\n## 3. Take the brand and the content in one visit\n\nCall `extract_open_design_design_system` with the same `url` and `extraUrls`, and `content: true`. Add `localizeImages: true` only if the user said the site is theirs.\n\n- Pages `blocked` because robots.txt disallows them are left out. Say so and don't retry.\n- **Keep the brand**: write DESIGN.md and tokens.css from the draft, as the `open-design-design-system-from-url` skill does, and save it as a custom design system.\n- **Refresh it**: keep the logo and the brand colour, and call `recommend_open_design_design_systems` for the rest.\n\n## 4. Plan the pages\n\nPlan the home page and the inner pages as one linked flow (a `collectionId` and a `flow` plan with the site's main navigation as the shared nav). Lead with what a visitor comes for (book, call, order, find the place), and add it as the flow's task, so the check and the critic walk it.\n\n## 5. Design each page\n\nFor each page, call `prepare_open_design_brief` with:\n\n- the `web-prototype` skill, the design system, the flow, `collectionId` and `screenRole`;\n- `redesign: { site: \u003Cthe url>, owned: \u003Ctrue only if the user said so> }`;\n- `baseScreen`: that old page's desktop screenshot from the extraction bundle (`screenshots` in its result), so the check shows old and new side by side.\n\nFollow the brief's redesign section: bind the site's own words from `content.json`, mark any rewritten text with `data-od-copy-edit` and the original in `data-od-original`, and keep the concept ribbon unless the site is the user's. Don't invent facts the site doesn't have.\n\n## 6. Check and critique\n\nCall `check_open_design_artifact` on each page and fix what it reports, including `copy-edit-original-missing` and `concept-unmarked`. Then get a second opinion with `open-design-critique`: the critic checks that the audit's problems are gone.\n\n## 7. Before and after\n\nCall `compare_open_design_before_after` with the `collectionId` (or the `entryPath` for a single page). It puts each old page beside the new one, re-checks every audit problem on the new design and lists the copy edits.\n\n- Problems marked **still open** aren't fixed: fix them and run it again, or tell the user plainly which remain.\n- Then run it once more with up to 3 `summary` lines for the client, each citing the fixed findings it rests on (`{ \"text\": \"The booking button is readable and on the first phone screen.\", \"cites\": [\"F1\", \"F2\"] }`). Lines that cite nothing or an open finding are left out. Don't claim anything the page doesn't show (speed, search ranking, sales).\n\n## 8. Hand it over\n\nShow the user the before\u002Fafter page and list the copy edits. Offer next:\n\n- **Send it**: export the before\u002Fafter page as a PDF (one page per screen) for email, or publish the redesign with `open-design-publish`; a flow's published site links to the before\u002Fafter page from its map. A page with the concept band gets a warning: send the link to the business rather than posting it publicly.\n",{"name":5,"description":7,"argument-hint":24},"the website address, and optionally up to 3 more pages (e.g. \"https:\u002F\u002Frosas.example, plus \u002Fmenu and \u002Fcontact\")","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-redesign",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-redesign",{"tool":39,"command":40},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-redesign",{"tool":42,"command":43},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-redesign","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-redesign\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]