Skill

search-first

Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code.

npx claudepluginhub nassimbf/ftitos-claude-code

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Systematizes the "search for existing solutions before implementing" workflow.

SKILL.md

Similar Skills

cache-components

139.3k

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars2

Forks0

Last CommitApr 18, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Search First -- Research Before You Code

Systematizes the "search for existing solutions before implementing" workflow.

When to Activate

Starting a new feature that likely has existing solutions
Adding a dependency or integration
The user asks "add X functionality" and you're about to write code
Before creating a new utility, helper, or abstraction

Workflow

1. NEED ANALYSIS
   Define what functionality is needed
   Identify language/framework constraints

2. PARALLEL SEARCH
   - npm / PyPI / package registries
   - MCP servers and skills
   - GitHub / open source

3. EVALUATE
   Score candidates (functionality, maintenance,
   community, docs, license, deps)

4. DECIDE
   - Adopt as-is
   - Extend / wrap
   - Build custom

5. IMPLEMENT
   Install package / Configure / Write minimal custom code

Decision Matrix

Signal	Action
Exact match, well-maintained, MIT/Apache	Adopt -- install and use directly
Partial match, good foundation	Extend -- install + write thin wrapper
Multiple weak matches	Compose -- combine 2-3 small packages
Nothing suitable found	Build -- write custom, but informed by research

Quick Checklist

Before writing a utility or adding functionality:

Does this already exist in the repo? Search through relevant modules first
Is this a common problem? Search npm/PyPI
Is there an MCP for this? Check available MCP servers
Is there a skill for this? Check available skills
Is there a GitHub implementation/template? Search for maintained OSS

Search Shortcuts by Category

Development Tooling

Linting: eslint, ruff, textlint, markdownlint
Formatting: prettier, black, gofmt
Testing: jest, pytest, go test

AI/LLM Integration

Claude SDK: Context7 for latest docs
Document processing: unstructured, pdfplumber, mammoth

Data & APIs

HTTP clients: httpx (Python), ky/got (Node)
Validation: zod (TS), pydantic (Python)

Anti-Patterns

Jumping to code: Writing a utility without checking if one exists
Ignoring MCP: Not checking if an MCP server already provides the capability
Over-customizing: Wrapping a library so heavily it loses its benefits
Dependency bloat: Installing a massive package for one small feature