| description | Seek truth through verification and code search |
|---|
seek truth. dont trust your knowledge. use web/code search to find deterministic answers in the code. use code refs and code snippets to reason about your decisions. you can clone dependencies/parts of the stack into a temp dir to scan files more quickly.
| description | Analyze codebase architecture and style patterns |
|---|
look at similar files to ensure we're following the established architecture, code style, impl details/patterns etc.
review data flows, architecture, modular design, software architecture patterns, paradigms.
everything should FEEL like the existing codebase - we essentially want to contribute code much like a core contributor - not a junior with no idea.
we need to ground ourselves with related files, as well as unrelated files to understand full vertical integration.
$ARGUMENTS