research

Researching feature implementation before coding involves analyzing your codebase for conventions and synthesizing external documentation to produce an actionable implementation blueprint. This identifies files to modify, new interfaces, and potential risk assessments.

Codebase analysis for technical investigation identifies relevant code patterns, file locations, and existing conventions within a project. It helps developers understand the current architecture and reduces guesswork when planning new features.

Creating an implementation blueprint requires synthesizing codebase patterns and external documentation into an actionable plan. The resulting blueprint specifies files to modify, defines new interfaces, and outlines risk assessments for the feature.

Yes, deep research mode integrates findings from external documentation, APIs, and community knowledge to compare libraries. It synthesizes this external data with your codebase analysis to ensure compatibility and inform architectural planning.

The best way to plan architectural changes for a new protocol is conducting a deep dive investigation. This approach researches best practices, compares relevant libraries, and identifies potential conflicts with your existing architecture before implementation.

Technical due diligence does not always require a full scan; you can choose a quick codebase scan for faster results. Multi-depth analysis allows you to select from quick scans to deep dives depending on your investigation needs.