create-architecture

name	create-architecture
description	Create architecture docs, stack choices, Mermaid diagrams, cost/ops estimates, module maps, or system design files. Use when mapping full architecture or changing structure.

Create Architecture

Required architecture template

# Architecture — <system/feature>

## Scope
- Covered system/feature.
- Non-goals.

## Current structure
- `<path>` — responsibility.
- Important dependencies and ownership.

## Stack
| Layer | Current / proposed choice | Reason | Alternatives rejected |
|---|---|---|---|
| Frontend | <framework/library> | <why> | <alternatives> |
| Backend/API | <framework/runtime> | <why> | <alternatives> |
| Data/storage | <database/cache/blob/etc.> | <why> | <alternatives> |
| Infra/deploy | <platform/hosting/queue/etc.> | <why> | <alternatives> |

## Target structure
- Modules and boundaries.
- Data/control flow.
- Required Mermaid diagram when architecture spans more than one module/service.

```mermaid
flowchart TD
  User[User] --> UI[Frontend]
  UI --> API[API / Backend]
  API --> Data[(Data store)]

Contracts

• Public APIs, schemas, events, side effects, and invariants.

Cost / operations estimate

Area	Approx cost / complexity	Notes
Runtime/hosting	<low/medium/high or €/month estimate>
Database/storage	<low/medium/high or €/month estimate>
Third-party APIs	<low/medium/high or €/month estimate>
Maintenance	<low/medium/high>

State assumptions clearly. Use rough ranges when exact prices are unknown.

Risks

• Coupling, migration hazards, testing impact, security/privacy, scaling limits, vendor lock-in, cost surprises.

Decisions

• Decision.
• Reason.
• Alternatives rejected.

Verification plan

• Architecture checks, tests, migration checks, load/perf checks, or manual review needed.