FEA and A updated
This commit is contained in:
Brian Madison
@@ -1,263 +1,767 @@
|
||||
# {Project Name} Architecture Document
|
||||
# {{Project Name}} Architecture Document
|
||||
|
||||
[[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. If at a minimum you cannot local `docs/prd.md` ask the user what docs will provide the basis for the architecture.]]
|
||||
|
||||
## Introduction
|
||||
|
||||
[[LLM: This section establishes the document's purpose and scope. Keep the content below but ensure project name is properly substituted.]]
|
||||
|
||||
This document outlines the overall project architecture for {{Project Name}}, including backend systems, shared services, and non-UI specific concerns. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development, ensuring consistency and adherence to chosen patterns and technologies.
|
||||
|
||||
**Relationship to Frontend Architecture:**
|
||||
If the project includes a significant user interface, a separate Frontend Architecture Document will detail the frontend-specific design and MUST be used in conjunction with this document. Core technology stack choices documented herein (see "Tech Stack") are definitive for the entire project, including any frontend components.
|
||||
|
||||
### Starter Template or Existing Project
|
||||
|
||||
[[LLM: Before proceeding further with architecture design, check if the project is based on a starter template or existing codebase:
|
||||
|
||||
1. Review the PRD and brainstorming brief for any mentions of:
|
||||
|
||||
- Starter templates (e.g., Create React App, Next.js, Vue CLI, Angular CLI, etc.)
|
||||
- Existing projects or codebases being used as a foundation
|
||||
- Boilerplate projects or scaffolding tools
|
||||
- Previous projects to be cloned or adapted
|
||||
|
||||
2. If a starter template or existing project is mentioned:
|
||||
|
||||
- Ask the user to provide access via one of these methods:
|
||||
- Link to the starter template documentation
|
||||
- Upload/attach the project files (for small projects)
|
||||
- Share a link to the project repository (GitHub, GitLab, etc.)
|
||||
- Analyze the starter/existing project to understand:
|
||||
- Pre-configured technology stack and versions
|
||||
- Project structure and organization patterns
|
||||
- Built-in scripts and tooling
|
||||
- Existing architectural patterns and conventions
|
||||
- Any limitations or constraints imposed by the starter
|
||||
- Use this analysis to inform and align your architecture decisions
|
||||
|
||||
3. If no starter template is mentioned but this is a greenfield project:
|
||||
|
||||
- Suggest appropriate starter templates based on the tech stack preferences
|
||||
- Explain the benefits (faster setup, best practices, community support)
|
||||
- Let the user decide whether to use one
|
||||
|
||||
4. If the user confirms no starter template will be used:
|
||||
- Proceed with architecture design from scratch
|
||||
- Note that manual setup will be required for all tooling and configuration
|
||||
|
||||
Document the decision here before proceeding with the architecture design. In none, just say N/A]]
|
||||
|
||||
## High Level Architecture
|
||||
|
||||
[[LLM: Produce the following child sections, and then derscribe why you made the choices you did if any choices were taken that you made that were unique or deviated from what was given as initial context from the PRD or prior discussions, and immediately execute tasks#advanced-elicitation display]]
|
||||
|
||||
### Introduction / Preamble
|
||||
|
||||
{This document outlines the overall project architecture, including backend systems, shared services, and non-UI specific concerns. Its primary goal is to serve as the guiding architectural blueprint for AI-driven development, ensuring consistency and adherence to chosen patterns and technologies.
|
||||
|
||||
**Relationship to Frontend Architecture:**
|
||||
If the project includes a significant user interface, a separate Frontend Architecture Document (typically named `front-end-architecture-tmpl.txt` or similar, and linked in the "Key Reference Documents" section) details the frontend-specific design and MUST be used in conjunction with this document. Core technology stack choices documented herein (see "Definitive Tech Stack Selections") are definitive for the entire project, including any frontend components.}
|
||||
[[LLM: This section contains multiple subsections that establish the foundation of the architecture. Present all subsections together (Introduction, Technical Summary, High Level Overview, Project Diagram, and Architectural Patterns), then apply `tasks#advanced-elicitation` protocol to the complete High Level Architecture section. The user can choose to refine the entire section or specific subsections.]]
|
||||
|
||||
### Technical Summary
|
||||
|
||||
{ Provide a brief paragraph overview of the system's architecture, key components, technology choices, and architectural patterns used. Reference the goals from the PRD. }
|
||||
[[LLM: Provide a brief paragraph (3-5 sentences) overview of:
|
||||
|
||||
- The system's overall architecture style
|
||||
- Key components and their relationships
|
||||
- Primary technology choices
|
||||
- Core architectural patterns being used
|
||||
- Reference back to the PRD goals and how this architecture supports them]]
|
||||
|
||||
### High Level Overview
|
||||
|
||||
[[LLM: Describe the main architectural style (e.g., Monolith, Microservices, Serverless, Event-Driven), reflecting the decision made in the PRD. Explain the repository structure (Monorepo/Polyrepo). Explain the primary user interaction or data flow at a conceptual level.]]
|
||||
[[LLM: Based on the PRD's Technical Assumptions section, describe:
|
||||
|
||||
1. The main architectural style (e.g., Monolith, Microservices, Serverless, Event-Driven)
|
||||
2. Repository structure decision from PRD (Monorepo/Polyrepo)
|
||||
3. Service architecture decision from PRD
|
||||
4. Primary user interaction flow or data flow at a conceptual level
|
||||
5. Key architectural decisions and their rationale
|
||||
|
||||
After presenting this section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### High Level Project Diagram
|
||||
|
||||
[[LLM: Produce a Mermaid High Level Diagram that best Describes the Overall PRD Backend Architecture]]
|
||||
[[LLM: Create a Mermaid diagram that visualizes the high-level architecture. Consider:
|
||||
|
||||
- System boundaries
|
||||
- Major components/services
|
||||
- Data flow directions
|
||||
- External integrations
|
||||
- User entry points
|
||||
|
||||
Use appropriate Mermaid diagram type (graph TD, C4, sequence) based on what best represents the architecture
|
||||
|
||||
After presenting the diagram, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
### Architectural and Design Patterns
|
||||
|
||||
{ List the key high-level patterns chosen for the architecture. These foundational patterns should be established early as they guide component design, interactions, and technology choices. }
|
||||
[[LLM: List the key high-level patterns that will guide the architecture. For each pattern:
|
||||
|
||||
- **Pattern 1:** {e.g., Serverless, Event-Driven, Microservices, CQRS} - _Rationale/Reference:_ {Briefly why, or link to a more detailed explanation if needed}
|
||||
- **Pattern 2:** {e.g., Dependency Injection, Repository Pattern, Module Pattern} - _Rationale/Reference:_ {...}
|
||||
- **Pattern N:** {...}
|
||||
1. Present 2-3 viable options if multiple exist
|
||||
2. Provide your recommendation with clear rationale
|
||||
3. Get user confirmation before finalizing
|
||||
4. These patterns should align with the PRD's technical assumptions and project goals
|
||||
|
||||
### Components
|
||||
Common patterns to consider:
|
||||
|
||||
[[LLM: Describe the major logical components or services of the system and their responsibilities, reflecting the decided overall architecture (e.g., distinct microservices, modules within a monolith, packages within a monorepo) and the architectural patterns adopted. Explain how they collaborate. Produce a component diagram or diagrams as needed in mermaid as a child section. Immediately execute tasks#advanced-elicitation display]]
|
||||
- Architectural style patterns (Serverless, Event-Driven, Microservices, CQRS, Hexagonal)
|
||||
- Code organization patterns (Dependency Injection, Repository, Module, Factory)
|
||||
- Data patterns (Event Sourcing, Saga, Database per Service)
|
||||
- Communication patterns (REST, GraphQL, Message Queue, Pub/Sub)]]
|
||||
|
||||
- Component A: {Description of responsibility}
|
||||
<<REPEAT: pattern>>
|
||||
|
||||
{Insert component diagram here if it helps - e.g., using Mermaid graph TD or C4 Model Container/Component Diagram}
|
||||
- **{{pattern_name}}:** {{pattern_description}} - _Rationale:_ {{rationale}}
|
||||
|
||||
- Component N...: {Description of responsibility}
|
||||
<</REPEAT>>
|
||||
|
||||
{ Insert component diagram here if it helps - e.g., using Mermaid graph TD or C4 Model Container/Component Diagram }
|
||||
@{example: patterns}
|
||||
|
||||
- **Serverless Architecture:** Using AWS Lambda for compute - _Rationale:_ Aligns with PRD requirement for cost optimization and automatic scaling
|
||||
- **Repository Pattern:** Abstract data access logic - _Rationale:_ Enables testing and future database migration flexibility
|
||||
- **Event-Driven Communication:** Using SNS/SQS for service decoupling - _Rationale:_ Supports async processing and system resilience
|
||||
|
||||
@{/example}
|
||||
|
||||
[[LLM: After presenting the patterns, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Tech Stack
|
||||
|
||||
[[LLM: This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
|
||||
|
||||
1. Review PRD technical assumptions and any preferences from `data#technical-preferences`
|
||||
2. For each category, present 2-3 viable options with pros/cons
|
||||
3. Make a clear recommendation based on project needs
|
||||
4. Get explicit user approval for each selection
|
||||
5. Document exact versions (avoid "latest" - pin specific versions)
|
||||
6. This table is the single source of truth - all other docs must reference these choices
|
||||
|
||||
Key decisions to finalize - before displaying the table, ensure you are aware of or ask the user about - let the user know if they are not sure on any that you can also provide suggestions with rationale:
|
||||
|
||||
- Starter templates (if any)
|
||||
- Languages and runtimes with exact versions
|
||||
- Frameworks and libraries / packages
|
||||
- Cloud provider and key services choices
|
||||
- Database and storage solutions - if unclear suggest sql or nosql or other types depending on the project and depending on cloud provider offer a suggestion
|
||||
- Development tools
|
||||
|
||||
Upon render of the table, ensure the user is aware of the importance of this sections choices, should also look for gaps or disagreements with anything, ask for any clarifications if something is unclear why its in the list, and also right away apply `tasks#advanced-elicitation` display - this statement and the options should be rendered and then prompt right all before allowing user input.]]
|
||||
|
||||
### Cloud Infrastructure
|
||||
|
||||
- **Provider:** {{cloud_provider}}
|
||||
- **Key Services:** {{core_services_list}}
|
||||
- **Deployment Regions:** {{regions}}
|
||||
|
||||
### Technology Stack Table
|
||||
|
||||
| Category | Technology | Version | Purpose | Rationale |
|
||||
| :----------------- | :----------------- | :---------- | :---------- | :------------- |
|
||||
| **Language** | {{language}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Runtime** | {{runtime}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Framework** | {{framework}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Database** | {{database}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Cache** | {{cache}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Message Queue** | {{queue}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **API Style** | {{api_style}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Authentication** | {{auth}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Testing** | {{test_framework}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Build Tool** | {{build_tool}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **IaC Tool** | {{iac_tool}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Monitoring** | {{monitoring}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
| **Logging** | {{logging}} | {{version}} | {{purpose}} | {{why_chosen}} |
|
||||
|
||||
@{example: tech_stack_row}
|
||||
| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |
|
||||
| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |
|
||||
| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |
|
||||
@{/example}
|
||||
|
||||
## Data Models
|
||||
|
||||
[[LLM: Define the core data models/entities:
|
||||
|
||||
1. Review PRD requirements and identify key business entities
|
||||
2. For each model, explain its purpose and relationships
|
||||
3. Include key attributes and data types
|
||||
4. Show relationships between models
|
||||
5. Discuss design decisions with user
|
||||
|
||||
Create a clear conceptual model before moving to database schema.
|
||||
|
||||
After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: data_model>>
|
||||
|
||||
### {{model_name}}
|
||||
|
||||
**Purpose:** {{model_purpose}}
|
||||
|
||||
**Key Attributes:**
|
||||
|
||||
- {{attribute_1}}: {{type_1}} - {{description_1}}
|
||||
- {{attribute_2}}: {{type_2}} - {{description_2}}
|
||||
|
||||
**Relationships:**
|
||||
|
||||
- {{relationship_1}}
|
||||
- {{relationship_2}}
|
||||
<</REPEAT>>
|
||||
|
||||
## Components
|
||||
|
||||
[[LLM: Based on the architectural patterns, tech stack, and data models from above:
|
||||
|
||||
1. Identify major logical components/services and their responsibilities
|
||||
2. Consider the repository structure (monorepo/polyrepo) from PRD
|
||||
3. Define clear boundaries and interfaces between components
|
||||
4. For each component, specify:
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
5. Create component diagrams where helpful
|
||||
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
<<REPEAT: component>>
|
||||
|
||||
### {{component_name}}
|
||||
|
||||
**Responsibility:** {{component_description}}
|
||||
|
||||
**Key Interfaces:**
|
||||
|
||||
- {{interface_1}}
|
||||
- {{interface_2}}
|
||||
|
||||
**Dependencies:** {{dependencies}}
|
||||
|
||||
**Technology Stack:** {{component_tech_details}}
|
||||
<</REPEAT>>
|
||||
|
||||
### Component Diagrams
|
||||
|
||||
[[LLM: Create Mermaid diagrams to visualize component relationships. Options:
|
||||
|
||||
- C4 Container diagram for high-level view
|
||||
- Component diagram for detailed internal structure
|
||||
- Sequence diagrams for complex interactions
|
||||
Choose the most appropriate for clarity
|
||||
|
||||
After presenting the diagrams, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## External APIs
|
||||
|
||||
[[LLM: For each external service integration:
|
||||
|
||||
1. Identify APIs needed based on PRD requirements and component design
|
||||
2. If documentation URLs are unknown, ask user for specifics
|
||||
3. Document authentication methods and security considerations
|
||||
4. List specific endpoints that will be used
|
||||
5. Note any rate limits or usage constraints
|
||||
|
||||
If no external APIs are needed, state this explicitly and skip to next section.]]
|
||||
|
||||
^^CONDITION: has_external_apis^^
|
||||
|
||||
<<REPEAT: external_api>>
|
||||
|
||||
### {{api_name}} API
|
||||
|
||||
- **Purpose:** {{api_purpose}}
|
||||
- **Documentation:** {{api_docs_url}}
|
||||
- **Base URL(s):** {{api_base_url}}
|
||||
- **Authentication:** {{auth_method}}
|
||||
- **Rate Limits:** {{rate_limits}}
|
||||
|
||||
**Key Endpoints Used:**
|
||||
<<REPEAT: endpoint>>
|
||||
|
||||
- `{{method}} {{endpoint_path}}` - {{endpoint_purpose}}
|
||||
<</REPEAT>>
|
||||
|
||||
**Integration Notes:** {{integration_considerations}}
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: external_api}
|
||||
|
||||
### Stripe API
|
||||
|
||||
- **Purpose:** Payment processing and subscription management
|
||||
- **Documentation:** https://stripe.com/docs/api
|
||||
- **Base URL(s):** `https://api.stripe.com/v1`
|
||||
- **Authentication:** Bearer token with secret key
|
||||
- **Rate Limits:** 100 requests per second
|
||||
|
||||
**Key Endpoints Used:**
|
||||
|
||||
- `POST /customers` - Create customer profiles
|
||||
- `POST /payment_intents` - Process payments
|
||||
- `POST /subscriptions` - Manage subscriptions
|
||||
@{/example}
|
||||
|
||||
^^/CONDITION: has_external_apis^^
|
||||
|
||||
[[LLM: After presenting external APIs (or noting their absence), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Core Workflows
|
||||
|
||||
[[LLM: Illustrate key system workflows using sequence diagrams:
|
||||
|
||||
1. Identify critical user journeys from PRD
|
||||
2. Show component interactions including external APIs
|
||||
3. Include error handling paths
|
||||
4. Document async operations
|
||||
5. Create both high-level and detailed diagrams as needed
|
||||
|
||||
Focus on workflows that clarify architecture decisions or complex interactions.
|
||||
|
||||
After presenting the workflow diagrams, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## REST API Spec
|
||||
|
||||
[[LLM: If the project includes a REST API:
|
||||
|
||||
1. Create an OpenAPI 3.0 specification
|
||||
2. Include all endpoints from epics/stories
|
||||
3. Define request/response schemas based on data models
|
||||
4. Document authentication requirements
|
||||
5. Include example requests/responses
|
||||
|
||||
Use YAML format for better readability. If no REST API, skip this section.]]
|
||||
|
||||
^^CONDITION: has_rest_api^^
|
||||
|
||||
```yaml
|
||||
openapi: 3.0.0
|
||||
info:
|
||||
title: { { api_title } }
|
||||
version: { { api_version } }
|
||||
description: { { api_description } }
|
||||
|
||||
servers:
|
||||
- url: { { api_base_url } }
|
||||
description: { { environment } }
|
||||
# ... OpenAPI specification continues
|
||||
```
|
||||
|
||||
^^/CONDITION: has_rest_api^^
|
||||
|
||||
[[LLM: After presenting the REST API spec (or skipping if not applicable), apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Database Schema
|
||||
|
||||
[[LLM: Transform the conceptual data models into concrete database schemas:
|
||||
|
||||
1. Use the database type(s) selected in Tech Stack
|
||||
2. Create schema definitions using appropriate notation
|
||||
3. Include indexes, constraints, and relationships
|
||||
4. Consider performance and scalability
|
||||
5. For NoSQL, show document structures
|
||||
|
||||
Present schema in format appropriate to database type (SQL DDL, JSON schema, etc.)
|
||||
|
||||
After presenting the database schema, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Source Tree
|
||||
|
||||
[[LLM: Provide an ASCII or Mermaid diagram representing the project's proposed folder structure based on information we have aligned on to this point such as monorepo vs polyrepo vs monolith vs microservices. The following is a general example, but is very project and technology dependant. Immediately upon render of the section, execute tasks#advanced-elicitation display.]]
|
||||
[[LLM: Create a project folder structure that reflects:
|
||||
|
||||
1. The chosen repository structure (monorepo/polyrepo)
|
||||
2. The service architecture (monolith/microservices/serverless)
|
||||
3. The selected tech stack and languages
|
||||
4. Component organization from above
|
||||
5. Best practices for the chosen frameworks
|
||||
6. Clear separation of concerns
|
||||
|
||||
Adapt the structure based on project needs. For monorepos, show service separation. For serverless, show function organization. Include language-specific conventions.
|
||||
|
||||
After presenting the structure, apply `tasks#advanced-elicitation` protocol to refine based on user feedback.]]
|
||||
|
||||
```plaintext
|
||||
{project-root}/
|
||||
├── .github/ # CI/CD workflows (e.g., GitHub Actions)
|
||||
{{project-root}}/
|
||||
├── .github/ # CI/CD workflows
|
||||
│ └── workflows/
|
||||
│ └── main.yml
|
||||
├── .vscode/ # VSCode settings (optional)
|
||||
│ └── settings.json
|
||||
├── build/ # Compiled output (if applicable, often git-ignored)
|
||||
├── config/ # Static configuration files (if any)
|
||||
├── docs/ # Project documentation (PRD, Arch, etc.)
|
||||
│ ├── index.md
|
||||
│ └── ... (other .md files)
|
||||
├── infra/ # Infrastructure as Code (e.g., CDK, Terraform)
|
||||
│ └── lib/
|
||||
│ └── bin/
|
||||
├── node_modules/ / venv / target/ # Project dependencies (git-ignored)
|
||||
├── scripts/ # Utility scripts (build, deploy helpers, etc.)
|
||||
├── build/ # Compiled output (git-ignored)
|
||||
├── config/ # Configuration files
|
||||
├── docs/ # Project documentation
|
||||
│ ├── PRD.md
|
||||
│ ├── architecture.md
|
||||
│ └── ...
|
||||
├── infra/ # Infrastructure as Code
|
||||
│ └── {{iac-structure}}
|
||||
├── {{dependencies-dir}}/ # Dependencies (git-ignored)
|
||||
├── scripts/ # Utility scripts
|
||||
├── src/ # Application source code
|
||||
│ ├── backend/ # Backend-specific application code (if distinct frontend exists)
|
||||
│ │ ├── core/ # Core business logic, domain models
|
||||
│ │ ├── services/ # Business services, orchestrators
|
||||
│ │ ├── adapters/ # Adapters to external systems (DB, APIs)
|
||||
│ │ ├── controllers/ / routes/ # API endpoint handlers
|
||||
│ │ └── main.ts / app.py # Backend application entry point
|
||||
│ ├── frontend/ # Placeholder: See Frontend Architecture Doc for details if used
|
||||
│ ├── shared/ / common/ # Code shared (e.g., types, utils, domain models if applicable)
|
||||
│ │ └── types/
|
||||
│ └── main.ts / index.ts / app.ts # Main application entry point (if not using backend/frontend split above)
|
||||
├── stories/ # Generated story files for development (optional)
|
||||
│ └── epic1/
|
||||
├── test/ # Automated tests
|
||||
│ ├── unit/ # Unit tests (mirroring src structure)
|
||||
│ ├── integration/ # Integration tests
|
||||
│ └── e2e/ # End-to-end tests
|
||||
├── .env.example # Example environment variables
|
||||
│ └── {{source-structure}}
|
||||
├── tests/ # Test files
|
||||
│ ├── unit/
|
||||
│ ├── integration/
|
||||
│ └── e2e/
|
||||
├── .env.example # Environment variables template
|
||||
├── .gitignore # Git ignore rules
|
||||
├── package.json / requirements.txt / pom.xml # Project manifest and dependencies
|
||||
├── tsconfig.json / pyproject.toml # Language-specific configuration (if applicable)
|
||||
├── Dockerfile # Docker build instructions (if applicable)
|
||||
└── README.md # Project overview and setup instructions
|
||||
├── {{package-manifest}} # Dependencies manifest
|
||||
├── {{config-files}} # Language/framework configs
|
||||
└── README.md # Project documentation
|
||||
```
|
||||
|
||||
## External APIs
|
||||
@{example: monorepo-structure}
|
||||
project-root/
|
||||
├── packages/
|
||||
│ ├── api/ # Backend API service
|
||||
│ ├── web/ # Frontend application
|
||||
│ ├── shared/ # Shared utilities/types
|
||||
│ └── infrastructure/ # IaC definitions
|
||||
├── scripts/ # Monorepo management scripts
|
||||
└── package.json # Root package.json with workspaces
|
||||
@{/example}
|
||||
|
||||
[[LLM: List the External API name proposed if needed - if unsure you can suggest or ask the user when it seems we will need to rely on some external services depending on the project requirements. List the URL to doc or API Spec (openapi / swagger url) - if you are unsure as user to provide after you explain when we need a given API or similar. For each API we need the following information]]
|
||||
|
||||
### {External API Name} API
|
||||
|
||||
- **Purpose:** {What service does this API provide?}
|
||||
- **Base URL(s):** {e.g., `https://some-saas/api/v1/`}
|
||||
- **Authentication/Authorization:** {Describe how access is controlled.}
|
||||
- **Endpoints Used**
|
||||
- Identify the endpoint - short statement of purpose to use it
|
||||
|
||||
## REST API Spec
|
||||
|
||||
[[LLM: Create OpenAPI Spec (Swagger) proposed if proposing a rest api]]
|
||||
|
||||
## Data Models
|
||||
|
||||
[[LLM: List major data models, discussing with the user why you have listed the specific data models]]
|
||||
|
||||
## Database Schema
|
||||
|
||||
[[LLM: Create a database schema model proposed to meet the project requirements. For each schema, include the purpose of each schema model]]
|
||||
|
||||
## Core Workflow
|
||||
|
||||
{ Illustrate key or complex workflows using mermaid sequence diagrams. Can have high level tying the full project together, and also smaller epic level sequence diagrams. }
|
||||
|
||||
## Tech Stack
|
||||
|
||||
[[LLM: This section outlines the definitive technology choices for the project. These selections should be made after a thorough understanding of the project's requirements, components, data models, and core workflows. The Architect Agent should guide the user through these decisions, ensuring each choice is justified and recorded accurately in the table below.]]
|
||||
|
||||
[[LLM: This table is the **single source of truth** for all technology selections. Other architecture documents (e.g., Frontend Architecture) must refer to these choices and elaborate on their specific application rather than re-defining them.]]
|
||||
|
||||
[[LLM: Key decisions to discuss and finalize here, which will then be expanded upon and formally documented in the detailed stack table below, include considerations such as:
|
||||
|
||||
- Preferred Starter Template Frontend: { Url to template or starter, if used }
|
||||
- Preferred Starter Template Backend: { Url to template or starter, if used }
|
||||
- Primary Language(s) & Version(s): {e.g., TypeScript 5.x, Python 3.11 - Specify exact versions, e.g., `5.2.3`}
|
||||
- Primary Runtime(s) & Version(s): {e.g., Node.js 22.x - Specify exact versions, e.g., `22.0.1`}
|
||||
|
||||
Must be definitive selections; do not list open-ended choices (e.g., for web scraping, pick one tool, not two). Specify exact versions (e.g., `18.2.0`). If 'Latest' is used, it implies the latest stable version _at the time of this document's last update_, and the specific version (e.g., `xyz-library@2.3.4`) should be recorded. Pinning versions is strongly preferred to avoid unexpected breaking changes for the AI agent.]]
|
||||
|
||||
- Cloud Provider(s): {e.g., AWS, Azure, GCP, On-premise}
|
||||
- Core Services Used: {List key managed services - e.g., Lambda, S3, Kubernetes Engine, RDS, Kafka}
|
||||
|
||||
| Category | Technology | Version | Purpose |
|
||||
| :------- | :--------- | :------ | :------ |
|
||||
[[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Infrastructure and Deployment
|
||||
|
||||
- Infrastructure as Code (IaC): {Tool used - e.g., AWS CDK, Terraform...} - Location: {Link to IaC code repo/directory}
|
||||
- Deployment Strategy: {e.g., CI/CD pipeline with automated promotions, Blue/Green, Canary} - Tools: {e.g., Jenkins, GitHub Actions, GitLab CI}
|
||||
- Environments: {List environments - e.g., Development, Staging, Production}
|
||||
- Environment Promotion: {Describe steps, e.g., `dev` -\> `staging` (manual approval / automated tests pass) -\> `production` (automated after tests pass and optional manual approval)}
|
||||
- Rollback Strategy: {e.g., Automated rollback on health check failure post-deployment, Manual trigger via CI/CD job, IaC state rollback. Specify primary mechanism.}
|
||||
[[LLM: Define the deployment architecture and practices:
|
||||
|
||||
1. Use IaC tool selected in Tech Stack
|
||||
2. Choose deployment strategy appropriate for the architecture
|
||||
3. Define environments and promotion flow
|
||||
4. Establish rollback procedures
|
||||
5. Consider security, monitoring, and cost optimization
|
||||
|
||||
Get user input on deployment preferences and CI/CD tool choices.]]
|
||||
|
||||
### Infrastructure as Code
|
||||
|
||||
- **Tool:** {{iac_tool}} {{version}}
|
||||
- **Location:** `{{iac_directory}}`
|
||||
- **Approach:** {{iac_approach}}
|
||||
|
||||
### Deployment Strategy
|
||||
|
||||
- **Strategy:** {{deployment_strategy}}
|
||||
- **CI/CD Platform:** {{cicd_platform}}
|
||||
- **Pipeline Configuration:** `{{pipeline_config_location}}`
|
||||
|
||||
### Environments
|
||||
|
||||
<<REPEAT: environment>>
|
||||
|
||||
- **{{env_name}}:** {{env_purpose}} - {{env_details}}
|
||||
<</REPEAT>>
|
||||
|
||||
### Environment Promotion Flow
|
||||
|
||||
```
|
||||
{{promotion_flow_diagram}}
|
||||
```
|
||||
|
||||
### Rollback Strategy
|
||||
|
||||
- **Primary Method:** {{rollback_method}}
|
||||
- **Trigger Conditions:** {{rollback_triggers}}
|
||||
- **Recovery Time Objective:** {{rto}}
|
||||
|
||||
[[LLM: After presenting the infrastructure and deployment section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Error Handling Strategy
|
||||
|
||||
- **General Approach:** {e.g., Use exceptions as primary mechanism, return error codes/tuples for specific modules, clearly defined custom error types hierarchy.}
|
||||
- **Logging:**
|
||||
- Library/Method: {e.g., `console.log/error` (Node.js), Python `logging` module with `structlog`, dedicated logging library like `Pino` or `Serilog`. Specify the chosen library.}
|
||||
- Format: {e.g., JSON, plain text with timestamp and severity. JSON is preferred for structured logging.}
|
||||
- Levels: {e.g., DEBUG, INFO, WARN, ERROR, CRITICAL. Specify standard usage for each.}
|
||||
- Context: {What contextual information must be included? e.g., Correlation ID, User ID (if applicable and safe), Service Name, Operation Name, Key Parameters (sanitized).}
|
||||
- **Specific Handling Patterns:**
|
||||
- External API Calls: {Define retry mechanisms (e.g., exponential backoff, max retries - specify library if one is mandated like `Polly` or `tenacity`), circuit breaker pattern usage (e.g., using `resilience4j` or equivalent - specify if and how), timeout configurations (connect and read timeouts). How are API errors (4xx, 5xx) translated or propagated?}
|
||||
- Internal Errors / Business Logic Exceptions: {How to convert internal errors to user-facing errors if applicable (e.g., generic error messages with a unique ID for support, specific error codes). Are there defined business exception classes?}
|
||||
- Transaction Management: {Approach to ensure data consistency in case of errors during multi-step operations, e.g., database transactions (specify isolation levels if non-default), Saga pattern for distributed transactions (specify orchestrator/choreography and compensation logic).}
|
||||
[[LLM: Define comprehensive error handling approach:
|
||||
|
||||
1. Choose appropriate patterns for the language/framework from Tech Stack
|
||||
2. Define logging standards and tools
|
||||
3. Establish error categories and handling rules
|
||||
4. Consider observability and debugging needs
|
||||
5. Ensure security (no sensitive data in logs)
|
||||
|
||||
This section guides both AI and human developers in consistent error handling.]]
|
||||
|
||||
### General Approach
|
||||
|
||||
- **Error Model:** {{error_model}}
|
||||
- **Exception Hierarchy:** {{exception_structure}}
|
||||
- **Error Propagation:** {{propagation_rules}}
|
||||
|
||||
### Logging Standards
|
||||
|
||||
- **Library:** {{logging_library}} {{version}}
|
||||
- **Format:** {{log_format}}
|
||||
- **Levels:** {{log_levels_definition}}
|
||||
- **Required Context:**
|
||||
- Correlation ID: {{correlation_id_format}}
|
||||
- Service Context: {{service_context}}
|
||||
- User Context: {{user_context_rules}}
|
||||
|
||||
### Error Handling Patterns
|
||||
|
||||
#### External API Errors
|
||||
|
||||
- **Retry Policy:** {{retry_strategy}}
|
||||
- **Circuit Breaker:** {{circuit_breaker_config}}
|
||||
- **Timeout Configuration:** {{timeout_settings}}
|
||||
- **Error Translation:** {{error_mapping_rules}}
|
||||
|
||||
#### Business Logic Errors
|
||||
|
||||
- **Custom Exceptions:** {{business_exception_types}}
|
||||
- **User-Facing Errors:** {{user_error_format}}
|
||||
- **Error Codes:** {{error_code_system}}
|
||||
|
||||
#### Data Consistency
|
||||
|
||||
- **Transaction Strategy:** {{transaction_approach}}
|
||||
- **Compensation Logic:** {{compensation_patterns}}
|
||||
- **Idempotency:** {{idempotency_approach}}
|
||||
|
||||
[[LLM: After presenting the error handling strategy, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Coding Standards
|
||||
|
||||
[[LLM: These standards are mandatory for all code generation by AI agents and human developers. Deviations are not permitted unless explicitly approved and documented as an exception in this section or a linked addendum. Ensure you let the user know they should really review this and also make sections to it as needed during development once this is sharded out to the coding-standards file as this will always be used by the dev agent to ensure it follows standards. Also keep this section as short and lean as possible to not bloat the context with stuff the agent will probably know anyways. The following are possible sections, it all depends on the project and what the user things should be included - use your best judgement to keep it lean but clear to keep a dumb dev agent on the rails. This applies to the child sections also, do not add them if not needed, or strive to keep them succinct.]]
|
||||
[[LLM: These standards are MANDATORY for AI agents. Work with user to define ONLY the critical rules needed to prevent bad code. Explain that:
|
||||
|
||||
- **Primary Runtime(s):** {e.g., Node.js 22.x, Python Runtime for Lambda - refer to Definitive Tech Stack}
|
||||
- **Style Guide & Linter:** {e.g., ESLint with Airbnb config + Prettier; Black, Flake8, MyPy; Go fmt, golint. Specify chosen tools and link to configuration files (e.g., `.eslintrc.js`, `pyproject.toml`). Linter rules are mandatory and must not be disabled without cause.}
|
||||
- **Naming Conventions:**
|
||||
- Variables: `{e.g., camelCase (JavaScript/TypeScript/Java), snake_case (Python/Ruby)}`
|
||||
- Functions/Methods: `{e.g., camelCase (JavaScript/TypeScript/Java), snake_case (Python/Ruby)}`
|
||||
- Classes/Types/Interfaces: `{e.g., PascalCase}`
|
||||
- Constants: `{e.g., UPPER_SNAKE_CASE}`
|
||||
- Files: `{e.g., kebab-case.ts (TypeScript), snake_case.py (Python), PascalCase.java (Java). Be specific per language.}`
|
||||
- Modules/Packages: `{e.g., camelCase or snake_case. Be specific per language.}`
|
||||
- **File Structure:** Adhere to the layout defined in the "Project Structure" section and the Frontend Architecture Document if applicable.
|
||||
- **Unit Test File Organization:** {e.g., `*.test.ts`/`*.spec.ts` co-located with source files; `test_*.py` in a parallel `tests/` directory. Specify chosen convention.}
|
||||
- **Asynchronous Operations:** {e.g., Always use `async`/`await` in TypeScript/JavaScript/Python for promise-based operations; Goroutines/Channels in Go with clear patterns for error propagation and completion; Java `CompletableFuture` or Project Reactor/RxJava if used.}
|
||||
- **Type Safety:** {e.g., Leverage TypeScript strict mode (all flags enabled); Python type hints (enforced by MyPy); Go static typing; Java generics and avoidance of raw types. All new code must be strictly typed.}
|
||||
- _Type Definitions:_ {Location, e.g., `src/common/types.ts`, shared packages, or co-located. Policy on using `any` or equivalent (strongly discouraged, requires justification).}
|
||||
- **Comments & Documentation:**
|
||||
- Code Comments: {Expectations for code comments: Explain _why_, not _what_, for complex logic. Avoid redundant comments. Use standard formats like JSDoc, TSDoc, Python docstrings (Google/NumPy style), GoDoc, JavaDoc.}
|
||||
- READMEs: {Each module/package/service should have a README explaining its purpose, setup, and usage if not trivial.}
|
||||
- **Dependency Management:** {Tool used - e.g., npm/yarn, pip/poetry, Go modules, Maven/Gradle. Policy on adding new dependencies (e.g., approval process, check for existing alternatives, security vulnerability scans). Specify versioning strategy (e.g., prefer pinned versions, use tilde `~` for patches, caret `^` for minor updates - be specific).}
|
||||
1. This section directly controls AI developer behavior
|
||||
2. Keep it minimal - assume AI knows general best practices
|
||||
3. Focus on project-specific conventions and gotchas
|
||||
4. Overly detailed standards bloat context and slow development
|
||||
5. Standards will be extracted to separate file for dev agent use
|
||||
|
||||
### Detailed Language & Framework Conventions
|
||||
For each standard, get explicit user confirmation it's necessary.]]
|
||||
|
||||
[[LLM: For each primary language and framework selected in the "Definitive Tech Stack Selections", the following specific conventions **must** be adhered to. If a chosen technology is not listed below, it implies adherence to its standard, widely accepted best practices and the general guidelines in this document.]]
|
||||
### Core Standards
|
||||
|
||||
#### `{Language/Framework 1 Name, e.g., TypeScript/Node.js}` Specifics
|
||||
- **Languages & Runtimes:** {{languages_and_versions}}
|
||||
- **Style & Linting:** {{linter_config}}
|
||||
- **Test Organization:** {{test_file_convention}}
|
||||
|
||||
- **Immutability:** `{e.g., "Always prefer immutable data structures. Use `Readonly\<T\>`, `ReadonlyArray\<T\>`, `as const` for object/array literals. Avoid direct mutation of objects/arrays passed as props or state. Consider libraries like Immer for complex state updates."}`
|
||||
- **Functional vs. OOP:** `{e.g., "Favor functional programming constructs (map, filter, reduce, pure functions) for data transformation and business logic where practical. Use classes for entities, services with clear state/responsibilities, or when framework conventions (e.g., NestJS) demand."}`
|
||||
- **Error Handling Specifics:** `{e.g., "Always use `Error`objects or extensions thereof for`throw`. Ensure `Promise`rejections are always`Error`objects. Use custom error classes inheriting from a base`AppError` for domain-specific errors."}`
|
||||
- **Null/Undefined Handling:** `{e.g., "Strict null checks (`strictNullChecks`) must be enabled. Avoid `\!` non-null assertion operator; prefer explicit checks, optional chaining (`?.`), or nullish coalescing (`??`). Define clear strategies for optional function parameters and return types."}`
|
||||
- **Module System:** `{e.g., "Use ESModules (`import`/`export`) exclusively. Avoid CommonJS (`require`/`module.exports`) in new code."}`
|
||||
- **Logging Specifics:** `{e.g., "Use the chosen structured logging library. Log messages must include a correlation ID. Do not log sensitive PII. Use appropriate log levels."}`
|
||||
- **Framework Idioms (e.g., for NestJS/Express):** `{e.g., "NestJS: Always use decorators for defining modules, controllers, services, DTOs. Adhere strictly to the defined module structure and dependency injection patterns. Express: Define middleware patterns, routing structure."}`
|
||||
- **Key Library Usage Conventions:** `{e.g., "When using Axios, create a single configured instance. For date/time, use {date-fns/Luxon/Day.js} and avoid native `Date` object for manipulations."}`
|
||||
- **Code Generation Anti-Patterns to Avoid:** `{e.g., "Avoid overly nested conditional logic (max 2-3 levels). Avoid single-letter variable names (except for trivial loop counters like `i`, `j`, `k`). Do not write code that bypasses framework security features (e.g., ORM query builders)."}`
|
||||
### Naming Conventions
|
||||
|
||||
#### `{Language/Framework 2 Name, e.g., Python}` Specifics:
|
||||
[[LLM: Only include if deviating from language defaults]]
|
||||
|
||||
- **Immutability:** `{e.g., "Use tuples for immutable sequences. For classes, consider `@dataclass(frozen=True)`. Be mindful of mutable default arguments."}`
|
||||
- **Functional vs. OOP:** `{e.g., "Employ classes for representing entities and services. Use functions for stateless operations. List comprehensions/generator expressions are preferred over `map/filter` for readability."}`
|
||||
- **Error Handling Specifics:** `{e.g., "Always raise specific, custom exceptions inheriting from a base `AppException`. Use `try-except-else-finally`blocks appropriately. Avoid broad`except Exception:` clauses without re-raising or specific handling."}`
|
||||
- **Resource Management:** `{e.g., "Always use `with` statements for resources like files or DB connections to ensure they are properly closed."}`
|
||||
- **Type Hinting:** `{e.g., "All new functions and methods must have full type hints. Run MyPy in CI. Strive for `disallow_untyped_defs = True`."}`
|
||||
- **Logging Specifics:** `{e.g., "Use the `logging`module configured for structured output (e.g., with`python-json-logger`). Include correlation IDs."}`
|
||||
- **Framework Idioms (e.g., for Django/Flask/FastAPI):** `{e.g., "Django: Follow fat models, thin views pattern. Use ORM conventions. FastAPI: Utilize Pydantic for request/response models and dependency injection for services."}`
|
||||
- **Key Library Usage Conventions:** `{e.g., "For HTTP requests, use `httpx`or`requests`with explicit timeout settings. For data manipulation, prefer`pandas` where appropriate but be mindful of performance."}`
|
||||
| Element | Convention | Example |
|
||||
| :-------- | :------------------- | :---------------- |
|
||||
| Variables | {{var_convention}} | {{var_example}} |
|
||||
| Functions | {{func_convention}} | {{func_example}} |
|
||||
| Classes | {{class_convention}} | {{class_example}} |
|
||||
| Files | {{file_convention}} | {{file_example}} |
|
||||
|
||||
#### `{Add more Language/Framework sections as needed...}`
|
||||
### Critical Rules
|
||||
|
||||
- **{Consider other things that the trained LLM Dev Agent could potentially be random about specific to the chosen language technologies and platforms that it should be reminded of here}**
|
||||
[[LLM: List ONLY rules that AI might violate or project-specific requirements. Examples:
|
||||
|
||||
- "Never use console.log in production code - use logger"
|
||||
- "All API responses must use ApiResponse wrapper type"
|
||||
- "Database queries must use repository pattern, never direct ORM"
|
||||
|
||||
Avoid obvious rules like "use SOLID principles" or "write clean code"]]
|
||||
|
||||
<<REPEAT: critical_rule>>
|
||||
|
||||
- **{{rule_name}}:** {{rule_description}}
|
||||
<</REPEAT>>
|
||||
|
||||
### Language-Specific Guidelines
|
||||
|
||||
[[LLM: Add ONLY if critical for preventing AI mistakes. Most teams don't need this section.]]
|
||||
|
||||
^^CONDITION: has_language_specifics^^
|
||||
|
||||
#### {{language_name}} Specifics
|
||||
|
||||
<<REPEAT: language_rule>>
|
||||
|
||||
- **{{rule_topic}}:** {{rule_detail}}
|
||||
<</REPEAT>>
|
||||
|
||||
^^/CONDITION: has_language_specifics^^
|
||||
|
||||
[[LLM: After presenting the coding standards, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Test Strategy and Standards
|
||||
|
||||
[[LLM: Work with the user to determine the test strategy. Unit test framework, test organization, Test coverage desired, Build then test or TDD, integration testing approach, integration testing with local or remote resources, any mocking for integration tests and then what? for example if using dynamo, will we use in memory ddb, docker ddb, remote test db instance etc... Consider this for all proposed technologies and what makes sense to test locally or remote. Use any info that follows as needed. This section is NOT going to be read directly by the dev agent as it can get long, the minimum basics the agent needs to know will be listed in coding standards such as what the unit or integration test library is and any specific standard of style the dev needs to know. If the qa agent is used, that agent will be familiar and review this section.]]
|
||||
[[LLM: Work with user to define comprehensive test strategy:
|
||||
|
||||
- **Tools:** {Reiterate primary testing frameworks and libraries from Tech Stack, e.g., Jest, Playwright, PyTest, JUnit, Testcontainers.}
|
||||
- **Unit Tests:**
|
||||
- **Scope:** {Test individual functions, methods, classes, or small modules in isolation. Focus on business logic, algorithms, and transformation rules.}
|
||||
- **Location:** {e.g., `*.test.ts`/`*.spec.ts` co-located with source files; `test_*.py` in a parallel `tests/` directory, following language conventions.}
|
||||
- **Mocking/Stubbing:** {Specify chosen mocking library (e.g., Jest mocks, `unittest.mock` in Python, Mockito for Java). Mock all external dependencies (network calls, file system, databases, time).}
|
||||
- **AI Agent Responsibility:** {AI Agent must generate unit tests covering all public methods, significant logic paths, edge cases, and error conditions for any new or modified code.}
|
||||
- **Integration Tests:**
|
||||
- **Scope:** {Test the interaction between several components or services within the application boundary. E.g., API endpoint to service layer to database (using a test database or in-memory version).}
|
||||
- **Location:** {e.g., `/tests/integration` or `/src/integration-test` (Java).}
|
||||
- **Environment:** {Specify how dependencies are handled (e.g., Testcontainers for databases/external services, in-memory databases, dedicated test environment).}
|
||||
- **AI Agent Responsibility:** {AI Agent may be tasked with generating integration tests for key service interactions or API endpoints based on specifications.}
|
||||
- **End-to-End (E2E) Tests:**
|
||||
- **Scope:** {Validate complete user flows or critical paths through the system from the user's perspective (e.g., UI interaction, API call sequence).}
|
||||
- **Tools:** {Reiterate E2E testing tools from Tech Stack (e.g., Playwright, Cypress, Selenium).}
|
||||
- **AI Agent Responsibility:** {AI Agent may be tasked with generating E2E test stubs or scripts based on user stories or BDD scenarios. Focus on critical happy paths and key error scenarios.}
|
||||
- **Test Coverage:**
|
||||
- **Target:** {Specify target code coverage if any (e.g., 80% line/branch coverage for unit tests). This is a guideline; quality of tests is paramount over raw coverage numbers.}
|
||||
- **Measurement:** {Tool used for coverage reports (e.g., Istanbul/nyc, Coverage.py, JaCoCo).}
|
||||
- **Mocking/Stubbing Strategy (General):** {Beyond specific test types, outline general principles. e.g., "Prefer fakes or test doubles over extensive mocking where it improves test clarity and maintainability. Strive for tests that are fast, reliable, and isolated."}
|
||||
- **Test Data Management:** {How is test data created, managed, and isolated? E.g., factories, fixtures, setup/teardown scripts, dedicated test data generation tools.}
|
||||
1. Use test frameworks from Tech Stack
|
||||
2. Decide on TDD vs test-after approach
|
||||
3. Define test organization and naming
|
||||
4. Establish coverage goals
|
||||
5. Determine integration test infrastructure
|
||||
6. Plan for test data and external dependencies
|
||||
|
||||
Note: Basic info goes in Coding Standards for dev agent. This detailed section is for QA agent and team reference. Apply `tasks#advanced-elicitation` after initial draft.]]
|
||||
|
||||
### Testing Philosophy
|
||||
|
||||
- **Approach:** {{test_approach}}
|
||||
- **Coverage Goals:** {{coverage_targets}}
|
||||
- **Test Pyramid:** {{test_distribution}}
|
||||
|
||||
### Test Types and Organization
|
||||
|
||||
#### Unit Tests
|
||||
|
||||
- **Framework:** {{unit_test_framework}} {{version}}
|
||||
- **File Convention:** {{unit_test_naming}}
|
||||
- **Location:** {{unit_test_location}}
|
||||
- **Mocking Library:** {{mocking_library}}
|
||||
- **Coverage Requirement:** {{unit_coverage}}
|
||||
|
||||
**AI Agent Requirements:**
|
||||
|
||||
- Generate tests for all public methods
|
||||
- Cover edge cases and error conditions
|
||||
- Follow AAA pattern (Arrange, Act, Assert)
|
||||
- Mock all external dependencies
|
||||
|
||||
#### Integration Tests
|
||||
|
||||
- **Scope:** {{integration_scope}}
|
||||
- **Location:** {{integration_test_location}}
|
||||
- **Test Infrastructure:**
|
||||
<<REPEAT: test_dependency>>
|
||||
- **{{dependency_name}}:** {{test_approach}} ({{test_tool}})
|
||||
<</REPEAT>>
|
||||
|
||||
@{example: test_dependencies}
|
||||
|
||||
- **Database:** In-memory H2 for unit tests, Testcontainers PostgreSQL for integration
|
||||
- **Message Queue:** Embedded Kafka for tests
|
||||
- **External APIs:** WireMock for stubbing
|
||||
@{/example}
|
||||
|
||||
#### End-to-End Tests
|
||||
|
||||
- **Framework:** {{e2e_framework}} {{version}}
|
||||
- **Scope:** {{e2e_scope}}
|
||||
- **Environment:** {{e2e_environment}}
|
||||
- **Test Data:** {{e2e_data_strategy}}
|
||||
|
||||
### Test Data Management
|
||||
|
||||
- **Strategy:** {{test_data_approach}}
|
||||
- **Fixtures:** {{fixture_location}}
|
||||
- **Factories:** {{factory_pattern}}
|
||||
- **Cleanup:** {{cleanup_strategy}}
|
||||
|
||||
### Continuous Testing
|
||||
|
||||
- **CI Integration:** {{ci_test_stages}}
|
||||
- **Performance Tests:** {{perf_test_approach}}
|
||||
- **Security Tests:** {{security_test_approach}}
|
||||
|
||||
[[LLM: After presenting the test strategy section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Security
|
||||
|
||||
[[LLM: Outline key security considerations relevant to the codebase. These are mandatory and must be actively addressed by the AI agent during development.]]
|
||||
[[LLM: Define MANDATORY security requirements for AI and human developers:
|
||||
|
||||
- **Input Sanitization/Validation:** {Specify library/method for ALL external inputs (API requests, user-provided data, file uploads). E.g., 'Use class-validator with NestJS DTOs for all API inputs; all validation rules must be defined in DTOs.' For other languages, 'Use {validation_library} for all external inputs; define schemas and constraints.' Validation must occur at the boundary before processing.}
|
||||
- **Output Encoding:** {Specify where and how output encoding should be performed to prevent XSS and other injection attacks. E.g., 'All dynamic data rendered in HTML templates must be contextually auto-escaped by the template engine (specify engine and confirm default behavior). If generating HTML/XML/JSON manually, use approved encoding libraries like {encoder_library_name}.'}
|
||||
- **Secrets Management:** {Reference `docs/environment-vars.md` regarding storage for different environments. In code, access secrets _only_ through a designated configuration module/service. Never hardcode secrets, include them in source control, or log them. Use specific tools for local development if applicable (e.g., Doppler, .env files NOT committed).}
|
||||
- **Dependency Security:** {Policy on checking for vulnerable dependencies. E.g., 'Run automated vulnerability scans (e.g., `npm audit`, `pip-audit`, Snyk, Dependabot alerts) as part of CI. Update vulnerable dependencies promptly based on severity.' Policy on adding new dependencies (vetting process).}
|
||||
- **Authentication/Authorization Checks:** {Where and how should these be enforced? E.g., 'All API endpoints (except explicitly public ones) must enforce authentication using the central auth module/middleware. Authorization (permission/role checks) must be performed at the service layer or entry point for protected resources.' Define patterns for implementing these checks.}
|
||||
- **Principle of Least Privilege (Implementation):** {e.g., 'Database connection users must have only the necessary permissions (SELECT, INSERT, UPDATE, DELETE) for the specific tables/schemas they access. IAM roles for cloud services must be narrowly scoped to the required actions and resources.'}
|
||||
- **API Security (General):** {e.g., 'Enforce HTTPS. Implement rate limiting and throttling (specify tool/method). Use standard HTTP security headers (CSP, HSTS, X-Frame-Options, etc. - specify which ones and their configuration). Follow REST/GraphQL security best practices.'}
|
||||
- **Error Handling & Information Disclosure:** {Ensure error messages do not leak sensitive information (stack traces, internal paths, detailed SQL errors) to the end-user. Log detailed errors server-side, provide generic messages or error IDs to the client.}
|
||||
- **Regular Security Audits/Testing:** {Mention if planned, e.g., penetration testing, static/dynamic analysis tool usage in CI (SAST/DAST).}
|
||||
- **{Other relevant practices, e.g., File upload security, Session management security, Data encryption at rest and in transit beyond HTTPS if specific requirements exist.}**
|
||||
1. Focus on implementation-specific rules
|
||||
2. Reference security tools from Tech Stack
|
||||
3. Define clear patterns for common scenarios
|
||||
4. These rules directly impact code generation
|
||||
5. Work with user to ensure completeness without redundancy]]
|
||||
|
||||
### Input Validation
|
||||
|
||||
- **Validation Library:** {{validation_library}}
|
||||
- **Validation Location:** {{where_to_validate}}
|
||||
- **Required Rules:**
|
||||
- All external inputs MUST be validated
|
||||
- Validation at API boundary before processing
|
||||
- Whitelist approach preferred over blacklist
|
||||
|
||||
### Authentication & Authorization
|
||||
|
||||
- **Auth Method:** {{auth_implementation}}
|
||||
- **Session Management:** {{session_approach}}
|
||||
- **Required Patterns:**
|
||||
- {{auth_pattern_1}}
|
||||
- {{auth_pattern_2}}
|
||||
|
||||
### Secrets Management
|
||||
|
||||
- **Development:** {{dev_secrets_approach}}
|
||||
- **Production:** {{prod_secrets_service}}
|
||||
- **Code Requirements:**
|
||||
- NEVER hardcode secrets
|
||||
- Access via configuration service only
|
||||
- No secrets in logs or error messages
|
||||
|
||||
### API Security
|
||||
|
||||
- **Rate Limiting:** {{rate_limit_implementation}}
|
||||
- **CORS Policy:** {{cors_configuration}}
|
||||
- **Security Headers:** {{required_headers}}
|
||||
- **HTTPS Enforcement:** {{https_approach}}
|
||||
|
||||
### Data Protection
|
||||
|
||||
- **Encryption at Rest:** {{encryption_at_rest}}
|
||||
- **Encryption in Transit:** {{encryption_in_transit}}
|
||||
- **PII Handling:** {{pii_rules}}
|
||||
- **Logging Restrictions:** {{what_not_to_log}}
|
||||
|
||||
### Dependency Security
|
||||
|
||||
- **Scanning Tool:** {{dependency_scanner}}
|
||||
- **Update Policy:** {{update_frequency}}
|
||||
- **Approval Process:** {{new_dep_process}}
|
||||
|
||||
### Security Testing
|
||||
|
||||
- **SAST Tool:** {{static_analysis}}
|
||||
- **DAST Tool:** {{dynamic_analysis}}
|
||||
- **Penetration Testing:** {{pentest_schedule}}
|
||||
|
||||
[[LLM: After presenting the security section, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------ | ---- | ------- | ----------- | ------ |
|
||||
[[LLM: Track document versions and changes]]
|
||||
|
||||
--- Below, Prompt for Design Architect (If Project has UI) To Produce Front End Architecture ----
|
||||
| Date | Version | Description | Author |
|
||||
| :------- | :------ | :---------------------------- | :--------- |
|
||||
| {{date}} | 1.0.0 | Initial architecture document | {{author}} |
|
||||
|
||||
---
|
||||
|
||||
## Checklist Results Report
|
||||
|
||||
[[LLM: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the `architect-checklist` and populate results here.]]
|
||||
|
||||
---
|
||||
|
||||
## Next Steps
|
||||
|
||||
[[LLM: After completing the architecture:
|
||||
|
||||
1. If project has UI components:
|
||||
|
||||
- Recommend engaging Design Architect agent
|
||||
- Use "Frontend Architecture Mode"
|
||||
- Provide this document as input
|
||||
|
||||
2. For all projects:
|
||||
|
||||
- Review with Product Owner
|
||||
- Begin story implementation with Dev agent
|
||||
- Set up infrastructure with DevOps agent
|
||||
|
||||
3. Include specific prompts for next agents if needed]]
|
||||
|
||||
^^CONDITION: has_ui^^
|
||||
|
||||
### Design Architect Prompt
|
||||
|
||||
[[LLM: Create a brief prompt to hand off to Design Architect for Frontend Architecture creation. Include:
|
||||
|
||||
- Reference to this architecture document
|
||||
- Key UI requirements from PRD
|
||||
- Any frontend-specific decisions made here
|
||||
- Request for detailed frontend architecture]]
|
||||
|
||||
^^/CONDITION: has_ui^^
|
||||
|
||||
### Developer Handoff
|
||||
|
||||
[[LLM: Create a brief prompt for developers starting implementation. Include:
|
||||
|
||||
- Reference to this architecture and coding standards
|
||||
- First epic/story to implement
|
||||
- Key technical decisions to follow]]
|
||||
|
||||
Reference in New Issue
Block a user