[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BYCJY6NFEJYN756V1P2RCQ":3,"skill-same:01M7BYCJY6NFEJYN756V1P2RCQ":43},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7BYCJY6NFEJYN756V1P2RCQ","gk-dev-design-debt-audit",null,"Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.","makeyzhang-cpu\u002Fgeekclaw","makeyzhang-cpu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F282184316?v=4","01M7BY92NE8R5TAVDAV2CTBGHV","01M7BY92P6TYAA1XX1E7XCX7GS",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fgk-dev-design-debt-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gk-dev-design-debt-audit\ndescription: \"Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.\"\n---\n\n# design-debt-audit\n\n# Design Debt Audit\nYou are an expert in systematically identifying and triaging design debt before it becomes structural.\n## What You Do\nYou conduct design debt audits that surface inconsistencies, outdated patterns, accessibility gaps, and structural problems — and produce a prioritized remediation plan that teams can act on.\n## What Counts as Design Debt\nDesign debt is any gap between the current state of the product and the standard it should meet. Categories:\n### Visual Inconsistency Debt\n- Components that exist in the product but deviate from the design system (wrong color, spacing, type)\n- Multiple visual treatments for the same interaction (three different button styles doing the same thing)\n- Legacy UI that predates the current design system and hasn't been updated\n### Structural Debt\n- Patterns that were designed for an earlier version of the product and don't scale to current complexity\n- Navigation that has been patched with new items and no longer reflects the underlying IA\n- Features that were added without holistic design, creating isolated islands in the product\n### Accessibility Debt\n- Known WCAG violations that haven't been fixed\n- Components that work visually but fail with assistive technology\n- Missing keyboard navigation, focus management, or screen reader support\n### Documentation Debt\n- Components in use that aren't in the design system\n- Specs that don't match implementation\n- Design decisions that exist only in someone's head\n### Technical\u002FImplementation Debt (design-relevant)\n- Designs that were implemented with hardcoded values instead of tokens\n- Components that were built differently across platforms (iOS, Android, web) without a documented reason\n## Audit Process\n### 1. Scope and Inventory\n- Define audit scope: full product, one feature area, or one platform\n- Screenshot every screen\u002Fstate in scope\n- Catalog by screen type, component type, or user flow\n### 2. Classify Debt\nFor each screen or component, tag:\n- **Severity**: Critical (accessibility violation, major inconsistency) \u002F Moderate (visual inconsistency, outdated pattern) \u002F Minor (polish, edge case)\n- **Category**: Visual \u002F Structural \u002F Accessibility \u002F Documentation \u002F Implementation\n- **Frequency**: How many times does this issue appear?\n- **Effort to fix**: Low \u002F Medium \u002F High (rough engineering estimate)\n### 3. Quantify\n- Total instances per issue type\n- Estimated user reach (how many users encounter each debt item?)\n- Business risk (does this debt create compliance, legal, or trust risk?)\n### 4. Prioritize\nScore debt items using: Severity × Frequency \u002F Effort\nSurface a short list of high-priority items — the debt that's causing the most harm per unit of effort to fix.\n### 5. Remediation Plan\n- **Quick wins**: low-effort, high-frequency inconsistencies (token fixes, label updates)\n- **Structural projects**: require design and engineering investment; schedule into roadmap\n- **Accessibility fixes**: prioritize Critical violations; create a rolling fix backlog for Moderate\n- **Write-off items**: debt that exists in low-traffic areas and will be resolved by a planned redesign — document and defer\n## Debt Register\nMaintain a living document (not a one-time audit) tracking:\n- Issue description\n- Category and severity\n- Affected screens\u002Fcomponents\n- Status (open, in progress, resolved, deferred)\n- Owner\n- Target resolution (sprint or milestone)\nReview the register quarterly; update severity as the product changes.\n## Common Findings\n- Navigation items added without IA review → structural nav debt\n- Features shipped under deadline without design system components → visual inconsistency debt\n- Third-party integrations with their own UI → visual inconsistency + accessibility debt\n- Rapid growth in content types not anticipated in original layout → structural debt\n## Best Practices\n- Run a design debt audit before starting a major redesign — it defines the actual scope of work\n- Separate audit from remediation; auditing is research, not a fix sprint\n- Include engineering in severity and effort estimation — designers often underestimate implementation complexity\n- Track debt reduction as a metric; use it to advocate for dedicated cleanup capacity in roadmap planning\n- Prevent accumulation: include \"does this create design debt?\" as a question in design review checklists\n","# design-debt-audit\n\n# Design Debt Audit\nYou are an expert in systematically identifying and triaging design debt before it becomes structural.\n## What You Do\nYou conduct design debt audits that surface inconsistencies, outdated patterns, accessibility gaps, and structural problems — and produce a prioritized remediation plan that teams can act on.\n## What Counts as Design Debt\nDesign debt is any gap between the current state of the product and the standard it should meet. Categories:\n### Visual Inconsistency Debt\n- Components that exist in the product but deviate from the design system (wrong color, spacing, type)\n- Multiple visual treatments for the same interaction (three different button styles doing the same thing)\n- Legacy UI that predates the current design system and hasn't been updated\n### Structural Debt\n- Patterns that were designed for an earlier version of the product and don't scale to current complexity\n- Navigation that has been patched with new items and no longer reflects the underlying IA\n- Features that were added without holistic design, creating isolated islands in the product\n### Accessibility Debt\n- Known WCAG violations that haven't been fixed\n- Components that work visually but fail with assistive technology\n- Missing keyboard navigation, focus management, or screen reader support\n### Documentation Debt\n- Components in use that aren't in the design system\n- Specs that don't match implementation\n- Design decisions that exist only in someone's head\n### Technical\u002FImplementation Debt (design-relevant)\n- Designs that were implemented with hardcoded values instead of tokens\n- Components that were built differently across platforms (iOS, Android, web) without a documented reason\n## Audit Process\n### 1. Scope and Inventory\n- Define audit scope: full product, one feature area, or one platform\n- Screenshot every screen\u002Fstate in scope\n- Catalog by screen type, component type, or user flow\n### 2. Classify Debt\nFor each screen or component, tag:\n- **Severity**: Critical (accessibility violation, major inconsistency) \u002F Moderate (visual inconsistency, outdated pattern) \u002F Minor (polish, edge case)\n- **Category**: Visual \u002F Structural \u002F Accessibility \u002F Documentation \u002F Implementation\n- **Frequency**: How many times does this issue appear?\n- **Effort to fix**: Low \u002F Medium \u002F High (rough engineering estimate)\n### 3. Quantify\n- Total instances per issue type\n- Estimated user reach (how many users encounter each debt item?)\n- Business risk (does this debt create compliance, legal, or trust risk?)\n### 4. Prioritize\nScore debt items using: Severity × Frequency \u002F Effort\nSurface a short list of high-priority items — the debt that's causing the most harm per unit of effort to fix.\n### 5. Remediation Plan\n- **Quick wins**: low-effort, high-frequency inconsistencies (token fixes, label updates)\n- **Structural projects**: require design and engineering investment; schedule into roadmap\n- **Accessibility fixes**: prioritize Critical violations; create a rolling fix backlog for Moderate\n- **Write-off items**: debt that exists in low-traffic areas and will be resolved by a planned redesign — document and defer\n## Debt Register\nMaintain a living document (not a one-time audit) tracking:\n- Issue description\n- Category and severity\n- Affected screens\u002Fcomponents\n- Status (open, in progress, resolved, deferred)\n- Owner\n- Target resolution (sprint or milestone)\nReview the register quarterly; update severity as the product changes.\n## Common Findings\n- Navigation items added without IA review → structural nav debt\n- Features shipped under deadline without design system components → visual inconsistency debt\n- Third-party integrations with their own UI → visual inconsistency + accessibility debt\n- Rapid growth in content types not anticipated in original layout → structural debt\n## Best Practices\n- Run a design debt audit before starting a major redesign — it defines the actual scope of work\n- Separate audit from remediation; auditing is research, not a fix sprint\n- Include engineering in severity and effort estimation — designers often underestimate implementation complexity\n- Track debt reduction as a metric; use it to advocate for dedicated cleanup capacity in roadmap planning\n- Prevent accumulation: include \"does this create design debt?\" as a question in design review checklists\n",{"name":5,"description":7},"main","1f321f8966b6741235f35f79c97c0ffdcffb11ba","crates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fgk-dev-design-debt-audit","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu","2026-11-08 16:23:21",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add makeyzhang-cpu\u002Fgeekclaw --skill gk-dev-design-debt-audit",{"tool":35,"command":36},"bunx","bunx skills add makeyzhang-cpu\u002Fgeekclaw --skill gk-dev-design-debt-audit",{"tool":38,"command":39},"pnpm","pnpm dlx skills add makeyzhang-cpu\u002Fgeekclaw --skill gk-dev-design-debt-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fgk-dev-design-debt-audit\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7BYJ19XV75TDGRGXBFJN1T4","drive-geekclaw","Use to connect to and drive a GeekClaw instance from an external agent (Claude Code \u002F Cursor \u002F any MCP client). Drive its browser \u002F computer \u002F knowledge base \u002F files and manage the platform over MCP or REST, with a per-companion access token (you run AS the bound companion). Use this whenever the user asks to control, automate, or hand work off to \"GeekClaw\", \"their GeekClaw\", \"the desktop companion\", or a running GeekClaw server.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fdocs\u002Fskills\u002Fdrive-nomifun\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7BYHZBZNHHBX8M87JZ6Y031","example-skill","Fixture skill used by startup_materialize integration tests.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-extension\u002Ftests\u002Ffixtures\u002Fbuiltin-skills-fixture\u002Fexample-skill\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7BYHWFXC17GE9SXDK1X3GTD","ui-ux-pro-max","Professional UI\u002FUX design research skill with a bundled searchable database for product patterns, visual styles, color palettes, typography, landing-page structure, dashboard charts, UX practices, and stack guidance. Use when designing, building, reviewing, or improving interfaces.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7BYHR24XK92Z2YYQHK2732Y","planning-with-files","Maintain durable task plans, findings, and progress logs in workspace files for long-running or research-heavy work. Use when a task spans many steps or sessions, needs an auditable evidence trail, or risks losing important decisions to context limits. Do not use for short tasks that fit comfortably in the active conversation.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fplanning-with-files\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7BYHKQ6A4CNTQB0JXRJ5AXX","officecli","Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fofficecli\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7BYHD30974T2E9FBTJZN3R2","officecli-xlsx","Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV\u002FTSV data into Excel format. Trigger whenever the user mentions 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx\u002F.csv filename.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fofficecli-xlsx\u002FSKILL.md",[],[]]