| name | web-research |
| description | Requires web search before answering when facts are uncertain: external APIs, regulated domains, latest library docs, unfamiliar errors. No guessing. Use during planning, implementation, and debugging when verification matters. |
Web Research — Don't Guess, Search
Core principle: Don't guess. If you're not sure, search.
When to Search
| Phase | Search When |
|---|
Planning (docs/biz/) | External API integration, domain rules/constraints, similar service tech |
| Development | Latest API docs, library versions, best practices |
| Debugging | Unfamiliar errors, compatibility issues, environment config problems |
Using Search Results
- In planning docs (
docs/biz/): "This API allows 1,000 free calls per month"
- In technical docs (
docs/ai-dev/): API documentation URLs, known constraints
- For non-developers: Only share what they need — signup requirements, free/paid status
When NOT to Search
- Well-known fundamentals (HTML, CSS, basic syntax)
- Questions about the project's own code (just read the code)
- Topics already researched and recorded in
docs/ai-dev/