[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JKDMKCAJZPEWFPJRWGEKWV":3,"skill-same:01M6JKDMKCAJZPEWFPJRWGEKWV":68},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":67},"01M6JKDMKCAJZPEWFPJRWGEKWV","tech-debt",null,"Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.","LongLeo287\u002FOmniClaw","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M6JK75GQ78TSP1ZPXNKK3MCH",9,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fbrain\u002Fknowledge\u002Frepositories\u002Fclaude_code_game_studios\u002F.claude\u002Fskills\u002Ftech_debt\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"tech","tech debt","scheduling","codebase","for","true","add","register","technical debt","across","scan","report","categorize","write","read","technical","grep","prioritize","indicators","2026-11-10 10:12:30",false,"---\nname: tech-debt\ndescription: \"Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.\"\nargument-hint: \"[scan|add|prioritize|report]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Write\n---\nWhen this skill is invoked:\n\n1. **Parse the subcommand** from the argument:\n   - `scan` — Scan the codebase for tech debt indicators\n   - `add` — Add a new tech debt entry manually\n   - `prioritize` — Re-prioritize the existing debt register\n   - `report` — Generate a summary report of current debt status\n\n2. **For `scan`**:\n   - Search the codebase for debt indicators:\n     - `TODO` comments (count and categorize)\n     - `FIXME` comments (these are bugs disguised as debt)\n     - `HACK` comments (workarounds that need proper solutions)\n     - `@deprecated` markers\n     - Duplicated code blocks (similar patterns in multiple files)\n     - Files over 500 lines (potential god objects)\n     - Functions over 50 lines (potential complexity)\n   - Categorize each finding:\n     - **Architecture Debt**: Wrong abstractions, missing patterns, coupling issues\n     - **Code Quality Debt**: Duplication, complexity, naming, missing types\n     - **Test Debt**: Missing tests, flaky tests, untested edge cases\n     - **Documentation Debt**: Missing docs, outdated docs, undocumented APIs\n     - **Dependency Debt**: Outdated packages, deprecated APIs, version conflicts\n     - **Performance Debt**: Known slow paths, unoptimized queries, memory issues\n   - Update the debt register at `docs\u002Ftech-debt-register.md`\n\n3. **For `add`**:\n   - Prompt for: description, category, affected files, estimated fix effort, impact if left unfixed\n   - Append to the debt register\n\n4. **For `prioritize`**:\n   - Read the debt register\n   - Score each item by: `(impact_if_unfixed * frequency_of_encounter) \u002F fix_effort`\n   - Re-sort the register by priority score\n   - Recommend which items to include in the next sprint\n\n5. **For `report`**:\n   - Read the debt register\n   - Generate summary statistics:\n     - Total items by category\n     - Total estimated fix effort\n     - Items added vs resolved since last report\n     - Trending direction (growing \u002F stable \u002F shrinking)\n   - Flag any items that have been in the register for more than 3 sprints\n   - Output the report\n\n### Debt Register Format\n\n```markdown\n## Technical Debt Register\nLast updated: [Date]\nTotal items: [N] | Estimated total effort: [T-shirt sizes summed]\n\n| ID | Category | Description | Files | Effort | Impact | Priority | Added | Sprint |\n|----|----------|-------------|-------|--------|--------|----------|-------|--------|\n| TD-001 | [Cat] | [Description] | [files] | [S\u002FM\u002FL\u002FXL] | [Low\u002FMed\u002FHigh\u002FCritical] | [Score] | [Date] | [Sprint to fix or \"Backlog\"] |\n```\n\n### Rules\n- Tech debt is not inherently bad — it is a tool. The register tracks conscious decisions.\n- Every debt entry must explain WHY it was accepted (deadline, prototype, missing info)\n- \"Scan\" should run at least once per sprint to catch new debt\n- Items older than 3 sprints without action should either be fixed or consciously accepted with a documented reason\n","When this skill is invoked:\n\n1. **Parse the subcommand** from the argument:\n   - `scan` — Scan the codebase for tech debt indicators\n   - `add` — Add a new tech debt entry manually\n   - `prioritize` — Re-prioritize the existing debt register\n   - `report` — Generate a summary report of current debt status\n\n2. **For `scan`**:\n   - Search the codebase for debt indicators:\n     - `TODO` comments (count and categorize)\n     - `FIXME` comments (these are bugs disguised as debt)\n     - `HACK` comments (workarounds that need proper solutions)\n     - `@deprecated` markers\n     - Duplicated code blocks (similar patterns in multiple files)\n     - Files over 500 lines (potential god objects)\n     - Functions over 50 lines (potential complexity)\n   - Categorize each finding:\n     - **Architecture Debt**: Wrong abstractions, missing patterns, coupling issues\n     - **Code Quality Debt**: Duplication, complexity, naming, missing types\n     - **Test Debt**: Missing tests, flaky tests, untested edge cases\n     - **Documentation Debt**: Missing docs, outdated docs, undocumented APIs\n     - **Dependency Debt**: Outdated packages, deprecated APIs, version conflicts\n     - **Performance Debt**: Known slow paths, unoptimized queries, memory issues\n   - Update the debt register at `docs\u002Ftech-debt-register.md`\n\n3. **For `add`**:\n   - Prompt for: description, category, affected files, estimated fix effort, impact if left unfixed\n   - Append to the debt register\n\n4. **For `prioritize`**:\n   - Read the debt register\n   - Score each item by: `(impact_if_unfixed * frequency_of_encounter) \u002F fix_effort`\n   - Re-sort the register by priority score\n   - Recommend which items to include in the next sprint\n\n5. **For `report`**:\n   - Read the debt register\n   - Generate summary statistics:\n     - Total items by category\n     - Total estimated fix effort\n     - Items added vs resolved since last report\n     - Trending direction (growing \u002F stable \u002F shrinking)\n   - Flag any items that have been in the register for more than 3 sprints\n   - Output the report\n\n### Debt Register Format\n\n```markdown\n## Technical Debt Register\nLast updated: [Date]\nTotal items: [N] | Estimated total effort: [T-shirt sizes summed]\n\n| ID | Category | Description | Files | Effort | Impact | Priority | Added | Sprint |\n|----|----------|-------------|-------|--------|--------|----------|-------|--------|\n| TD-001 | [Cat] | [Description] | [files] | [S\u002FM\u002FL\u002FXL] | [Low\u002FMed\u002FHigh\u002FCritical] | [Score] | [Date] | [Sprint to fix or \"Backlog\"] |\n```\n\n### Rules\n- Tech debt is not inherently bad — it is a tool. The register tracks conscious decisions.\n- Every debt entry must explain WHY it was accepted (deadline, prototype, missing info)\n- \"Scan\" should run at least once per sprint to catch new debt\n- Items older than 3 sprints without action should either be fixed or consciously accepted with a documented reason\n",{"name":5,"description":7,"allowed-tools":43,"argument-hint":44,"user-invocable":45},"Read, Glob, Grep, Write","[scan|add|prioritize|report]",true,"main","c173cdffe08e788a99b91928a831b476b8434838","brain\u002Fknowledge\u002Frepositories\u002Fclaude_code_game_studios\u002F.claude\u002Fskills\u002Ftech_debt",0,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw","https:\u002F\u002Fportfolio-longleo.vercel.app\u002Flabs\u002Fomniclaw.html","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-09-30 00:58:05",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":45},[57,60,63],{"tool":58,"command":59},"npx","npx skills add LongLeo287\u002FOmniClaw --skill tech-debt",{"tool":61,"command":62},"bunx","bunx skills add LongLeo287\u002FOmniClaw --skill tech-debt",{"tool":64,"command":65},"pnpm","pnpm dlx skills add LongLeo287\u002FOmniClaw --skill tech-debt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fbrain\u002Fknowledge\u002Frepositories\u002Fclaude_code_game_studios\u002F.claude\u002Fskills\u002Ftech_debt\u002FSKILL.md",[],[69,112,133,161,177,204],{"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":91,"publishedAt":38},"01M6JR0KQP4MHT32TN40D9CBFX","UI-UX Pro Max","Advanced UI\u002FUX analysis and generation skills with data-driven patterns. Python scripts (core.py, search.py) for systematic UI pattern extraction, design system generation, and component search from curated data sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fui_ux_pro_max\u002FSKILL.md",[75,80,83,88],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":81,"categoryName":82,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000033","数据分析师",[92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111],"ux","ui","ui ux pro max","max","pro","ui ux","design","component","search","analysis","team","rd","ui-ux","active","systematic","scripts","pattern extraction","sources","advanced","data-driven",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":38},"01M6JR0EF5AEQHP2FSTB57H05P","shadcn-ui","Expert guidance for integrating and building applications with shadcn\u002Fui components, including component discovery, installation, customization, and best practices.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fshadcn_ui\u002FSKILL.md",[118],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},[120,93,121,122,99,123,124,125,126,102,127,128,129,105,130,131,132,23],"shadcn","shadcn ui","components","core","best practices","applications","discovery","customization","guidance","expert","installation","ui components","with",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":142,"publishedAt":38},"01M6JR08F51BEN17RHFYX65WVE","zustand_store_ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand_store_ts\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000009","前端开发",[143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,132,159,160],"zustand store ts","zustand","store","typescript","microsoft","react","create","state management","state","react state management","management","global","use","patterns","separation","middleware","action","implementing",{"skillNo":162,"name":144,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":38},"01M6JR00TDMVAFFCZXZ04AN7Q7","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand\u002FSKILL.md",[],[144,167,150,168,151,169,170,153,171,155,172,173,174,145,132,175,176,159,160],"development","code","actions","src","guide","implementation","zustand state","triggers","questions","zustand state management",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":187,"publishedAt":38},"01M6JQZSWV4KWJP112G6XHEP44","youtube_summarizer","Automatically fetch YouTube video transcripts, generate structured summaries, and send full transcripts to messaging platforms. Detects YouTube URLs and provides metadata, key insights, and downloadable transcripts.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_summarizer\u002FSKILL.md",[183,186],{"categoryNo":184,"categoryName":185,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":81,"categoryName":82,"taxonomyType":78,"taxonomyTypeDesc":79},[188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203],"youtube","youtube summarizer","summarizer","generate","metadata","messaging","Video","fetch","telegram","transcription","summarization","structured","full","insights","transcripts","summaries",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":210,"publishedAt":38},"01M6JQZN3QJB6B77JGKJD62DQT","youtube_clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_clipper\u002FSKILL.md",[],[188,211,212,194,213,214,215,216,217,218,33,32,219,220,221,222,223],"clipper","youtube clipper","Bash","下载","视频","生成","关键词","翻译","clip","总结","工具","文案","sonnet"]