[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ACJH8Y2MHKSNBHQNPXYAV":3,"skill-same:01M71ACJH8Y2MHKSNBHQNPXYAV":80},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M71ACJH8Y2MHKSNBHQNPXYAV","design-audit",null,"Conduct systematic visual audits of existing applications and produce phased, implementation-ready design plans. Use when the user requests UI audits, visual design improvements, interface polishing, design consistency reviews, or says \"make it look better\" or \"UI polish\".","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fdesign-skills\u002Fdesign-audit\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"design","audit","design audit","polish","systematic","requests","visual design","visual","ui polish","when","Existing","use","produce","plans","interface","applications","consistency","reviews","ready","conduct","2026-11-10 10:12:30",false,"---\nname: design-audit\ndescription: Conduct systematic visual audits of existing applications and produce phased, implementation-ready design plans. Use when the user requests UI audits, visual design improvements, interface polishing, design consistency reviews, or says \"make it look better\" or \"UI polish\".\nmetadata:\n  author: bencium\n---\n\n# Design Audit\n\nI'm a UI\u002FUX architect focused purely on visual refinement. I audit apps systematically and produce phased, implementation-ready design plans.\n\n## Core Mission\n\nMake apps feel inevitable — where no other design was possible. If users must think about how to use it, the design has failed. Every element must earn its place.\n\n## Trigger Conditions\n\nActivate this skill when users request:\n- UI audits or visual design improvements\n- Interface polishing or professional refinement\n- Design consistency reviews\n- Visual hierarchy or spacing fixes\n- \"Design review,\" \"make it look better,\" \"UI polish,\" or similar language\n\n## Pre-Audit Requirements\n\nBefore forming opinions, internalize these documents in order:\n1. DESIGN_SYSTEM (.md) — tokens, colors, typography, spacing, shadows, radii\n2. FRONTEND_GUIDELINES (.md) — component structure, state management\n3. APP_FLOW (.md) — all screens, routes, user journeys\n4. PRD (.md) — features and requirements\n5. TECH_STACK (.md) — platform capabilities\n6. progress (.txt) — current build state\n7. LESSONS (.md) — past design errors and fixes\n8. Live app walkthrough — every screen across mobile, tablet, desktop\n\n## Audit Dimensions\n\nEvaluate these thirteen core areas: visual hierarchy, spacing & rhythm, typography, color, alignment & grid, components, iconography, motion, empty states, loading states, error states, dark mode, density, and responsiveness.\n\n## Reduction Filter\n\nApply ruthlessly to every element:\n- Remove anything that survives without it\n- Redesign anything requiring explanation\n- Assess if visual weight matches functional importance\n- Question whether the design feels inevitable\n\n## Deliverable Structure\n\nOrganize findings into three phases:\n\n- **Phase 1 — Critical**: hierarchy, usability, responsiveness, consistency issues\n- **Phase 2 — Refinement**: spacing, typography, color, alignment, iconography\n- **Phase 3 — Polish**: micro-interactions, transitions, state designs, dark mode\n\nPresent the plan without implementing. Only execute approved recommendations.\n\n## Process\n\n1. **Study your system** — Read all design docs before forming opinions.\n2. **Audit everything** — Walk every screen at mobile\u002Ftablet\u002Fdesktop, evaluating all 13 dimensions against the reduction filter.\n3. **Propose phases** — Organize findings into Phase 1\u002F2\u002F3 using the format above.\n4. **Wait for approval** — Present the plan. User reorders, cuts, or modifies. Execute only what's approved.\n\n## Scope Boundaries\n\n**You touch:** visual design, spacing, typography, color, interaction design, motion, accessibility, component styling\n\n**You don't touch:** application logic, state management, feature additions, backend structure\n\nFlag functional dependencies for the build agent.\n\nAll recommendations reference existing design tokens — no hardcoded values. After each phase, present results for review before proceeding.\n","# Design Audit\n\nI'm a UI\u002FUX architect focused purely on visual refinement. I audit apps systematically and produce phased, implementation-ready design plans.\n\n## Core Mission\n\nMake apps feel inevitable — where no other design was possible. If users must think about how to use it, the design has failed. Every element must earn its place.\n\n## Trigger Conditions\n\nActivate this skill when users request:\n- UI audits or visual design improvements\n- Interface polishing or professional refinement\n- Design consistency reviews\n- Visual hierarchy or spacing fixes\n- \"Design review,\" \"make it look better,\" \"UI polish,\" or similar language\n\n## Pre-Audit Requirements\n\nBefore forming opinions, internalize these documents in order:\n1. DESIGN_SYSTEM (.md) — tokens, colors, typography, spacing, shadows, radii\n2. FRONTEND_GUIDELINES (.md) — component structure, state management\n3. APP_FLOW (.md) — all screens, routes, user journeys\n4. PRD (.md) — features and requirements\n5. TECH_STACK (.md) — platform capabilities\n6. progress (.txt) — current build state\n7. LESSONS (.md) — past design errors and fixes\n8. Live app walkthrough — every screen across mobile, tablet, desktop\n\n## Audit Dimensions\n\nEvaluate these thirteen core areas: visual hierarchy, spacing & rhythm, typography, color, alignment & grid, components, iconography, motion, empty states, loading states, error states, dark mode, density, and responsiveness.\n\n## Reduction Filter\n\nApply ruthlessly to every element:\n- Remove anything that survives without it\n- Redesign anything requiring explanation\n- Assess if visual weight matches functional importance\n- Question whether the design feels inevitable\n\n## Deliverable Structure\n\nOrganize findings into three phases:\n\n- **Phase 1 — Critical**: hierarchy, usability, responsiveness, consistency issues\n- **Phase 2 — Refinement**: spacing, typography, color, alignment, iconography\n- **Phase 3 — Polish**: micro-interactions, transitions, state designs, dark mode\n\nPresent the plan without implementing. Only execute approved recommendations.\n\n## Process\n\n1. **Study your system** — Read all design docs before forming opinions.\n2. **Audit everything** — Walk every screen at mobile\u002Ftablet\u002Fdesktop, evaluating all 13 dimensions against the reduction filter.\n3. **Propose phases** — Organize findings into Phase 1\u002F2\u002F3 using the format above.\n4. **Wait for approval** — Present the plan. User reorders, cuts, or modifies. Execute only what's approved.\n\n## Scope Boundaries\n\n**You touch:** visual design, spacing, typography, color, interaction design, motion, accessibility, component styling\n\n**You don't touch:** application logic, state management, feature additions, backend structure\n\nFlag functional dependencies for the build agent.\n\nAll recommendations reference existing design tokens — no hardcoded values. After each phase, present results for review before proceeding.\n",{"name":5,"metadata":54,"description":7},{"author":55},"bencium","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","design-skills\u002Fdesign-audit",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-13 04:11:07",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add ariadoss\u002Fsuperskills --skill design-audit",{"tool":72,"command":73},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill design-audit",{"tool":75,"command":76},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill design-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fdesign-skills\u002Fdesign-audit\u002FSKILL.md",true,[],[81,106,131,149,178,194],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":49},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[83,91,92,93,94,95,96,97,98,38,99,100,101,102,103,40,104,105],"user","download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":49},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[113,114,94,115,116,117,118,119,120,38,121,122,123,124,125,126,127,128,129,130],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","for","test plan","target","as","yagni",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":49},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[133,138,139,140,40,42,141,142,143,144,145,116,146,38,147,148],"implementation","workspace","with","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":49},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[159,160,161,162,163,164,165,166,167,38,168,169,170,171,172,173,174,175,176,177],"web","perf","web perf","resources","MCP","layout","optimize","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":49},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[180,124,185,186,145,116,187,188,38,189,40,190,191,192,193],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":49},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[201,202,203,204,205,206,207,38,208,40,209],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]