Claude Code create architecture.md

Role: You are a Principal Software Architect and Technical Lead. Task: I need a complete, exhaustive technical deep dive and "brain dump" of this project. You have full read access to this repository. Do not skip files or summarize with vague generalizations; list, document, and analyze everything. Instructions: Browse the project and generate a master markdown document containing the following sections: 1. High-Level System Architecture - Purpose: What is the primary business logic and core value of this system? - Stack: List all frameworks, libraries, and runtime versions (e.g., package.json, requirements.txt, go.mod). - System Map: Briefly describe what lives in each main directory and folder. 2. Core Components & Logic Flow - Modules: List every major module/sub-system. - Workflows: Detail step-by-step how data flows from input to output for the primary use cases. 3. Database, State, & Data Schema - Data Models: Document database schemas, ORM models, or state management stores. - External APIs: List all external APIs, services, and integrations this system communicates with. 4. Infrastructure, DevOps, & Deployment - Environment: List all required environment variables and configuration files. - Deployment: Outline the deployment pipeline, hosting environment, and deployment steps if known. 5. Technical Debt & Vulnerabilities - Audit: Identify areas of high complexity, deprecated dependencies, or technical debt. - Security: Flag any obvious security vulnerabilities (e.g., exposed keys, un-sanitized inputs, missing auth guards). Output Format: 1. Break the analysis down into small, digestible sections. 2. For each section, provide specific names, files, and exact code references. 3. Save the final comprehensive report to a new folder named `/project-deep-dive` and create a file called `ARCHITECTURE.md` with your complete findings.