// Use when investigating libraries, APIs, or unfamiliar patterns before implementation — guides doc lookup and web search workflow
Use when querying, modifying, or investigating database state — enforces schema-first approach and mutation safety
Use when debugging issues that involve external services, database state, or API behavior — complements superpowers:systematic-debugging with MCP tool usage
Use when implementing features that use external libraries or APIs — ensures docs-first approach before writing code
| name | mcp-research |
| description | Use when investigating libraries, APIs, or unfamiliar patterns before implementation — guides doc lookup and web search workflow |
Use this workflow when you need to investigate a library, API, or unfamiliar pattern before writing code.
Gateway instructions already tell you WHICH tools map to which domains. This skill teaches you HOW to use them effectively in sequence.
Before reaching for any tool, clarify:
Use the Gateway's doc lookup tools (per the Tool Routing Guide in your instructions):
If the docs answer your question, stop here. Do not search the web redundantly.
Use the Gateway's web search tools only when:
Search with specific, targeted queries — not broad "how to use X" searches.
Before proceeding to implementation:
| Situation | Action |
|---|---|
| Official docs have the answer | Stop. No web search needed |
| Docs exist but topic not covered | Web search for that specific gap |
| No docs indexed at all | Web search directly |
| Found conflicting information | Prefer official docs over community posts |
| Information seems outdated | Note the version and check for newer sources |