web-research

name	web-research
description	Search multiple websites for techniques, solutions, or best practices — read, compare, synthesize, then test/validate in the actual project before concluding. Trigger on /web-research, or when exploring solutions, researching approaches, learning new techniques, or validating ideas from the web.
user-invocable	true
allowed-tools	Read, Grep, Glob, Bash, Edit, Browser

Web Research

Find techniques from multiple sources, cross-reference, test in the real project, then conclude.

Workflow

1. Define the question

State what you're looking for in one sentence. Be specific.

ค้นหา: วิธี optimize PostgreSQL query ที่มี JOIN หลายตาราง
Research: best error handling patterns in TypeScript monorepos

2. Search multiple sources

Do not rely on a single source. Search from at least 3 different angles:

• Web search — general keywords, problem description
• Official docs — library/framework documentation
• Stack Overflow / Reddit — real-world issues and solutions
• GitHub — example projects, issues, discussions
• Blogs / articles — tutorials, deep dives, comparisons

For each source, note:

• What technique does it suggest?
• What problem does it solve?
• What are the trade-offs or limitations?
• Does it have code examples? Are they complete?

3. Synthesize

Compare findings across sources:

Source	Technique	Pros	Cons	Works here?
src 1	...	...	...	?
src 2	...	...	...	?
src 3	...	...	...	?

• What do sources agree on? (likely reliable)
• What conflicts? (needs testing)
• What is specific to a certain version/context? (may not apply)
• What is the simplest approach that could work?

4. Test in the real project

Before concluding, validate:

• Can you reproduce the technique in the actual codebase?
• Does it work with the project's dependencies, versions, and config?
• Are there edge cases the articles didn't mention?
• Does it actually solve the original problem?

Do not just copy-paste from the web. Adapt to the project.

5. Conclude

• Works — technique validated, document the result
• Works with modifications — note what had to change
• Doesn't work — explain why (version mismatch, different context, outdated info)
• Better alternative found — document the alternative

Output

## Research: <topic>

### Sources consulted
- [title](url) — key takeaway
- [title](url) — key takeaway

### Synthesis
What the sources agree on, what conflicts, what needs testing.

### Validation
What was tested, what worked, what didn't.

### Conclusion
Final recommendation or technique with rationale.

Rules

• Minimum 3 sources before concluding. Do not rely on one answer.
• Test before recommending — "works in theory" is not done.
• Note when a source is outdated (version mismatch, deprecated API).
• If no good source found, say so — do not fabricate.
• Document failed attempts too — they save future time.
• Do not copy code verbatim without attribution and adaptation.