Discovers and researches authoritative documentation with version-specific, context-aware search. Auto-activates when user asks "find documentation", "API docs", "how to use", "integration guide", "best practices", "design pattern", or when running /ccpm:plan or /ccpm:plan. Fetches latest docs from official sources via Context7 MCP. Uses progressive discovery (overview → API reference → integration → best practices). Prioritizes: Official docs → Framework guides → API references → Community resources. Provides version-specific recommendations and code examples from documentation. Flags important caveats and performance considerations. Surfaces migration guides when upgrading frameworks.
Auto-activates when users ask for documentation, API references, or run `/ccpm:plan`. Discovers authoritative docs via Context7 MCP, providing version-specific examples, best practices, and implementation guidance from official sources.
/plugin marketplace add duongdev/ccpm/plugin install ccpm@duongdev-ccpm-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Intelligent documentation discovery and research for technical implementation.
This skill auto-activates when:
/ccpm:plan (needs library docs)/ccpm:plan (technical research phase)Finds relevant documentation for:
Search strategies:
Works seamlessly with Context7 to fetch latest documentation:
User: "Find React 19 documentation for Server Components"
Claude: [docs-seeker activates]
Searching for React 19 Server Components documentation...
Using Context7 to fetch latest docs:
1. Official React docs (react.dev)
2. Server Components RFC
3. Next.js App Router integration guide
Found:
- React 19 Server Components: https://react.dev/reference/rsc/server-components
- Key features: Async components, data fetching, streaming
- Best practices: Use for data-heavy components, avoid client-side state
- Integration: Works with Next.js 15 App Router
Summary available for /ccpm:plan architecture section.
Use with /ccpm:plan:
When planning a task, docs-seeker helps gather technical context:
User: "/ccpm:plan AUTH-123 JIRA-456"
Claude: [docs-seeker activates during research phase]
Researching technical requirements for AUTH-123...
Finding relevant documentation:
1. JWT authentication best practices
2. OAuth 2.0 specification
3. Passport.js integration guide
4. Express.js security middleware
Key findings:
- JWT: Use RS256 for production (not HS256)
- Refresh tokens: Store in httpOnly cookies
- OAuth: Implement PKCE flow for SPAs
- Rate limiting: 5 login attempts per 15 minutes
Documentation links saved to Linear task for implementation reference.
Use with /ccpm:plan:
When writing specs, docs-seeker finds authoritative sources:
User: "/ccpm:plan DOC-789 api-design"
Claude: [docs-seeker activates]
Researching API design best practices...
Finding documentation:
1. RESTful API design guide (Microsoft)
2. GraphQL schema design (Apollo)
3. OpenAPI 3.1 specification
4. API versioning strategies
Recommendations based on docs:
- Endpoints: Use nouns, not verbs (/users not /getUsers)
- Versioning: URL path (/v1/) or Accept header
- Pagination: Cursor-based for scalability
- Error handling: RFC 7807 Problem Details
- Documentation: OpenAPI spec + Swagger UI
Writing API design section with these guidelines...
During feature implementation:
User: "How do I implement file uploads with NextJS 15?"
Claude: [docs-seeker activates]
Searching Next.js 15 file upload documentation...
Found official guides:
1. Next.js App Router: Route Handlers
2. FormData API usage
3. File upload best practices
4. Streaming uploads for large files
Implementation approach:
```typescript
// app/api/upload/route.ts
export async function POST(request: Request) {
const formData = await request.formData();
const file = formData.get('file') as File;
// Process file
const bytes = await file.arrayBuffer();
const buffer = Buffer.from(bytes);
// Save to storage
await saveFile(buffer, file.name);
return Response.json({ success: true });
}
Documentation: https://nextjs.org/docs/app/building-your-application/routing/route-handlers
Would you like me to add this to the implementation plan?
## Documentation Sources
### Official Sources (Highest Priority)
**Always check official docs first**:
- Framework documentation (React, Next.js, Vue, Angular)
- Library docs (Lodash, Axios, Moment.js)
- Cloud provider docs (AWS, GCP, Azure)
- API specifications (Stripe, Twilio, SendGrid)
### Technical Specifications
**For standards and protocols**:
- W3C specifications
- IETF RFCs
- ECMA standards
- OpenAPI/Swagger specs
### Community Resources
**When official docs are insufficient**:
- MDN Web Docs (JavaScript, CSS, HTML)
- Stack Overflow discussions
- GitHub repositories and READMEs
- Technical blogs (reputable sources only)
## Search Strategies
### Strategy 1: Version-Specific Search
Always search for the specific version in use:
❌ Generic: "React hooks documentation" ✅ Specific: "React 19 hooks documentation"
❌ Generic: "Node.js async/await" ✅ Specific: "Node.js 20 async/await best practices"
### Strategy 2: Context-Aware Search
Include the context of what you're building:
❌ Vague: "authentication docs" ✅ Context: "JWT authentication with Express.js and Passport"
❌ Vague: "database queries" ✅ Context: "PostgreSQL complex joins with Prisma ORM"
### Strategy 3: Progressive Discovery
Start broad, then narrow down:
1. **Overview**: "What is Server Components in React?"
2. **API Reference**: "Server Component API methods"
3. **Integration**: "Server Components with Next.js App Router"
4. **Best Practices**: "Server Components performance optimization"
## Examples
### Example 1: Research for Spec Writing
User: "/ccpm:plan DOC-456 architecture"
Claude: [docs-seeker activates]
Researching architecture patterns for payment processing...
Finding documentation:
Stripe API documentation
PCI compliance requirements
Architecture patterns
Error handling
Documentation summary:
Writing architecture section with these patterns...
### Example 2: Quick Implementation Help
User: "How do I use React useEffect with async functions?"
Claude: [docs-seeker activates]
Searching React useEffect async documentation...
Found: React 19 documentation on useEffect
Official recommendation:
// ✅ Correct approach
useEffect(() => {
async function fetchData() {
const response = await fetch('/api/data');
const data = await response.json();
setData(data);
}
fetchData();
}, []);
// ❌ Wrong - useEffect cannot be async directly
useEffect(async () => {
// This won't work!
}, []);
Key points from docs:
Documentation: https://react.dev/reference/react/useEffect#fetching-data-with-effects
Would you like me to show the full pattern with cleanup?
### Example 3: API Integration Research
User: "Find Stripe webhook documentation"
Claude: [docs-seeker activates]
Searching Stripe webhook documentation...
Found official Stripe docs:
Webhook Events
Webhook Security
const sig = request.headers['stripe-signature'];
const event = stripe.webhooks.constructEvent(
request.body,
sig,
process.env.STRIPE_WEBHOOK_SECRET
);
Best Practices
Testing
Documentation: https://stripe.com/docs/webhooks
This should be added to the implementation plan under "Webhook Handler" section.
## Integration with CCPM Workflows
### Workflow 1: Spec Writing
### Workflow 2: Planning Phase
### Workflow 3: Implementation Support
## Works With Context7 MCP
**Context7 integration provides**:
- Latest documentation (always up-to-date)
- Version-specific information
- Framework changelog and migration guides
- API reference with examples
**Example Context7 usage**:
docs-seeker: "Find Next.js 15 App Router documentation" ↓ Context7 MCP: Fetches latest from nextjs.org ↓ Returns: App Router architecture, routing, data fetching, caching ↓ docs-seeker: Summarizes key points relevant to task
## Tips for Better Results
### Be Specific
**Good requests**:
- "Find Prisma migration documentation for PostgreSQL"
- "Get Tailwind CSS v4 documentation for dark mode"
- "Show GraphQL schema stitching with Apollo Federation"
**Vague requests** (harder to help):
- "Find docs"
- "How does this work?"
- "Give me information about React"
### Include Version Information
Always mention versions when known:
- "Next.js 15" not just "Next.js"
- "React 19" not just "React"
- "Node.js 20 LTS" not just "Node.js"
### Specify Your Stack
Help docs-seeker find the right integration docs:
- "React with TypeScript"
- "Express.js with Prisma ORM"
- "Next.js with Auth.js (NextAuth v5)"
## Common Use Cases
### Use Case 1: Starting New Feature
Before implementation:
### Use Case 2: Troubleshooting
When stuck:
### Use Case 3: Architecture Decisions
When designing:
## Integration with Other Skills
**Works alongside**:
- **sequential-thinking**: Use docs-seeker to research each step
- **pm-workflow-guide**: Suggests when documentation research needed
- **ccpm-debugging**: Find debugging guides when issues arise
- **Context7 MCP**: Fetches actual documentation content
**Example combined activation**:
User: "Break down this complex GraphQL federation task" ↓ sequential-thinking: Structure the problem breakdown ↓ docs-seeker: Find Apollo Federation documentation ↓ Together: Create informed, well-researched plan
## Summary
This skill provides:
- ✅ Intelligent documentation discovery
- ✅ Version-specific search results
- ✅ Integration with Context7 MCP
- ✅ Support for CCPM planning and spec writing
- ✅ Implementation guidance from authoritative sources
**Philosophy**: Research first, implement with confidence. Use authoritative sources, always check official documentation, and stay current with latest versions.
---
**Source**: From [claudekit-skills/docs-seeker](https://github.com/mrgoonie/claudekit-skills)
**License**: MIT
**CCPM Integration**: `/ccpm:plan`, `/ccpm:plan`, Context7 MCP
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.