backend-scan

To explore an unfamiliar backend project structure, you can use an automated scan that analyzes the codebase to generate memory files containing the project overview, tech stack, and architecture conventions for quick discovery.

The best way to keep memory synchronized with a backend codebase is by running a sync mode scan that detects drift and updates your stored knowledge of the project's API patterns, database schema, and architectural decisions after major changes.

State analysis for backend architecture works by examining a provided project path to extract and map technical details, operating in an initial discovery mode to identify the tech stack, API patterns, and database schema before outputting them as memory files.

You do not strictly need git for a basic project scan, but providing git access optionally enables staleness detection during sync mode, allowing the scan to identify outdated memory files and update drift in your backend architecture records.

Yes, you can use backend-scan to extract API patterns and database schema details, as the state analysis specifically targets these elements and outputs dedicated memory files to document your project's technical conventions.

You should run an initial codebase exploration scan when starting work on an unfamiliar project for first discovery, and switch to a memory sync update when you need to detect drift after major changes have been made to the backend codebase.