majiayu000 Examples: "Is useEffect still the way to handle this in React 18?", "Did Stripe change their webhook payload?", "What's the current Node LTS version?"
Just search, grab the answer, keep coding. No storage, no ceremony, no permission needed.
Examples: Choosing between competing technologies, understanding a new architectural pattern, debugging something that doesn't match documentation.
Always ask first: "This needs deeper research (5-15 min). Should I dig into this now?" Let the user decide if they want to pause for research or continue with existing knowledge.
Research thoroughly, save findings in research/[topic].md for team reference.
MCP servers (preferred when available):
- Tavily MCP server
- Exa MCP server
- Other specialized search MCP servers
Built-in tools (fallback):
- Cursor: web_search tool
- Claude Code: Built-in web search
Tell the user which you're using:
- "Using Tavily MCP server for enhanced search capabilities"
- "Using Exa MCP server for code-focused research"
- "Using built-in web search (no MCP servers configured)"
This transparency helps users understand tool selection and configure MCP servers if desired.
Good pattern:
Stripe Checkout v4 Migration
Breaking change: redirectToCheckout() removed in v4
New pattern:
- Use Payment Element (unified UI)
- Or Checkout Sessions API (hosted page)
Migration: [Specific code example]
Source: Stripe docs v2024.11.15
Be transparent: Say "I should verify this" or "Let me check current best practices" rather than guessing.
Speed over perfection: For quick checks, first good answer wins. For deep dives, thoroughness matters.
No unnecessary storage: Quick research lives in the conversation. Only save deep research that others might reference.