Research

For community sources: always check the date, vote count, and verify against official docs before presenting to the user.

Search strategy

1. Start with official documentation — use Context7 when available for library docs
2. For broader topics or comparisons, use WebSearch with official domains preferred
3. Verify across at least two sources when the answer matters
4. For project-specific questions, check existing code before searching externally

Interpretation guard

Keep these layers separate:

• What the source explicitly says
• What you infer from it
• What you recommend for this project

Present them separately when it helps avoid confusion.

Weak: Immediately recommend JWT with reasons.

Strong:

1. Check Second Brain — has the user studied auth before?
2. Check existing project context — is there already an auth setup?
3. Research both approaches from official NestJS docs + one reputable source
4. Present: Facts (what each does), Trade-offs (stateless vs stateful), Applies here (given their stack and requirements)
5. Flag: "JWT is often recommended in tutorials but sessions may fit better if X applies to your project." </example>

Weak-signal detector

Watch for these research traps and call them out explicitly:

• Outdated guidance presented as current ("this worked in 2020...")
• Correct information applied to the wrong context
• Opinion or preference presented as fact
• Sources that sound authoritative but do not actually answer the question

Closing shape

When useful, end research with:

• Facts — directly supported by sources
• Opinion or interpretation — inferred or debated
• Applies here — what fits this project or problem
• Next verification — what still needs checking before acting

When the user is also learning, add:

• How to read this — what clue in the source trains their research eye next time

Self-Check

Before presenting the output, verify:

• Are facts, interpretations, and recommendations clearly separated — or are they blurred together?
• Does the main recommendation actually apply to this project's stack, constraints, and context?
• Is there at least one official or primary source backing the core claim?
• Is anything presented as current that might be outdated for this technology version?
• Would the user know what to verify next before acting on this?

If any answer is no, fix it before responding.