[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JDHMRCFJYP1SAGCJTC6Y1M":3,"skill-same:01M6JDHMRCFJYP1SAGCJTC6Y1M":70},{"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":25,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6JDHMRCFJYP1SAGCJTC6Y1M","search-first",null,"Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Invokes the researcher agent.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fsearch-first\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"search","first","search first","writing","research","workflow","libraries","code","Tools","coding","researcher","patterns","coding workflow","for","Existing","custom","2026-11-10 10:12:30",false,"---\nname: search-first\ndescription: Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Invokes the researcher agent.\norigin: ECC\n---\n\n# \u002Fsearch-first — Research Before You Code\n\nSystematizes the \"search for existing solutions before implementing\" workflow.\n\n## Trigger\n\nUse this skill when:\n- Starting a new feature that likely has existing solutions\n- Adding a dependency or integration\n- The user asks \"add X functionality\" and you're about to write code\n- Before creating a new utility, helper, or abstraction\n\n## Workflow\n\n```\n┌─────────────────────────────────────────────┐\n│  0. TOOL AVAILABILITY PREFLIGHT             │\n│     Check search channels before relying on │\n│     them; report skipped channels honestly   │\n├─────────────────────────────────────────────┤\n│  1. NEED ANALYSIS                           │\n│     Define what functionality is needed      │\n│     Identify language\u002Fframework constraints  │\n├─────────────────────────────────────────────┤\n│  2. PARALLEL SEARCH (researcher agent)      │\n│     ┌──────────┐ ┌──────────┐ ┌──────────┐  │\n│     │  npm \u002F   │ │  MCP \u002F   │ │  GitHub \u002F │  │\n│     │  PyPI    │ │  Skills  │ │  Web      │  │\n│     └──────────┘ └──────────┘ └──────────┘  │\n├─────────────────────────────────────────────┤\n│  3. EVALUATE                                │\n│     Score candidates (functionality, maint, │\n│     community, docs, license, deps)         │\n├─────────────────────────────────────────────┤\n│  4. DECIDE                                  │\n│     ┌─────────┐  ┌──────────┐  ┌─────────┐  │\n│     │  Adopt  │  │  Extend  │  │  Build   │  │\n│     │ as-is   │  │  \u002FWrap   │  │  Custom  │  │\n│     └─────────┘  └──────────┘  └─────────┘  │\n├─────────────────────────────────────────────┤\n│  5. IMPLEMENT                               │\n│     Install package \u002F Configure MCP \u002F       │\n│     Write minimal custom code               │\n└─────────────────────────────────────────────┘\n```\n\n## Decision Matrix\n\n| Signal | Action |\n|--------|--------|\n| Exact match, well-maintained, MIT\u002FApache | **Adopt** — install and use directly |\n| Partial match, good foundation | **Extend** — install + write thin wrapper |\n| Multiple weak matches | **Compose** — combine 2-3 small packages |\n| Nothing suitable found | **Build** — write custom, but informed by research |\n\n## How to Use\n\n### Step 0: Tool Availability Preflight\n\nThis is agent guidance, not an executable setup script. Check only the channels\nthat are relevant to the task and project in front of you.\n\n| Channel | Check | If missing |\n|---------|-------|------------|\n| Repository search | `rg --files` and targeted `rg` queries | State that only visible files were inspected |\n| Package registry | `npm --version`, `python -m pip --version`, or project package manager | Use web\u002Fdocs search and avoid claiming registry coverage |\n| GitHub CLI | `gh auth status` | Use public web or local git history only |\n| MCP\u002Fdocs tools | Available tool list or local MCP config | Fall back to official docs\u002Fweb search |\n| Skills directory | `ls ~\u002F.claude\u002Fskills ~\u002F.codex\u002Fskills` where applicable | Say no local skill catalog was available |\n\n### Quick Mode (inline)\n\nBefore writing a utility or adding functionality, mentally run through:\n\n0. Does this already exist in the repo? → `rg` through relevant modules\u002Ftests first\n1. Is this a common problem? → Search npm\u002FPyPI\n2. Is there an MCP for this? → Check `~\u002F.claude\u002Fsettings.json` and search\n3. Is there a skill for this? → Check `~\u002F.claude\u002Fskills\u002F`\n4. Is there a GitHub implementation\u002Ftemplate? → Run GitHub code search for maintained OSS before writing net-new code\n\n### Full Mode (agent)\n\nFor non-trivial functionality, launch the researcher agent:\n\n```\nAgent(subagent_type=\"general-purpose\", prompt=\"\n  Research existing tools for: [DESCRIPTION]\n  Language\u002Fframework: [LANG]\n  Constraints: [ANY]\n\n  Search: npm\u002FPyPI, MCP servers, Claude Code skills, GitHub\n  Return: Structured comparison with recommendation\n\")\n```\n\nOlder Claude Code docs may call this `Task(...)`; use the current agent\u002Fsubagent\ntool name exposed by the active harness.\n\n## Search Shortcuts by Category\n\n### Development Tooling\n- Linting → `eslint`, `ruff`, `textlint`, `markdownlint`\n- Formatting → `prettier`, `black`, `gofmt`\n- Testing → `jest`, `pytest`, `go test`\n- Pre-commit → `husky`, `lint-staged`, `pre-commit`\n\n### AI\u002FLLM Integration\n- Claude SDK → Context7 for latest docs\n- Prompt management → Check MCP servers\n- Document processing → `unstructured`, `pdfplumber`, `mammoth`\n\n### Data & APIs\n- HTTP clients → `httpx` (Python), `ky`\u002F`undici` (Node)\n- Validation → `zod` (TS), `pydantic` (Python)\n- Database → Check for MCP servers first\n\n### Content & Publishing\n- Markdown processing → `remark`, `unified`, `markdown-it`\n- Image optimization → `sharp`, `imagemin`\n\n## Integration Points\n\n### With planner agent\nThe planner should invoke researcher before Phase 1 (Architecture Review):\n- Researcher identifies available tools\n- Planner incorporates them into the implementation plan\n- Avoids \"reinventing the wheel\" in the plan\n\n### With architect agent\nThe architect should consult researcher for:\n- Technology stack decisions\n- Integration pattern discovery\n- Existing reference architectures\n\n### With iterative-retrieval skill\nCombine for progressive discovery:\n- Cycle 1: Broad search (npm, PyPI, MCP)\n- Cycle 2: Evaluate top candidates in detail\n- Cycle 3: Test compatibility with project constraints\n\n## Examples\n\n### Example 1: \"Add dead link checking\"\n```\nNeed: Check markdown files for broken links\nSearch: npm \"markdown dead link checker\"\nFound: textlint-rule-no-dead-link (score: 9\u002F10)\nAction: ADOPT — npm install textlint-rule-no-dead-link\nResult: Zero custom code, battle-tested solution\n```\n\n### Example 2: \"Add HTTP client wrapper\"\n```\nNeed: Resilient HTTP client with retries and timeout handling\nSearch: npm \"http client retry\", PyPI \"httpx retry\"\nFound: got (Node) with retry plugin, httpx (Python) with built-in retry\nAction: ADOPT — use got\u002Fhttpx directly with retry config\nResult: Zero custom code, production-proven libraries\n```\n\n### Example 3: \"Add config file linter\"\n```\nNeed: Validate project config files against a schema\nSearch: npm \"config linter schema\", \"json schema validator cli\"\nFound: ajv-cli (score: 8\u002F10)\nAction: ADOPT + EXTEND — install ajv-cli, write project-specific schema\nResult: 1 package + 1 schema file, no custom validation logic\n```\n\n## Anti-Patterns\n\n- **Jumping to code**: Writing a utility without checking if one exists\n- **Ignoring MCP**: Not checking if an MCP server already provides the capability\n- **Silent skipping**: Reporting \"nothing found\" when a search channel was unavailable\n- **Over-customizing**: Wrapping a library so heavily it loses its benefits\n- **Dependency bloat**: Installing a massive package for one small feature\n","# \u002Fsearch-first — Research Before You Code\n\nSystematizes the \"search for existing solutions before implementing\" workflow.\n\n## Trigger\n\nUse this skill when:\n- Starting a new feature that likely has existing solutions\n- Adding a dependency or integration\n- The user asks \"add X functionality\" and you're about to write code\n- Before creating a new utility, helper, or abstraction\n\n## Workflow\n\n```\n┌─────────────────────────────────────────────┐\n│  0. TOOL AVAILABILITY PREFLIGHT             │\n│     Check search channels before relying on │\n│     them; report skipped channels honestly   │\n├─────────────────────────────────────────────┤\n│  1. NEED ANALYSIS                           │\n│     Define what functionality is needed      │\n│     Identify language\u002Fframework constraints  │\n├─────────────────────────────────────────────┤\n│  2. PARALLEL SEARCH (researcher agent)      │\n│     ┌──────────┐ ┌──────────┐ ┌──────────┐  │\n│     │  npm \u002F   │ │  MCP \u002F   │ │  GitHub \u002F │  │\n│     │  PyPI    │ │  Skills  │ │  Web      │  │\n│     └──────────┘ └──────────┘ └──────────┘  │\n├─────────────────────────────────────────────┤\n│  3. EVALUATE                                │\n│     Score candidates (functionality, maint, │\n│     community, docs, license, deps)         │\n├─────────────────────────────────────────────┤\n│  4. DECIDE                                  │\n│     ┌─────────┐  ┌──────────┐  ┌─────────┐  │\n│     │  Adopt  │  │  Extend  │  │  Build   │  │\n│     │ as-is   │  │  \u002FWrap   │  │  Custom  │  │\n│     └─────────┘  └──────────┘  └─────────┘  │\n├─────────────────────────────────────────────┤\n│  5. IMPLEMENT                               │\n│     Install package \u002F Configure MCP \u002F       │\n│     Write minimal custom code               │\n└─────────────────────────────────────────────┘\n```\n\n## Decision Matrix\n\n| Signal | Action |\n|--------|--------|\n| Exact match, well-maintained, MIT\u002FApache | **Adopt** — install and use directly |\n| Partial match, good foundation | **Extend** — install + write thin wrapper |\n| Multiple weak matches | **Compose** — combine 2-3 small packages |\n| Nothing suitable found | **Build** — write custom, but informed by research |\n\n## How to Use\n\n### Step 0: Tool Availability Preflight\n\nThis is agent guidance, not an executable setup script. Check only the channels\nthat are relevant to the task and project in front of you.\n\n| Channel | Check | If missing |\n|---------|-------|------------|\n| Repository search | `rg --files` and targeted `rg` queries | State that only visible files were inspected |\n| Package registry | `npm --version`, `python -m pip --version`, or project package manager | Use web\u002Fdocs search and avoid claiming registry coverage |\n| GitHub CLI | `gh auth status` | Use public web or local git history only |\n| MCP\u002Fdocs tools | Available tool list or local MCP config | Fall back to official docs\u002Fweb search |\n| Skills directory | `ls ~\u002F.claude\u002Fskills ~\u002F.codex\u002Fskills` where applicable | Say no local skill catalog was available |\n\n### Quick Mode (inline)\n\nBefore writing a utility or adding functionality, mentally run through:\n\n0. Does this already exist in the repo? → `rg` through relevant modules\u002Ftests first\n1. Is this a common problem? → Search npm\u002FPyPI\n2. Is there an MCP for this? → Check `~\u002F.claude\u002Fsettings.json` and search\n3. Is there a skill for this? → Check `~\u002F.claude\u002Fskills\u002F`\n4. Is there a GitHub implementation\u002Ftemplate? → Run GitHub code search for maintained OSS before writing net-new code\n\n### Full Mode (agent)\n\nFor non-trivial functionality, launch the researcher agent:\n\n```\nAgent(subagent_type=\"general-purpose\", prompt=\"\n  Research existing tools for: [DESCRIPTION]\n  Language\u002Fframework: [LANG]\n  Constraints: [ANY]\n\n  Search: npm\u002FPyPI, MCP servers, Claude Code skills, GitHub\n  Return: Structured comparison with recommendation\n\")\n```\n\nOlder Claude Code docs may call this `Task(...)`; use the current agent\u002Fsubagent\ntool name exposed by the active harness.\n\n## Search Shortcuts by Category\n\n### Development Tooling\n- Linting → `eslint`, `ruff`, `textlint`, `markdownlint`\n- Formatting → `prettier`, `black`, `gofmt`\n- Testing → `jest`, `pytest`, `go test`\n- Pre-commit → `husky`, `lint-staged`, `pre-commit`\n\n### AI\u002FLLM Integration\n- Claude SDK → Context7 for latest docs\n- Prompt management → Check MCP servers\n- Document processing → `unstructured`, `pdfplumber`, `mammoth`\n\n### Data & APIs\n- HTTP clients → `httpx` (Python), `ky`\u002F`undici` (Node)\n- Validation → `zod` (TS), `pydantic` (Python)\n- Database → Check for MCP servers first\n\n### Content & Publishing\n- Markdown processing → `remark`, `unified`, `markdown-it`\n- Image optimization → `sharp`, `imagemin`\n\n## Integration Points\n\n### With planner agent\nThe planner should invoke researcher before Phase 1 (Architecture Review):\n- Researcher identifies available tools\n- Planner incorporates them into the implementation plan\n- Avoids \"reinventing the wheel\" in the plan\n\n### With architect agent\nThe architect should consult researcher for:\n- Technology stack decisions\n- Integration pattern discovery\n- Existing reference architectures\n\n### With iterative-retrieval skill\nCombine for progressive discovery:\n- Cycle 1: Broad search (npm, PyPI, MCP)\n- Cycle 2: Evaluate top candidates in detail\n- Cycle 3: Test compatibility with project constraints\n\n## Examples\n\n### Example 1: \"Add dead link checking\"\n```\nNeed: Check markdown files for broken links\nSearch: npm \"markdown dead link checker\"\nFound: textlint-rule-no-dead-link (score: 9\u002F10)\nAction: ADOPT — npm install textlint-rule-no-dead-link\nResult: Zero custom code, battle-tested solution\n```\n\n### Example 2: \"Add HTTP client wrapper\"\n```\nNeed: Resilient HTTP client with retries and timeout handling\nSearch: npm \"http client retry\", PyPI \"httpx retry\"\nFound: got (Node) with retry plugin, httpx (Python) with built-in retry\nAction: ADOPT — use got\u002Fhttpx directly with retry config\nResult: Zero custom code, production-proven libraries\n```\n\n### Example 3: \"Add config file linter\"\n```\nNeed: Validate project config files against a schema\nSearch: npm \"config linter schema\", \"json schema validator cli\"\nFound: ajv-cli (score: 8\u002F10)\nAction: ADOPT + EXTEND — install ajv-cli, write project-specific schema\nResult: 1 package + 1 schema file, no custom validation logic\n```\n\n## Anti-Patterns\n\n- **Jumping to code**: Writing a utility without checking if one exists\n- **Ignoring MCP**: Not checking if an MCP server already provides the capability\n- **Silent skipping**: Reporting \"nothing found\" when a search channel was unavailable\n- **Over-customizing**: Wrapping a library so heavily it loses its benefits\n- **Dependency bloat**: Installing a massive package for one small feature\n",{"name":5,"origin":47,"description":7},"ECC","master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fecc\u002Fsearch-first",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add S3YED\u002Fappie-kit --skill search-first",{"tool":62,"command":63},"bunx","bunx skills add S3YED\u002Fappie-kit --skill search-first",{"tool":65,"command":66},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill search-first","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fsearch-first\u002FSKILL.md",true,[],[71,102,137,162,193,215],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":84,"publishedAt":42},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[77,80,83],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":81,"categoryName":82,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[85,86,87,88,34,89,90,91,92,93,94,95,96,97,98,99,100,101],"music","ai music","humanizer","visualization","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":116,"publishedAt":42},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[108,111],{"categoryNo":109,"categoryName":110,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":145,"publishedAt":42},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[143,144],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},[118,146,122,147,148,149,124,150,26,151,152,153,154,155,156,157,158,159,160,161],"elements","agentic webdesign agent elements","MCP","ai agent","registry","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":172,"publishedAt":42},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[168,171],{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":200,"publishedAt":42},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[199],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[201,202,203,204,205,206,31,207,208,33,209,210,211,212,213,214,39],"workflows","quality","software","software quality workflows","review","tdd","commit","debugging","debugger","pre-commit","investigation","code simplification","user","simplification",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":228,"publishedAt":42},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[221,224,227],{"categoryNo":222,"categoryName":223,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":225,"categoryName":226,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[229,230,231,232,233,234,235,29,176,236,237,124,238,179,239,33,240,241,37,242],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","safe","typescript","react components","modular","refactor","simplify","test-driven-development"]