<skill_overview> Optimize use of "assist/research/code-research" subagent for evidence-based codebase analysis

Locate where a feature or behavior is implemented Trace data flow or call chains across modules Explain configuration, environment, or initialization logic Answer questions with file/line evidence Inspect recent changes or regressions

</skill_overview> <task_formulation>

State the exact question and expected outcome Provide known entry points: file, symbol, or keyword Specify scope boundaries (module, package, layer) Request evidence with file paths and line numbers Specify depth level when needed: standard, deep, expert

Where is JWT validation implemented? Show the handler path and middleware order with file references. Clear goal, scope, and evidence requirements

Trace how user profile data is loaded from API to UI. Include data flow and key transformations. Call-chain focus and expected detail level

Explain the whole backend. Too broad and undefined scope

</task_formulation> <research_strategies>

Review project structure and likely entry files Search for key terms or routes Inspect candidate files to confirm entry points

Locate the handler or public API Trace symbol usage across modules Summarize the chain with evidence

Locate configuration definitions and defaults Trace how configuration is loaded and applied Document overrides and precedence

Identify recent changes and affected areas Relate changes to observed behavior Highlight potential regression risks

Ask 1-3 targeted clarification questions Research narrowly scoped answers Repeat until scope is satisfied

</research_strategies> <response_format>