[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72XRE2ADGS6TT3K7BRB43TM":3,"skill-same:01M72XRE2ADGS6TT3K7BRB43TM":50},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M72XRE2ADGS6TT3K7BRB43TM","search-first",null,"Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Systematizes the \"search for existing solutions before implementing\" approach. Use when starting new features or adding functionality.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002F.kiro\u002Fskills\u002Fsearch-first\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: search-first\ndescription: >\n  Research-before-coding workflow. Search for existing tools, libraries, and\n  patterns before writing custom code. Systematizes the \"search for existing\n  solutions before implementing\" approach. Use when starting new features or\n  adding functionality.\nmetadata:\n  origin: 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## Scope and Approval Rules\n\nDefault to read-only research: inspect the repo, package metadata, docs, and public examples before recommending a dependency or integration. Do not install packages, configure MCP servers, publish artifacts, open PRs, or make external write actions from this skill unless the user has explicitly approved that action in the current task.\n\nWhen a candidate requires credentials, paid services, network writes, or project-wide config changes, return a recommendation and approval checkpoint instead of applying it directly.\n\n## Workflow\n\n```\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. APPROVAL CHECKPOINT \u002F IMPLEMENT         │\n│     Recommend package \u002F MCP \u002F custom code   │\n│     Apply only after explicit approval      │\n└─────────────────────────────────────────────┘\n```\n\n## Decision Matrix\n\n| Signal | Action |\n|--------|--------|\n| Exact match, well-maintained, MIT\u002FApache | **Adopt** — recommend the package and request approval before install or config changes |\n| Partial match, good foundation | **Extend** — recommend the package plus a thin wrapper, then wait for approval before applying |\n| Multiple weak matches | **Compose** — propose 2-3 small packages and the integration plan before installing anything |\n| Nothing suitable found | **Build** — explain why custom code is warranted, then implement only within the approved task scope |\n\n## How to Use\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? → Search through relevant modules\u002Ftests first\n1. Is this a common problem? → Search npm\u002FPyPI\n2. Is there an MCP for this? → Check MCP configuration and search\n3. Is there a skill for this? → Check available skills\n4. Is there a GitHub implementation\u002Ftemplate? → Run GitHub code search for maintained OSS before writing net-new code\n\n### Full Mode (subagent)\n\nFor non-trivial functionality, delegate to a research-focused subagent:\n\n```\nInvoke subagent with prompt:\n  \"Research existing tools for: [DESCRIPTION]\n   Language\u002Fframework: [LANG]\n   Constraints: [ANY]\n\n   Search: npm\u002FPyPI, MCP servers, skills, GitHub\n   Return: Structured comparison with recommendation\"\n```\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 → Check 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`got` (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 — recommend `textlint-rule-no-dead-link` and ask before installing it\nResult: Zero custom code if approved, 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 — recommend `got`\u002F`httpx` directly with retry config and ask before changing dependencies\nResult: Zero custom code if approved, 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 — recommend `ajv-cli` plus a project-specific schema, then wait for approval before install\u002Fwrite\nResult: 1 package + 1 schema file if approved, 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- **Over-customizing**: Wrapping a library so heavily it loses its benefits\n- **Dependency bloat**: Installing a massive package for one small feature\n\n## When to Use This Skill\n\n- Starting new features\n- Adding dependencies or integrations\n- Before writing utilities or helpers\n- When evaluating technology choices\n- Planning architecture decisions\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## Scope and Approval Rules\n\nDefault to read-only research: inspect the repo, package metadata, docs, and public examples before recommending a dependency or integration. Do not install packages, configure MCP servers, publish artifacts, open PRs, or make external write actions from this skill unless the user has explicitly approved that action in the current task.\n\nWhen a candidate requires credentials, paid services, network writes, or project-wide config changes, return a recommendation and approval checkpoint instead of applying it directly.\n\n## Workflow\n\n```\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. APPROVAL CHECKPOINT \u002F IMPLEMENT         │\n│     Recommend package \u002F MCP \u002F custom code   │\n│     Apply only after explicit approval      │\n└─────────────────────────────────────────────┘\n```\n\n## Decision Matrix\n\n| Signal | Action |\n|--------|--------|\n| Exact match, well-maintained, MIT\u002FApache | **Adopt** — recommend the package and request approval before install or config changes |\n| Partial match, good foundation | **Extend** — recommend the package plus a thin wrapper, then wait for approval before applying |\n| Multiple weak matches | **Compose** — propose 2-3 small packages and the integration plan before installing anything |\n| Nothing suitable found | **Build** — explain why custom code is warranted, then implement only within the approved task scope |\n\n## How to Use\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? → Search through relevant modules\u002Ftests first\n1. Is this a common problem? → Search npm\u002FPyPI\n2. Is there an MCP for this? → Check MCP configuration and search\n3. Is there a skill for this? → Check available skills\n4. Is there a GitHub implementation\u002Ftemplate? → Run GitHub code search for maintained OSS before writing net-new code\n\n### Full Mode (subagent)\n\nFor non-trivial functionality, delegate to a research-focused subagent:\n\n```\nInvoke subagent with prompt:\n  \"Research existing tools for: [DESCRIPTION]\n   Language\u002Fframework: [LANG]\n   Constraints: [ANY]\n\n   Search: npm\u002FPyPI, MCP servers, skills, GitHub\n   Return: Structured comparison with recommendation\"\n```\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 → Check 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`got` (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 — recommend `textlint-rule-no-dead-link` and ask before installing it\nResult: Zero custom code if approved, 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 — recommend `got`\u002F`httpx` directly with retry config and ask before changing dependencies\nResult: Zero custom code if approved, 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 — recommend `ajv-cli` plus a project-specific schema, then wait for approval before install\u002Fwrite\nResult: 1 package + 1 schema file if approved, 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- **Over-customizing**: Wrapping a library so heavily it loses its benefits\n- **Dependency bloat**: Installing a massive package for one small feature\n\n## When to Use This Skill\n\n- Starting new features\n- Adding dependencies or integrations\n- Before writing utilities or helpers\n- When evaluating technology choices\n- Planning architecture decisions\n",{"name":5,"metadata":24,"description":26},{"origin":25},"ECC","Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Systematizes the \"search for existing solutions before implementing\" approach. Use when starting new features or adding functionality.\n","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","everything-claude-code\u002F.kiro\u002Fskills\u002Fsearch-first",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add SriramGandhiS\u002FSkills --skill search-first",{"tool":42,"command":43},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill search-first",{"tool":45,"command":46},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill search-first","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Feverything-claude-code\u002F.kiro\u002Fskills\u002Fsearch-first\u002FSKILL.md",true,[],[51,59,64,70,77,84],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":58},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":60,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":58},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":58},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":58},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":58},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":58},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]