1 architectural_planning {{task}} {{context}} {{#each requirements}} {{this}} {{/each}} {{allowed_libraries}} {{forbidden_approaches}} {{complexity_limits}} {{integration_requirements}} System Architecture Diagram High-level component architecture showing major modules and their interactions markdown mermaid diagram or textual description Data Model Database schema, data structures, and key entities markdown table or entity-relationship description API Specification Endpoints, methods, request/response formats if applicable OpenAPI spec or markdown table Technology Stack Recommended frameworks, libraries, and tools markdown list with justifications Before creating the architecture: 1. Analyze the requirements: - What are the core functional requirements? - What are the non-functional requirements (performance, security, scalability)? - What constraints must be respected? 2. Consider architectural patterns: - Which pattern best fits (MVC, microservices, event-driven, etc.)? - What are the trade-offs of this pattern? - How does it align with existing codebase patterns? 3. Design component boundaries: - What are the logical modules? - How do they communicate? - What are the interfaces between them? 4. Plan data flow: - How does data enter the system? - How is it processed and stored? - How is it retrieved and presented? 5. Identify integration points: - What external systems need integration? - What are the APIs/services required? - How will authentication/authorization work? 6. Consider testing strategy: - What needs to be tested at each layer? - How will components be tested in isolation? - What integration tests are needed? After this thinking, provide a comprehensive architecture design. {{#if existing_code}} Current implementation to consider {{existing_code}} {{/if}} {{#if example}} Reference implementation pattern {{example}} {{/if}}