[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF5QCB7HXYZBZGYN4HESKQ":3,"skill-same:01M6AF5QCB7HXYZBZGYN4HESKQ":74},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6AF5QCB7HXYZBZGYN4HESKQ","code-simplifier",null,"Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to \"simplify code\", \"clean up code\", \"refactor for clarity\", \"improve readability\", or review recently modified code for elegance. Focuses on project-specific best practices.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fcode-simplifier\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"code","code simplifier","simplifier","when","review","unknown","for","consistency","maintainability","project","community","clean","simplify code","up","use","clarity","improve","simplify","refactor","best practices","2026-11-10 10:12:30",false,"---\nname: code-simplifier\ndescription: Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to \"simplify code\", \"clean up code\", \"refactor for clarity\", \"improve readability\", or review recently modified code for elegance. Focuses on project-specific best practices.\nmetadata:\n  risk: unknown\n  source: community\n---\n\n\u003C!--\nBased on Anthropic's code-simplifier agent:\nhttps:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-official\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-simplifier\u002Fagents\u002Fcode-simplifier.md\n-->\n\n# Code Simplifier\n\nYou are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions.\n\n## Refinement Principles\n\n### 1. Preserve Functionality\n\nNever change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.\n\n### 2. Apply Project Standards\n\nFollow the established coding standards from CLAUDE.md including:\n\n- Use ES modules with proper import sorting and extensions\n- Prefer `function` keyword over arrow functions\n- Use explicit return type annotations for top-level functions\n- Follow proper React component patterns with explicit Props types\n- Use proper error handling patterns (avoid try\u002Fcatch when possible)\n- Maintain consistent naming conventions\n\n### 3. Enhance Clarity\n\nSimplify code structure by:\n\n- Reducing unnecessary complexity and nesting\n- Eliminating redundant code and abstractions\n- Improving readability through clear variable and function names\n- Consolidating related logic\n- Removing unnecessary comments that describe obvious code\n- **Avoiding nested ternary operators** - prefer switch statements or if\u002Felse chains for multiple conditions\n- Choosing clarity over brevity - explicit code is often better than overly compact code\n\n### 4. Maintain Balance\n\nAvoid over-simplification that could:\n\n- Reduce code clarity or maintainability\n- Create overly clever solutions that are hard to understand\n- Combine too many concerns into single functions or components\n- Remove helpful abstractions that improve code organization\n- Prioritize \"fewer lines\" over readability (e.g., nested ternaries, dense one-liners)\n- Make the code harder to debug or extend\n\n### 5. Focus Scope\n\nOnly refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.\n\n## Refinement Process\n\n1. **Identify** the recently modified code sections\n2. **Analyze** for opportunities to improve elegance and consistency\n3. **Apply** project-specific best practices and coding standards\n4. **Ensure** all functionality remains unchanged\n5. **Verify** the refined code is simpler and more maintainable\n6. **Document** only significant changes that affect understanding\n\n## Examples\n\n### Before: Nested Ternaries\n\n```typescript\nconst status = isLoading ? 'loading' : hasError ? 'error' : isComplete ? 'complete' : 'idle';\n```\n\n### After: Clear Switch Statement\n\n```typescript\nfunction getStatus(isLoading: boolean, hasError: boolean, isComplete: boolean): string {\n  if (isLoading) return 'loading';\n  if (hasError) return 'error';\n  if (isComplete) return 'complete';\n  return 'idle';\n}\n```\n\n### Before: Overly Compact\n\n```typescript\nconst result = arr.filter(x => x > 0).map(x => x * 2).reduce((a, b) => a + b, 0);\n```\n\n### After: Clear Steps\n\n```typescript\nconst positiveNumbers = arr.filter(x => x > 0);\nconst doubled = positiveNumbers.map(x => x * 2);\nconst sum = doubled.reduce((a, b) => a + b, 0);\n```\n\n### Before: Redundant Abstraction\n\n```typescript\nfunction isNotEmpty(arr: unknown[]): boolean {\n  return arr.length > 0;\n}\n\nif (isNotEmpty(items)) {\n  \u002F\u002F ...\n}\n```\n\n### After: Direct Check\n\n```typescript\nif (items.length > 0) {\n  \u002F\u002F ...\n}\n```\n","\u003C!--\nBased on Anthropic's code-simplifier agent:\nhttps:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-plugins-official\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-simplifier\u002Fagents\u002Fcode-simplifier.md\n-->\n\n# Code Simplifier\n\nYou are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions.\n\n## Refinement Principles\n\n### 1. Preserve Functionality\n\nNever change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.\n\n### 2. Apply Project Standards\n\nFollow the established coding standards from CLAUDE.md including:\n\n- Use ES modules with proper import sorting and extensions\n- Prefer `function` keyword over arrow functions\n- Use explicit return type annotations for top-level functions\n- Follow proper React component patterns with explicit Props types\n- Use proper error handling patterns (avoid try\u002Fcatch when possible)\n- Maintain consistent naming conventions\n\n### 3. Enhance Clarity\n\nSimplify code structure by:\n\n- Reducing unnecessary complexity and nesting\n- Eliminating redundant code and abstractions\n- Improving readability through clear variable and function names\n- Consolidating related logic\n- Removing unnecessary comments that describe obvious code\n- **Avoiding nested ternary operators** - prefer switch statements or if\u002Felse chains for multiple conditions\n- Choosing clarity over brevity - explicit code is often better than overly compact code\n\n### 4. Maintain Balance\n\nAvoid over-simplification that could:\n\n- Reduce code clarity or maintainability\n- Create overly clever solutions that are hard to understand\n- Combine too many concerns into single functions or components\n- Remove helpful abstractions that improve code organization\n- Prioritize \"fewer lines\" over readability (e.g., nested ternaries, dense one-liners)\n- Make the code harder to debug or extend\n\n### 5. Focus Scope\n\nOnly refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.\n\n## Refinement Process\n\n1. **Identify** the recently modified code sections\n2. **Analyze** for opportunities to improve elegance and consistency\n3. **Apply** project-specific best practices and coding standards\n4. **Ensure** all functionality remains unchanged\n5. **Verify** the refined code is simpler and more maintainable\n6. **Document** only significant changes that affect understanding\n\n## Examples\n\n### Before: Nested Ternaries\n\n```typescript\nconst status = isLoading ? 'loading' : hasError ? 'error' : isComplete ? 'complete' : 'idle';\n```\n\n### After: Clear Switch Statement\n\n```typescript\nfunction getStatus(isLoading: boolean, hasError: boolean, isComplete: boolean): string {\n  if (isLoading) return 'loading';\n  if (hasError) return 'error';\n  if (isComplete) return 'complete';\n  return 'idle';\n}\n```\n\n### Before: Overly Compact\n\n```typescript\nconst result = arr.filter(x => x > 0).map(x => x * 2).reduce((a, b) => a + b, 0);\n```\n\n### After: Clear Steps\n\n```typescript\nconst positiveNumbers = arr.filter(x => x > 0);\nconst doubled = positiveNumbers.map(x => x * 2);\nconst sum = doubled.reduce((a, b) => a + b, 0);\n```\n\n### Before: Redundant Abstraction\n\n```typescript\nfunction isNotEmpty(arr: unknown[]): boolean {\n  return arr.length > 0;\n}\n\nif (isNotEmpty(items)) {\n  \u002F\u002F ...\n}\n```\n\n### After: Direct Check\n\n```typescript\nif (items.length > 0) {\n  \u002F\u002F ...\n}\n```\n",{"name":5,"metadata":49,"description":7},{"risk":29,"source":34},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fcode-simplifier",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add davila7\u002Fclaude-code-templates --skill code-simplifier",{"tool":66,"command":67},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill code-simplifier",{"tool":69,"command":70},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill code-simplifier","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fcode-simplifier\u002FSKILL.md",true,[],[75,104,129,160,195,219],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":44},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[87,88,89,90,91,30,92,93,38,27,94,95,96,97,98,99,100,101,102,103],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":44},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[110],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[112,113,114,115,116,117,118,119,33,120,121,27,24,122,123,124,125,126,127,128],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","cleanup","unused","todo","work","plan","focus","signals","audit","dependency",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":142,"publishedAt":44},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[135,138,139],{"categoryNo":136,"categoryName":137,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[143,144,145,146,147,148,149,30,150,151,152,153,154,155,156,38,157,158,27,159],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":44},"01M6AFY6F7CC2BBZP1QD6VTNVC","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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000009","前端开发",[172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,30,194],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":199,"sourceHtmlUrl":200,"categories":201,"keywords":206,"publishedAt":44},"01M6AFWF33SFV9Z3SF4PEEE4BF","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.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[202,205],{"categoryNo":203,"categoryName":204,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":169,"categoryName":170,"taxonomyType":84,"taxonomyTypeDesc":85},[207,208,209,210,211,173,212,182,183,213,214,215,216,30,217,95,218],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":164,"licenseFileUrl":223,"sourceHtmlUrl":224,"categories":225,"keywords":233,"publishedAt":44},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[226,229,230],{"categoryNo":227,"categoryName":228,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":231,"categoryName":232,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[234,235,236,237,238,239,240,241,175,242,185,24,243,28,244,245,37,155,246,27,247,248,249,250,251,101,252],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","conversation","short","invoke","you","analysis","claims","argument","assemble","recommendations"]