[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D4DR15N35NFB4ZZRCGDKAS":3,"skill-same:01M7D4DR15N35NFB4ZZRCGDKAS":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},"01M7D4DR15N35NFB4ZZRCGDKAS","open-design-poster",null,"Design a poster or flyer for print or screen, check it, and export print-ready PDFs or upload-ready images, including other sizes and one version per row of a spreadsheet — use whenever the user wants a poster, flyer, event or gig poster, print piece, handout, certificate or name card set, or wants an existing design in other sizes or as a print-ready PDF, 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\u002Fpackages\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-poster\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"open-design-poster\"\ndescription: Design a poster or flyer for print or screen, check it, and export print-ready PDFs or upload-ready images, including other sizes and one version per row of a spreadsheet — use whenever the user wants a poster, flyer, event or gig poster, print piece, handout, certificate or name card set, or wants an existing design in other sizes or as a print-ready PDF, even if they don't mention Open Design\nargument-hint: what the poster is for, and optionally the size (e.g. \"A3 poster for our hackathon, with a QR code to the signup page\")\n---\n\n\u003C!-- generated:curated-entry -->\n\nDesign a poster with Open Design, check it, and export files that are ready to print or post.\n\nBrief: \"$ARGUMENTS\" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: \"What is the poster for, and is it for print (which size) or screens?\")\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. Pick the medium and a default shape\n\nDecide whether this is for **print** or **screens**. If the brief doesn't say, ask the user before doing anything else. Don't guess between print and screen: the units, bleed and type sizes are different.\n\nYou don't need the final size yet. The poster is built **fluid**: it reflows to any shape, so the user can pick or change the size later, when exporting. Use the size the user names as the default shape; otherwise use `a3` for print and `ig-portrait` for screens, and tell the user they can change it at any time.\n\n| Use | Format id | Size |\n|---|---|---|\n| Print, small: flyer, handout | `a4` · `letter` | 210×297 mm · 8.5×11 in |\n| Print, medium: notice-board poster | `a3` · `tabloid` | 297×420 mm · 11×17 in |\n| Print, large: wall poster | `a2` · `a1` · `poster-18x24` · `poster-24x36` | 420×594 mm · 594×841 mm · 18×24 in · 24×36 in |\n| Print, conference or research poster | `a0` | 841×1189 mm |\n| Instagram portrait | `ig-portrait` | 1080×1350 px |\n| Story \u002F Reels \u002F TikTok cover | `story` | 1080×1920 px |\n| X single image | `x-image` | 1600×900 px |\n| Square (Instagram \u002F LinkedIn) | `ig-square` | 1080×1080 px |\n\nA handout and a wall poster carry different amounts of text, so if the user says which it is, write the copy for that; the shape itself can still change.\n\n## 2. Generate\n\nIf the user asked for options (\"show me a few directions\"), run a design exploration first and build out the direction they pick, with the same `format` and `fluid: true`.\n\nOtherwise call `prepare_open_design_brief` with:\n\n- a `skillId`: `od:prototype:poster-hero` for a bold marketing poster, `od:prototype:magazine-poster` for an editorial or type-led one, or another skill whose style fits better (`list_open_design_skills` with query \"poster\");\n- the brief, in the user's words;\n- `format`: the default shape from step 1;\n- `fluid: true`.\n\nCall `list_open_design_design_systems` first if the user names a brand or visual direction, or `recommend_open_design_design_systems` if they name none and no design system is active.\n\nAuthor the file yourself, following the returned instructions. Their **Canvas** section is authoritative: one `data-od-card data-od-fluid` element sized by `--od-w`\u002F`--od-h`, everything inside sized in container units, and layout rules for wide and tall shapes. Also:\n\n- Use real copy from the brief, with no lorem ipsum. A poster is read from a distance: one dominant headline, then the what \u002F when \u002F where, then the call to action.\n- If the user gives a list of names, sessions or locations to make one poster each, mark the changing text with `data-od-field=\"\u003Ccolumn name>\"` (and a per-person QR slot with `data-od-qr-field=\"\u003Ccolumn>\"`), and fill the design with the first row's values.\n- No external image URLs unless the user supplied them. No emoji as key visuals; draw them as inline SVG.\n\n## 3. Add a QR code, if it needs one\n\nRegister the artifact first (step 4), then call `create_open_design_qr_code` with the entry path and the URL, and paste the returned inline SVG where the code goes. Never draw a fake or placeholder QR code.\n\n## 4. Register\n\nCall `register_open_design_artifact` with the entry path, kind `html`, a title, `sourceSkillId`, and `format` set to the default shape.\n\n## 5. Check and fix\n\nCall `check_open_design_artifact` with the entry path. It returns the poster as an image plus preflight findings. Fix every **error** in its findings (text cut off, overlapping or in the bleed, a QR code that doesn't decode), and fix warnings where you reasonably can (sizes that don't scale with the poster, small type, low contrast, low-resolution images). Look at the image too: the headline should dominate and nothing important should be cramped or cut. Check again until there are no errors (at most two fix rounds; tell the user about anything left).\n\n\u003C!-- claude-only -->\n**Artifact preview.** If you have an Artifact tool, publish this design as its private artifact preview once the check is clean: call `publish_open_design_artifact` with `provider: \"claude-artifact\"` and follow what it returns. Publish again after each round of feedback you apply; it goes to the same artifact. Give the link once, then just say the preview was updated.\n\u003C!-- \u002Fclaude-only -->\n\n## 6. Other shapes\n\nWhen the user wants other sizes, or before the final export of a print piece, call `export_open_design_artifact` with `shapeSheet: true` and `checkOnly: true` (add `presets` with just the shapes they care about, or leave it out for every shape). It writes one image of the poster at each shape, marking shapes with errors; show it to the user. If you can view images, look at it too: the headline should dominate every shape and nothing important should be cropped.\n\nFor a shape that has errors or looks wrong, call `adapt_open_design_artifact` with the entry path and those format ids. For a fluid poster it returns **tune** instructions: fix that shape inside the same file with its `@container` rule, then check every shape again with a shape sheet. Don't create new files for other sizes.\n\n## 7. Export\n\n- **One shape:** call `export_open_design_artifact` with the entry path and `preset` set to the format id. A print format gives a PDF the size of the bleed box, with trim and bleed boxes set and the bleed added automatically; add `cropMarks: true` if the user's printer wants crop marks. A screen format gives a PNG within the platform's size limit.\n- **Several shapes:** pass `presets` with the format ids instead: one file per shape, named `\u003Cname>-\u003Cformat>`.\n- **One per row of a list:** add `data` with the workspace path of the user's CSV, XLSX or JSON file, and `nameField` with the column to name files by. Images come out one per row; print PDFs come out as one multi-page PDF per shape (add `split: true` for one file per row).\n\n## 8. Report\n\nList each exported file's path, size and any remaining warnings. For print files, also give the trim size and bleed, and tell the user the PDF is RGB: most print shops convert it, but they should ask if theirs needs CMYK. Mention that the poster can be exported at any other size later without regenerating it. Don't print, post, upload or order anything yourself.\n","\u003C!-- generated:curated-entry -->\n\nDesign a poster with Open Design, check it, and export files that are ready to print or post.\n\nBrief: \"$ARGUMENTS\" — or, if that is empty, the user's request in this conversation (if it isn't clear, ask the user: \"What is the poster for, and is it for print (which size) or screens?\")\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. Pick the medium and a default shape\n\nDecide whether this is for **print** or **screens**. If the brief doesn't say, ask the user before doing anything else. Don't guess between print and screen: the units, bleed and type sizes are different.\n\nYou don't need the final size yet. The poster is built **fluid**: it reflows to any shape, so the user can pick or change the size later, when exporting. Use the size the user names as the default shape; otherwise use `a3` for print and `ig-portrait` for screens, and tell the user they can change it at any time.\n\n| Use | Format id | Size |\n|---|---|---|\n| Print, small: flyer, handout | `a4` · `letter` | 210×297 mm · 8.5×11 in |\n| Print, medium: notice-board poster | `a3` · `tabloid` | 297×420 mm · 11×17 in |\n| Print, large: wall poster | `a2` · `a1` · `poster-18x24` · `poster-24x36` | 420×594 mm · 594×841 mm · 18×24 in · 24×36 in |\n| Print, conference or research poster | `a0` | 841×1189 mm |\n| Instagram portrait | `ig-portrait` | 1080×1350 px |\n| Story \u002F Reels \u002F TikTok cover | `story` | 1080×1920 px |\n| X single image | `x-image` | 1600×900 px |\n| Square (Instagram \u002F LinkedIn) | `ig-square` | 1080×1080 px |\n\nA handout and a wall poster carry different amounts of text, so if the user says which it is, write the copy for that; the shape itself can still change.\n\n## 2. Generate\n\nIf the user asked for options (\"show me a few directions\"), run a design exploration first and build out the direction they pick, with the same `format` and `fluid: true`.\n\nOtherwise call `prepare_open_design_brief` with:\n\n- a `skillId`: `od:prototype:poster-hero` for a bold marketing poster, `od:prototype:magazine-poster` for an editorial or type-led one, or another skill whose style fits better (`list_open_design_skills` with query \"poster\");\n- the brief, in the user's words;\n- `format`: the default shape from step 1;\n- `fluid: true`.\n\nCall `list_open_design_design_systems` first if the user names a brand or visual direction, or `recommend_open_design_design_systems` if they name none and no design system is active.\n\nAuthor the file yourself, following the returned instructions. Their **Canvas** section is authoritative: one `data-od-card data-od-fluid` element sized by `--od-w`\u002F`--od-h`, everything inside sized in container units, and layout rules for wide and tall shapes. Also:\n\n- Use real copy from the brief, with no lorem ipsum. A poster is read from a distance: one dominant headline, then the what \u002F when \u002F where, then the call to action.\n- If the user gives a list of names, sessions or locations to make one poster each, mark the changing text with `data-od-field=\"\u003Ccolumn name>\"` (and a per-person QR slot with `data-od-qr-field=\"\u003Ccolumn>\"`), and fill the design with the first row's values.\n- No external image URLs unless the user supplied them. No emoji as key visuals; draw them as inline SVG.\n\n## 3. Add a QR code, if it needs one\n\nRegister the artifact first (step 4), then call `create_open_design_qr_code` with the entry path and the URL, and paste the returned inline SVG where the code goes. Never draw a fake or placeholder QR code.\n\n## 4. Register\n\nCall `register_open_design_artifact` with the entry path, kind `html`, a title, `sourceSkillId`, and `format` set to the default shape.\n\n## 5. Check and fix\n\nCall `check_open_design_artifact` with the entry path. It returns the poster as an image plus preflight findings. Fix every **error** in its findings (text cut off, overlapping or in the bleed, a QR code that doesn't decode), and fix warnings where you reasonably can (sizes that don't scale with the poster, small type, low contrast, low-resolution images). Look at the image too: the headline should dominate and nothing important should be cramped or cut. Check again until there are no errors (at most two fix rounds; tell the user about anything left).\n\n\u003C!-- claude-only -->\n**Artifact preview.** If you have an Artifact tool, publish this design as its private artifact preview once the check is clean: call `publish_open_design_artifact` with `provider: \"claude-artifact\"` and follow what it returns. Publish again after each round of feedback you apply; it goes to the same artifact. Give the link once, then just say the preview was updated.\n\u003C!-- \u002Fclaude-only -->\n\n## 6. Other shapes\n\nWhen the user wants other sizes, or before the final export of a print piece, call `export_open_design_artifact` with `shapeSheet: true` and `checkOnly: true` (add `presets` with just the shapes they care about, or leave it out for every shape). It writes one image of the poster at each shape, marking shapes with errors; show it to the user. If you can view images, look at it too: the headline should dominate every shape and nothing important should be cropped.\n\nFor a shape that has errors or looks wrong, call `adapt_open_design_artifact` with the entry path and those format ids. For a fluid poster it returns **tune** instructions: fix that shape inside the same file with its `@container` rule, then check every shape again with a shape sheet. Don't create new files for other sizes.\n\n## 7. Export\n\n- **One shape:** call `export_open_design_artifact` with the entry path and `preset` set to the format id. A print format gives a PDF the size of the bleed box, with trim and bleed boxes set and the bleed added automatically; add `cropMarks: true` if the user's printer wants crop marks. A screen format gives a PNG within the platform's size limit.\n- **Several shapes:** pass `presets` with the format ids instead: one file per shape, named `\u003Cname>-\u003Cformat>`.\n- **One per row of a list:** add `data` with the workspace path of the user's CSV, XLSX or JSON file, and `nameField` with the column to name files by. Images come out one per row; print PDFs come out as one multi-page PDF per shape (add `split: true` for one file per row).\n\n## 8. Report\n\nList each exported file's path, size and any remaining warnings. For print files, also give the trim size and bleed, and tell the user the PDF is RGB: most print shops convert it, but they should ask if theirs needs CMYK. Mention that the poster can be exported at any other size later without regenerating it. Don't print, post, upload or order anything yourself.\n",{"name":5,"description":7,"argument-hint":24},"what the poster is for, and optionally the size (e.g. \"A3 poster for our hackathon, with a QR code to the signup page\")","main","e38061066b92c298798dbddc1decbae8c026464f","packages\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-poster",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-poster",{"tool":39,"command":40},"bunx","bunx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-poster",{"tool":42,"command":43},"pnpm","pnpm dlx skills add feimacode\u002Fopen-design-agent-kit --skill open-design-poster","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeimacode\u002Fopen-design-agent-kit\u002Fblob\u002Fmain\u002Fpackages\u002Fclaude-plugin-local\u002Fskills\u002Fopen-design-poster\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",[],[]]