sinaptik-ai Web Research
Methodology
Follow this structured approach for any research task:
1. Scope the question
Before searching, clarify:
- What specifically does the user need to know?
- What format should the answer take? (summary, comparison table, list, report)
- How deep should the research go? (quick answer vs. comprehensive analysis)
2. Search strategy
- Start with 2–3 targeted queries using different phrasings
- Use specific terms, not vague ones: "React server components vs client components performance 2025" beats "React performance"
- For comparisons, search each option independently before comparing
- For recent topics, include the year in queries
- If initial results are thin, broaden terms or try adjacent queries
3. Source evaluation
Prioritize sources in this order:
- Official documentation — most reliable for technical topics
- Primary sources — research papers, official reports, announcements
- Expert analysis — recognized experts, reputable publications
- Community consensus — Stack Overflow, GitHub discussions (check vote counts and recency)
- News articles — for current events, cross-reference multiple outlets
Red flags: outdated dates, no author attribution, SEO-farm patterns, contradicted by official sources.
4. Synthesize findings
- Lead with the direct answer, then supporting evidence
- Note conflicting information across sources and which is more credible
- Include source URLs for key claims
- Flag uncertainty: "Based on available data..." or "Sources disagree on..."
- Distinguish facts from opinions
5. Present results
For quick questions: Direct answer in 2–3 sentences with source link.
For comparisons:
| Criteria | Option A | Option B |
|---|---|---|
| Key metric | Value | Value |
| Pros | ... | ... |
| Cons | ... | ... |
For deep research: Structure as:
- Summary — 2–3 sentence answer
- Key findings — bulleted list of important points
- Analysis — detailed discussion organized by theme
- Sources — numbered list of references used
Common Research Patterns
Product/tool comparison
- Search for each product independently
- Search for "X vs Y" comparison articles
- Check official pricing pages and feature lists
- Look for user reviews on neutral platforms
- Compile into comparison table
Technical question
- Check official documentation first
- Search for the specific error message or API
- Look at GitHub issues and Stack Overflow
- Check release notes if version-specific
Current events / news
- Search multiple news sources
- Check the date — prefer last 48 hours for breaking news
- Look for the primary source (press release, official statement)
- Cross-reference facts across 2+ outlets
How-to / tutorial
- Find official docs or getting-started guides
- Check for community tutorials with recent dates
- Verify steps actually work (versions matter)
- Prefer tutorials that explain why, not just what
Output Quality Rules
- Always cite sources — include URLs for every factual claim
- Always note dates — "As of March 2025, ..." for time-sensitive info
- Never fabricate — if you can't find it, say so
- Quantify when possible — "65% of developers prefer X" beats "most developers prefer X"
- Acknowledge limits — if research was shallow or sources were scarce, say so