code-ai-installer 2.5.0 → 3.0.0

package/locales/en/.agents/skills/api-contracts/agents/claude.json

@@ -1,17 +0,0 @@
-{
-  "name": "api-contracts",
-  "display_name": "API Contracts",
-  "description": "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns.",
-  "default_prompt": "Use $api-contracts when the task matches the \"API Contracts\" skill.",
-  "triggers": [
-    "api-contracts",
-    "api contracts",
-    "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns"
-  ],
-  "capabilities": [
-    "api",
-    "contracts"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/api-contracts/agents/copilot.json

@@ -1,17 +0,0 @@
-{
-  "name": "api-contracts",
-  "display_name": "API Contracts",
-  "description": "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns.",
-  "default_prompt": "Use $api-contracts when the task matches the \"API Contracts\" skill.",
-  "triggers": [
-    "api-contracts",
-    "api contracts",
-    "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns"
-  ],
-  "capabilities": [
-    "api",
-    "contracts"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/api-contracts/agents/gemini.json

@@ -1,17 +0,0 @@
-{
-  "name": "api-contracts",
-  "display_name": "API Contracts",
-  "description": "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns.",
-  "default_prompt": "Use $api-contracts when the task matches the \"API Contracts\" skill.",
-  "triggers": [
-    "api-contracts",
-    "api contracts",
-    "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns"
-  ],
-  "capabilities": [
-    "api",
-    "contracts"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/api-contracts/agents/kimi.yaml

@@ -1,13 +0,0 @@
-name: "api-contracts"
-display_name: "API Contracts"
-description: "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns."
-default_prompt: "Use $api-contracts when the task matches the \"API Contracts\" skill."
-triggers:
-  - "api-contracts"
-  - "api contracts"
-  - "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns"
-capabilities:
-  - "api"
-  - "contracts"
-tools: []
-implicit_invocation: true

package/locales/en/.agents/skills/api-contracts/agents/openai.yaml

@@ -1,8 +0,0 @@
-interface:
-  display_name: "API Contracts"
-  short_description: "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalab…"
-  default_prompt: "Use $api-contracts when the task matches the \"API Contracts\" skill."
-dependencies:
-  tools: []
-policy:
-  allow_implicit_invocation: true

package/locales/en/.agents/skills/api-contracts/agents/qwen.json

@@ -1,17 +0,0 @@
-{
-  "name": "api-contracts",
-  "display_name": "API Contracts",
-  "description": "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns.",
-  "default_prompt": "Use $api-contracts when the task matches the \"API Contracts\" skill.",
-  "triggers": [
-    "api-contracts",
-    "api contracts",
-    "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns"
-  ],
-  "capabilities": [
-    "api",
-    "contracts"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/api-contracts/agents/skill.yaml

@@ -1,21 +0,0 @@
-version: 1
-name: "api-contracts"
-display_name: "API Contracts"
-description: "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns."
-default_prompt: "Use $api-contracts when the task matches the \"API Contracts\" skill."
-triggers:
-  - "api-contracts"
-  - "api contracts"
-  - "API contracts for UX flows — endpoints, schemas, errors, validation, authorization, perf/scalability considerations, idempotency, and integration patterns"
-capabilities:
-  - "api"
-  - "contracts"
-tools: []
-invocation:
-  explicit: true
-  implicit: true
-localization:
-  default_locale: "en"
-  available_locales:
-    - "ru"
-    - "en"

package/locales/en/.agents/skills/architecture-compliance-review/SKILL.md

@@ -1,213 +0,0 @@
----
-name: architecture-compliance-review
-description: Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags.
----
-
-# Skill: Architecture Compliance Review
-
-Review for compliance with the architectural document and ADRs.
-
-**Sections:**
-1. [Expected Architecture](#1-expected)
-2. [Checklist](#2-checklist)
-3. [Automated Detection](#3-detection)
-4. [Red Flags](#4-red-flags)
-5. [Output Template](#5-output)
-
----
-
-## 1. Expected Architecture
-
-### Layer Architecture (Node.js / Express)
-
-```
-┌──────────────────────────┐
-│        Routes            │  ← HTTP routing only, no logic
-├──────────────────────────┤
-│      Middleware           │  ← Auth, validation (Zod), logging
-├──────────────────────────┤
-│      Controllers          │  ← Request/response handling, HTTP concerns
-├──────────────────────────┤
-│       Services            │  ← Business logic, orchestration
-├──────────────────────────┤
-│     Repositories          │  ← Data access (Mongoose), queries
-├──────────────────────────┤
-│        Models             │  ← Schema definitions
-└──────────────────────────┘
-```
-
-### Dependency rules
-
-| Layer | Can depend on | MUST NOT depend on |
-|-------|--------------|-------------------|
-| Routes | Controllers, Middleware | Services, Repos, Models |
-| Middleware | (standalone) | Services, Repos |
-| Controllers | Services | Repos, Models directly |
-| Services | Repos, other Services | `req`, `res`, HTTP concerns |
-| Repos | Models | `req`, `res`, `next`, Services |
-| Models | (standalone) | Anything above |
-
-### Frontend Architecture (React)
-
-```
-┌──────────────────────────┐
-│        Pages              │  ← Route-level components
-├──────────────────────────┤
-│      Components           │  ← UI building blocks (presentational)
-├──────────────────────────┤
-│        Hooks              │  ← State/logic encapsulation
-├──────────────────────────┤
-│       Services/API        │  ← HTTP calls to backend
-├──────────────────────────┤
-│        Store              │  ← Global state (Zustand/RTK)
-└──────────────────────────┘
-```
-
----
-
-## 2. Checklist
-
-### 2.1 Layer Boundaries
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| ARCH-01 | No DB calls (Mongoose) in routes or controllers | 🔴 P0 | ☐ |
-| ARCH-02 | No `req`/`res` objects in services | 🔴 P0 | ☐ |
-| ARCH-03 | No business logic in routes (only routing) | 🟠 P1 | ☐ |
-| ARCH-04 | Controllers delegate to services (no direct repo calls) | 🟠 P1 | ☐ |
-| ARCH-05 | Models are standalone (no imports from layers above) | 🟠 P1 | ☐ |
-
-### 2.2 Module Boundaries
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| ARCH-06 | Service A doesn't import internals of Service B | 🟠 P1 | ☐ |
-| ARCH-07 | No circular dependencies between modules | 🔴 P0 | ☐ |
-| ARCH-08 | Shared code is in `utils/` or `common/`, not copy-pasted | 🟠 P1 | ☐ |
-| ARCH-09 | Feature modules have clear public API (index exports) | 🟡 P2 | ☐ |
-
-### 2.3 Code Size & Complexity
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| ARCH-10 | File < 500 lines (God Object indicator) | 🟠 P1 | ☐ |
-| ARCH-11 | Function < 40 lines (complexity indicator) | 🟠 P1 | ☐ |
-| ARCH-12 | Class/module < 10 public methods | 🟡 P2 | ☐ |
-| ARCH-13 | Cyclomatic complexity reasonable (no deeply nested if/else) | 🟠 P1 | ☐ |
-
-### 2.4 ADR Compliance
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| ARCH-14 | Code follows existing ADR decisions | 🔴 P0 | ☐ |
-| ARCH-15 | New patterns/libraries → ADR created | 🟠 P1 | ☐ |
-| ARCH-16 | DB schema changes → ADR if significant | 🟠 P1 | ☐ |
-| ARCH-17 | Integration changes → ADR created | 🟠 P1 | ☐ |
-
-### 2.5 Naming Conventions
-
-| # | Check | Severity | Status |
-|---|-------|----------|--------|
-| ARCH-18 | Files follow naming convention (`camelCase.js` or `kebab-case.js`) | 🟡 P2 | ☐ |
-| ARCH-19 | Exports match file purpose (not mixed responsibilities) | 🟠 P1 | ☐ |
-| ARCH-20 | Test files co-located or in `__tests__/` consistently | 🟡 P2 | ☐ |
-
----
-
-## 3. Automated Detection
-
-### Grep patterns for boundary violations
-
-```bash
-# 🔴 P0: DB in routes/controllers
-grep_search: Query="mongoose"    Includes=["*/routes/*"]       → DB access in routes!
-grep_search: Query="Model.find"  Includes=["*/controllers/*"]  → DB in controller!
-grep_search: Query=".save()"     Includes=["*/routes/*"]       → DB mutation in route!
-
-# 🔴 P0: HTTP in services
-grep_search: Query="req\."  Includes=["*/services/*"]  → HTTP object in service!
-grep_search: Query="res\."  Includes=["*/services/*"]  → HTTP object in service!
-grep_search: Query="next("  Includes=["*/services/*"]  → Express middleware in service!
-
-# 🟠 P1: Cross-module internals
-grep_search: Query="from '\.\./" Includes=["*/services/*"]  → Check: crossing module boundary?
-
-# 🟠 P1: God Object detection
-find_by_name: Pattern="*.js" Extensions=["js","ts"]
-→ Check: file size > 500 lines?
-
-# 🟡 P2: Copy-paste detection
-grep_search: Query="<duplicated code block>"  → Extract to shared util
-```
-
-### File size audit
-
-```bash
-# Find files > 500 lines
-find_by_name: Pattern="*.js" → for each: check line count
-# If file > 500 lines → P1: God Object risk
-# If function > 40 lines → P1: complexity risk
-```
-
----
-
-## 4. Red Flags
-
-| Red Flag | Pattern | Severity | Indicator |
-|----------|---------|----------|-----------|
-| **Big Ball of Mud** | Everything in one file/folder | 🔴 P0 | File > 1000 lines, no folder structure |
-| **God Object** | One module does everything | 🔴 P0 | Class > 20 methods, file > 500 lines |
-| **Tight Coupling** | Service A depends on internals of B | 🟠 P1 | Deep import paths, circular deps |
-| **Magic** | Implicit side effects, hidden globals | 🟠 P1 | Global state mutation, hidden event listeners |
-| **Layering violation** | DB in routes, HTTP in services | 🔴 P0 | Mongoose in wrong folder |
-| **Missing abstraction** | Same code in 3+ places | 🟠 P1 | Duplicated validation, repeated queries |
-| **Wrong granularity** | Too many tiny files or too few large files | 🟡 P2 | 1-liner utils as separate files |
-
----
-
-## 5. Output Template
-
-```markdown
-# Architecture Compliance Review
-
-**Scope:** <PR/module>
-**Reviewer:** Reviewer Agent
-**Date:** YYYY-MM-DD
-**Reference:** Architecture Doc, ADR-xxx
-
-## Findings
-
-| # | Severity | Check | File:Line | Finding | Fix |
-|---|----------|-------|-----------|---------|-----|
-| 1 | 🔴 P0 | ARCH-01 | `routes/products.js:25` | `Product.find()` called directly in route | Move to `productService.list()` |
-| 2 | 🟠 P1 | ARCH-10 | `services/config.js` | 620 lines — God Object risk | Split into `configService` + `templateService` |
-| 3 | 🟠 P1 | ARCH-15 | `services/analytics.js` | New analytics module, no ADR | Create ADR for analytics approach |
-
-## Layer Compliance
-| Layer | Files | Violations | Status |
-|-------|:-----:|:----------:|:------:|
-| Routes | 5 | 0 | ✅ |
-| Controllers | 4 | 1 | ⚠️ |
-| Services | 6 | 0 | ✅ |
-| Repos | 3 | 0 | ✅ |
-
-## ADR Compliance
-| ADR | Description | Compliant? |
-|-----|-------------|:----------:|
-| ADR-018 | ImageViewer component | ✅ |
-| ADR-019 | CSS overflow strategy | ✅ |
-| — | New analytics pattern | ❌ ADR needed |
-
-## Verdict
-- ✅ COMPLIANT — architecture fully followed
-- ⚠️ VIOLATIONS — fix P0/P1 before merge
-- ❌ REDESIGN — fundamental architecture mismatch
-```
-
----
-
-## See also
-- `$architecture-doc` — Architecture Document (reference)
-- `$adr-log` — ADR Log (reference)
-- `$code-review-checklist` — general review (architecture section)
-- `$current-state-analysis` — initial repo audit

package/locales/en/.agents/skills/architecture-compliance-review/agents/claude.json

@@ -1,18 +0,0 @@
-{
-  "name": "architecture-compliance-review",
-  "display_name": "Architecture Compliance Review",
-  "description": "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags.",
-  "default_prompt": "Use $architecture-compliance-review when the task matches the \"Architecture Compliance Review\" skill.",
-  "triggers": [
-    "architecture-compliance-review",
-    "architecture compliance review",
-    "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags"
-  ],
-  "capabilities": [
-    "architecture",
-    "compliance",
-    "review"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/architecture-compliance-review/agents/copilot.json

@@ -1,18 +0,0 @@
-{
-  "name": "architecture-compliance-review",
-  "display_name": "Architecture Compliance Review",
-  "description": "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags.",
-  "default_prompt": "Use $architecture-compliance-review when the task matches the \"Architecture Compliance Review\" skill.",
-  "triggers": [
-    "architecture-compliance-review",
-    "architecture compliance review",
-    "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags"
-  ],
-  "capabilities": [
-    "architecture",
-    "compliance",
-    "review"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/architecture-compliance-review/agents/gemini.json

@@ -1,18 +0,0 @@
-{
-  "name": "architecture-compliance-review",
-  "display_name": "Architecture Compliance Review",
-  "description": "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags.",
-  "default_prompt": "Use $architecture-compliance-review when the task matches the \"Architecture Compliance Review\" skill.",
-  "triggers": [
-    "architecture-compliance-review",
-    "architecture compliance review",
-    "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags"
-  ],
-  "capabilities": [
-    "architecture",
-    "compliance",
-    "review"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/architecture-compliance-review/agents/kimi.yaml

@@ -1,14 +0,0 @@
-name: "architecture-compliance-review"
-display_name: "Architecture Compliance Review"
-description: "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags."
-default_prompt: "Use $architecture-compliance-review when the task matches the \"Architecture Compliance Review\" skill."
-triggers:
-  - "architecture-compliance-review"
-  - "architecture compliance review"
-  - "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags"
-capabilities:
-  - "architecture"
-  - "compliance"
-  - "review"
-tools: []
-implicit_invocation: true

package/locales/en/.agents/skills/architecture-compliance-review/agents/openai.yaml

@@ -1,8 +0,0 @@
-interface:
-  display_name: "Architecture Compliance Review"
-  short_description: "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conv…"
-  default_prompt: "Use $architecture-compliance-review when the task matches the \"Architecture Compliance Review\" skill."
-dependencies:
-  tools: []
-policy:
-  allow_implicit_invocation: true

package/locales/en/.agents/skills/architecture-compliance-review/agents/qwen.json

@@ -1,18 +0,0 @@
-{
-  "name": "architecture-compliance-review",
-  "display_name": "Architecture Compliance Review",
-  "description": "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags.",
-  "default_prompt": "Use $architecture-compliance-review when the task matches the \"Architecture Compliance Review\" skill.",
-  "triggers": [
-    "architecture-compliance-review",
-    "architecture compliance review",
-    "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags"
-  ],
-  "capabilities": [
-    "architecture",
-    "compliance",
-    "review"
-  ],
-  "tools": [],
-  "implicit_invocation": true
-}

package/locales/en/.agents/skills/architecture-compliance-review/agents/skill.yaml

@@ -1,22 +0,0 @@
-version: 1
-name: "architecture-compliance-review"
-display_name: "Architecture Compliance Review"
-description: "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags."
-default_prompt: "Use $architecture-compliance-review when the task matches the \"Architecture Compliance Review\" skill."
-triggers:
-  - "architecture-compliance-review"
-  - "architecture compliance review"
-  - "Code compliance review against architecture/ADR — module boundaries, layers, dependencies, conventions, red flags"
-capabilities:
-  - "architecture"
-  - "compliance"
-  - "review"
-tools: []
-invocation:
-  explicit: true
-  implicit: true
-localization:
-  default_locale: "en"
-  available_locales:
-    - "ru"
-    - "en"

package/locales/en/.agents/skills/architecture-doc/SKILL.md

@@ -1,204 +0,0 @@
----
-name: architecture-doc
-description: Architectural document based on PRD+UX — modules, flows, data, integrations, errors, testability, bottlenecks, growth plan, and implementation plan.
----
-
-# Skill: Architecture Document
-
-Create an architectural document based on PRD and UX Spec.
-
-**Sections:**
-1. [General rules](#1-general-rules)
-2. [Document Structure](#2-document-structure)
-3. [Component Diagram](#3-component-diagram)
-4. [Data Flow (Sequence)](#4-data-flow)
-5. [Anti-patterns](#5-anti-patterns)
-6. [Output Template](#6-output)
-
----
-
-## 1. General rules
-
-| Rule | Convention |
-|---------|-----------|
-| **Goal** | Connect "what" (PRD) with "how" (code) |
-| **Audience** | Full Stack, DevOps, Reviewer, PM |
-| **Format** | Markdown with Mermaid diagrams |
-| **Dependencies** | Must reference PRD, UX, ADRs, Contracts |
-| **Scope** | Complete system (frontend, backend, DB, external) |
-| **Update frequency** | Living document; update when architecture changes |
-
----
-
-## 2. Document Structure
-
-### 2.1 System Overview
-- **Vision:** 1-2 sentence summary of the technical solution.
-- **Constraints:** Hard limits (e.g., "Must run in Wix iframe", "PostgreSQL only", "Max 100ms latency").
-- **Key metrics NFRs:** Scale targets (req/sec, # of users), availability (99.9%).
-
-### 2.2 Component Architecture
-- **Web Client (Frontend):** Framework (React), layout, state management (Zustand/RTK), routing.
-- **API Gateway / Backend:** Framework (Express/Go), auth layer, core modules.
-- **Data Layer:** DBMS, caching, object storage.
-- **External Integrations:** Wix API, Email provider, Payment gateway.
-- *(Include Mermaid Component Diagram here)*
-
-### 2.3 Core Modules
-Describe each logical module (e.g., Auth, Billing, Products):
-- **Responsibility:** What it does.
-- **Dependencies:** What it calls.
-- **Data:** Key entities it owns.
-
-### 2.4 Data Architecture
-- **Schema Overview:** Key collections/tables (link to full Data Model).
-- **Storage Strategy:** Where data lives (MongoDB Atlas, local SQLite for dev).
-- **Caching Strategy:** Redis? In-memory? Browser cache?
-
-### 2.5 Key User Flows (Sequence)
-- Describe 2-3 critical paths (e.g., "User Login & Dashboard Load", "Purchase Flow").
-- *(Include Mermaid Sequence Diagram here)*
-
-### 2.6 Cross-Cutting Concerns
-- **Authentication & Authorization:** JWT vs Session, Role-Based Access Control (RBAC).
-- **Error Handling:** Global error format, retry strategies.
-- **Observability:** Logging (Pino), metrics, tracing (trace_id).
-- **Security:** CSRF, XSS, rate limiting, secrets management.
-
-### 2.7 Deployment & Infrastructure
-- **Environments:** Dev, Staging, Prod.
-- **Hosting:** Vercel (FE) + Render (BE) vs Custom K8s cluster.
-- **CI/CD:** GitHub Actions (lint → test → build → deploy).
-
-### 2.8 Risks & Technical Debt
-- **Known bottlenecks:** "Search uses regex, will be slow at 100k records."
-- **Planned tech debt:** "Skipping Redis cache for MVP."
-- **Mitigation:** "Will migrate to Elasticsearch when hitting 50k users."
-
----
-
-## 3. Component Diagram
-
-Use Mermaid for visualizing system boundaries:
-
-```mermaid
-graph TD
-    Client[Web Browser (React)]
-    API[Backend API (Node.js)]
-    DB[(Database (MongoDB))]
-    Ext[External API (Wix)]
-    Cache[(Cache (Redis))]
-
-    Client -- HTTPS --> API
-    API -- Mongoose --> DB
-    API -- REST --> Ext
-    API -- ioredis --> Cache
-```
-
-<br>
-
-*Rules for diagrams:*
-- Keep them simple (max 10-15 nodes).
-- Group related components (subgraphs).
-- Label connections with protocols (HTTPS, REST) or tools (Mongoose).
-
----
-
-## 4. Data Flow (Sequence)
-
-Use Mermaid for critical flows:
-
-```mermaid
-sequenceDiagram
-    participant User
-    participant Client as Frontend (React)
-    participant API as Backend (Express)
-    participant DB as MongoDB
-
-    User->>Client: Clicks "Save Settings"
-    Client->>API: PUT /api/v1/settings (JWT)
-    activate API
-    API->>API: Validate Token & Body (Zod)
-    API->>DB: updateOne(settings)
-    DB-->>API: OK (updated)
-    API-->>Client: 200 OK { data: ... }
-    deactivate API
-    Client-->>User: Show Toast "Saved"
-```
-
-<br>
-
-*Rules for sequence diagrams:*
-- Show happy path + 1 major error path (if critical).
-- clearly show `activate`/`deactivate` blocks.
-- Label arrows with meaningful actions/endpoints.
-
----
-
-## 5. Anti-patterns
-
-| ❌ Anti-pattern | ✅ Solution |
-|----------------|-----------|
-| **Too detailed** | Document high-level architecture, not every function. |
-| **No diagrams** | Text describes, diagrams visualize. Always use Mermaid. |
-| **Ignoring NFRs** | Explicitly mention performance, security, and scale constraints. |
-| **Orphaned document** | Link to PRD, UX Specs, ADRs, and API Contracts. |
-| **"We'll figure it out later"** | If undetermined, explicitly list as "Open Question" or "Risk". |
-
----
-
-## 6. Output Template
-
-```markdown
-# Architecture Document: <Project Name>
-
-**Date:** YYYY-MM-DD
-**Version:** v1.0
-**Status:** Draft | Approved
-
-## 1. System Overview
-<Vision and NFR constraints>
-
-## 2. Component Architecture
-<Mermaid graph>
-- Web Client: ...
-- Backend API: ...
-- Database: ...
-
-## 3. Core Modules
-- Module A: ...
-- Module B: ...
-
-## 4. Key User Flows
-<Mermaid sequence diagram for primary flow>
-
-## 5. Data Architecture
-<High-level schema, storage, caching>
-
-## 6. Cross-Cutting Concerns
-- Auth: ...
-- Observability: ...
-- Error Handling: ...
-
-## 7. Deployment & Infrastructure
-<Hosting, CI/CD pipeline overview>
-
-## 8. Risks & Mitigations
-| Risk | Impact | Mitigation |
-|------|--------|------------|
-| ... | ... | ... |
-
----
-**References:**
-- [PRD](./prd.md)
-- [ADR Index](./adr/README.md)
-- [API Contracts](./api-contracts.md)
-```
-
----
-
-## See also
-- `$current-state-analysis` — before architecture changes
-- `$adr-log` — detailed architectural decisions
-- `$data-model` — complete DB schema
-- `$deployment-ci-plan` — specific execution plan