[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HQEK6Y09SSXYZVCN17KC1N":3,"skill-same:01M6HQEK6Y09SSXYZVCN17KC1N":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M6HQEK6Y09SSXYZVCN17KC1N","design-critique",null,"Get structured design feedback on usability, hierarchy, and consistency. Trigger with \"review this design\", \"critique this mockup\", \"what do you think of this screen?\", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.","welflau\u002Fai-dev-system","welflau","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7010385?v=4","01M6HPTDGF18RFY07M229P8CTM","01M6HPTDMRMZCJPYBFEA9XVVYT",3,"MIT","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcb_teams_marketplace\u002Fplugins\u002Fdesign-to-code\u002Fskills\u002Fdesign-critique\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"design critique","critique","design","stage","when","hierarchy","for","consistency","you","URL","with","screen","link","trigger","get","exploration","do","usability","feedback","sharing","figma","review","2026-11-10 10:12:30",false,"---\nname: design-critique\ndescription: Get structured design feedback on usability, hierarchy, and consistency. Trigger with \"review this design\", \"critique this mockup\", \"what do you think of this screen?\", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.\nargument-hint: \"\u003CFigma URL, screenshot, or description>\"\n---\n\n# \u002Fdesign-critique\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGet structured design feedback across multiple dimensions.\n\n## Usage\n\n```\n\u002Fdesign-critique $ARGUMENTS\n```\n\nReview the design: @$1\n\nIf a Figma URL is provided, pull the design from Figma. If a file is referenced, read it. Otherwise, ask the user to describe or share their design.\n\n## What I Need From You\n\n- **The design**: Figma URL, screenshot, or detailed description\n- **Context**: What is this? Who is it for? What stage (exploration, refinement, final)?\n- **Focus** (optional): \"Focus on mobile\" or \"Focus on the onboarding flow\"\n\n## Critique Framework\n\n### 1. First Impression (2 seconds)\n- What draws the eye first? Is that correct?\n- What's the emotional reaction?\n- Is the purpose immediately clear?\n\n### 2. Usability\n- Can the user accomplish their goal?\n- Is the navigation intuitive?\n- Are interactive elements obvious?\n- Are there unnecessary steps?\n\n### 3. Visual Hierarchy\n- Is there a clear reading order?\n- Are the right elements emphasized?\n- Is whitespace used effectively?\n- Is typography creating the right hierarchy?\n\n### 4. Consistency\n- Does it follow the design system?\n- Are spacing, colors, and typography consistent?\n- Do similar elements behave similarly?\n\n### 5. Accessibility\n- Color contrast ratios\n- Touch target sizes\n- Text readability\n- Alternative text for images\n\n## How to Give Feedback\n\n- **Be specific**: \"The CTA competes with the navigation\" not \"the layout is confusing\"\n- **Explain why**: Connect feedback to design principles or user needs\n- **Suggest alternatives**: Don't just identify problems, propose solutions\n- **Acknowledge what works**: Good feedback includes positive observations\n- **Match the stage**: Early exploration gets different feedback than final polish\n\n## Output\n\n```markdown\n## Design Critique: [Design Name]\n\n### Overall Impression\n[1-2 sentence first reaction — what works, what's the biggest opportunity]\n\n### Usability\n| Finding | Severity | Recommendation |\n|---------|----------|----------------|\n| [Issue] | ? Critical \u002F ? Moderate \u002F ? Minor | [Fix] |\n\n### Visual Hierarchy\n- **What draws the eye first**: [Element] — [Is this correct?]\n- **Reading flow**: [How does the eye move through the layout?]\n- **Emphasis**: [Are the right things emphasized?]\n\n### Consistency\n| Element | Issue | Recommendation |\n|---------|-------|----------------|\n| [Typography\u002Fspacing\u002Fcolor] | [Inconsistency] | [Fix] |\n\n### Accessibility\n- **Color contrast**: [Pass\u002Ffail for key text]\n- **Touch targets**: [Adequate size?]\n- **Text readability**: [Font size, line height]\n\n### What Works Well\n- [Positive observation 1]\n- [Positive observation 2]\n\n### Priority Recommendations\n1. **[Most impactful change]** — [Why and how]\n2. **[Second priority]** — [Why and how]\n3. **[Third priority]** — [Why and how]\n```\n\n## If Connectors Available\n\nIf **~~design tool** is connected:\n- Pull the design directly from Figma and inspect components, tokens, and layers\n- Compare against the existing design system for consistency\n\nIf **~~user feedback** is connected:\n- Cross-reference design decisions with recent user feedback and support tickets\n\n## Tips\n\n1. **Share the context** — \"This is a checkout flow for a B2B SaaS\" helps me give relevant feedback.\n2. **Specify your stage** — Early exploration gets different feedback than final polish.\n3. **Ask me to focus** — \"Just look at the navigation\" gives you more depth on one area.\n","# \u002Fdesign-critique\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGet structured design feedback across multiple dimensions.\n\n## Usage\n\n```\n\u002Fdesign-critique $ARGUMENTS\n```\n\nReview the design: @$1\n\nIf a Figma URL is provided, pull the design from Figma. If a file is referenced, read it. Otherwise, ask the user to describe or share their design.\n\n## What I Need From You\n\n- **The design**: Figma URL, screenshot, or detailed description\n- **Context**: What is this? Who is it for? What stage (exploration, refinement, final)?\n- **Focus** (optional): \"Focus on mobile\" or \"Focus on the onboarding flow\"\n\n## Critique Framework\n\n### 1. First Impression (2 seconds)\n- What draws the eye first? Is that correct?\n- What's the emotional reaction?\n- Is the purpose immediately clear?\n\n### 2. Usability\n- Can the user accomplish their goal?\n- Is the navigation intuitive?\n- Are interactive elements obvious?\n- Are there unnecessary steps?\n\n### 3. Visual Hierarchy\n- Is there a clear reading order?\n- Are the right elements emphasized?\n- Is whitespace used effectively?\n- Is typography creating the right hierarchy?\n\n### 4. Consistency\n- Does it follow the design system?\n- Are spacing, colors, and typography consistent?\n- Do similar elements behave similarly?\n\n### 5. Accessibility\n- Color contrast ratios\n- Touch target sizes\n- Text readability\n- Alternative text for images\n\n## How to Give Feedback\n\n- **Be specific**: \"The CTA competes with the navigation\" not \"the layout is confusing\"\n- **Explain why**: Connect feedback to design principles or user needs\n- **Suggest alternatives**: Don't just identify problems, propose solutions\n- **Acknowledge what works**: Good feedback includes positive observations\n- **Match the stage**: Early exploration gets different feedback than final polish\n\n## Output\n\n```markdown\n## Design Critique: [Design Name]\n\n### Overall Impression\n[1-2 sentence first reaction — what works, what's the biggest opportunity]\n\n### Usability\n| Finding | Severity | Recommendation |\n|---------|----------|----------------|\n| [Issue] | ? Critical \u002F ? Moderate \u002F ? Minor | [Fix] |\n\n### Visual Hierarchy\n- **What draws the eye first**: [Element] — [Is this correct?]\n- **Reading flow**: [How does the eye move through the layout?]\n- **Emphasis**: [Are the right things emphasized?]\n\n### Consistency\n| Element | Issue | Recommendation |\n|---------|-------|----------------|\n| [Typography\u002Fspacing\u002Fcolor] | [Inconsistency] | [Fix] |\n\n### Accessibility\n- **Color contrast**: [Pass\u002Ffail for key text]\n- **Touch targets**: [Adequate size?]\n- **Text readability**: [Font size, line height]\n\n### What Works Well\n- [Positive observation 1]\n- [Positive observation 2]\n\n### Priority Recommendations\n1. **[Most impactful change]** — [Why and how]\n2. **[Second priority]** — [Why and how]\n3. **[Third priority]** — [Why and how]\n```\n\n## If Connectors Available\n\nIf **~~design tool** is connected:\n- Pull the design directly from Figma and inspect components, tokens, and layers\n- Compare against the existing design system for consistency\n\nIf **~~user feedback** is connected:\n- Cross-reference design decisions with recent user feedback and support tickets\n\n## Tips\n\n1. **Share the context** — \"This is a checkout flow for a B2B SaaS\" helps me give relevant feedback.\n2. **Specify your stage** — Early exploration gets different feedback than final polish.\n3. **Ask me to focus** — \"Just look at the navigation\" gives you more depth on one area.\n",{"name":5,"description":7,"argument-hint":55},"\u003CFigma URL, screenshot, or description>","main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fskills\u002Fmarketplace\u002Fcb_teams_marketplace\u002Fplugins\u002Fdesign-to-code\u002Fskills\u002Fdesign-critique",1,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system","https:\u002F\u002Fgithub.com\u002Fwelflau","2026-11-12 14:55:20",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add welflau\u002Fai-dev-system --skill design-critique",{"tool":69,"command":70},"bunx","bunx skills add welflau\u002Fai-dev-system --skill design-critique",{"tool":72,"command":73},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill design-critique","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcb_teams_marketplace\u002Fplugins\u002Fdesign-to-code\u002Fskills\u002Fdesign-critique\u002FSKILL.md",true,[],[78,109,139,165,187,211],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":92,"publishedAt":108},"01M6HS9Z4B0YA8CJCS2Y2F04Y3","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FSKILL.md",[86,89],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":90,"categoryName":91,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,38,34],"testing","webapp testing","webapp","frontend","screenshots","playwright","web","debugging","toolkit","browser","ui","logs","applications","behavior","local","2026-11-11 15:11:14",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":108},"01M6HRAGMG7JF0HXYHMA5QHS8A","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通",[120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138],"internal comms","comms","status","help","SET","write","use","reports","me","incident","leadership","project","resources","communications","internal communications","formats","sort","my","updates",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":50},"01M6HSTDP4M3JFXEBK91VFB4PA","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FSKILL.md",[146],{"categoryNo":90,"categoryName":91,"taxonomyType":20,"taxonomyTypeDesc":21},[148,99,149,150,151,96,152,153,154,155,156,157,158,159,126,160,161,162,163,34,164],"web artifacts builder","artifacts","artifacts builder","builder","css","components","react","routing","state management","state","file","Tailwind","single-file","simple","ui components","multi","single",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":50},"01M6HSDXH0JSP8R3QTNY9XZ8HN","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FSKILL.md",[172,173,174],{"categoryNo":90,"categoryName":91,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[96,30,176,152,99,153,154,177,178,179,149,180,105,181,126,182,183,184,185,38,186,32],"frontend design","react components","create","code","examples","landing","ui design","pages","aesthetics","web ui","generic",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":191,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":50},"01M6HSA77QYVP7A72HREGTDN2C","algorithmic-art","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FSKILL.md",[194],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[196,197,198,178,179,199,200,201,202,126,203,43,204,205,38,206,207,208,209,210,32],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","systems","users","Existing","request","generative","copyright","fields",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":215,"sourceHtmlUrl":216,"categories":217,"keywords":219,"publishedAt":50},"01M6HS9HE0X390Y6RQKTY1YNGJ","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FSKILL.md",[218],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[220,221,222,223,101,224,149,124,225,226,181,227,228,183,229,38,36,230,231,34,232,233],"theme factory","factory","theme","docs","generate","fly","slides","styling","artifact","themes","fonts","can","apply","new"]