From e905498db2cd51363ae8266b574b7697daff2a84 Mon Sep 17 00:00:00 2001 From: "google-labs-jules[bot]" <161369871+google-labs-jules[bot]@users.noreply.github.com> Date: Mon, 6 Apr 2026 18:36:45 +0000 Subject: [PATCH] docs(arch): autonomous evolution of architecture blueprints for deterministic Agent parsing Co-authored-by: beginwebdev2002 <102213457+beginwebdev2002@users.noreply.github.com> --- architectures/clean-architecture/data-flow.md | 5 -- .../clean-architecture/folder-structure.md | 5 -- .../clean-architecture/trade-offs.md | 12 ++-- architectures/cqrs/data-flow.md | 12 ++-- architectures/cqrs/folder-structure.md | 12 ++-- architectures/cqrs/readme.md | 1 - architectures/cqrs/trade-offs.md | 12 ++-- .../domain-driven-design/data-flow.md | 12 ++-- .../domain-driven-design/folder-structure.md | 12 ++-- .../implementation-guide.md | 66 +++++++++++++++++-- architectures/domain-driven-design/readme.md | 6 +- .../domain-driven-design/trade-offs.md | 12 ++-- .../event-driven-architecture/data-flow.md | 10 +-- .../folder-structure.md | 10 +-- .../implementation-guide.md | 10 +-- .../event-driven-architecture/readme.md | 10 +-- .../event-driven-architecture/trade-offs.md | 10 +-- .../feature-sliced-design/data-flow.md | 12 ++-- .../feature-sliced-design/folder-structure.md | 12 ++-- .../implementation-guide.md | 12 ++-- architectures/feature-sliced-design/readme.md | 6 +- .../feature-sliced-design/trade-offs.md | 12 ++-- .../hexagonal-architecture/data-flow.md | 6 +- .../folder-structure.md | 6 +- .../hexagonal-architecture/readme.md | 6 +- .../hexagonal-architecture/trade-offs.md | 6 +- architectures/micro-frontends/data-flow.md | 7 +- .../micro-frontends/folder-structure.md | 7 +- .../micro-frontends/implementation-guide.md | 7 +- architectures/micro-frontends/readme.md | 7 +- architectures/micro-frontends/trade-offs.md | 7 +- architectures/microservices/data-flow.md | 12 ++-- .../microservices/folder-structure.md | 12 ++-- .../microservices/implementation-guide.md | 3 +- architectures/microservices/readme.md | 1 - architectures/microservices/trade-offs.md | 12 ++-- .../model-view-controller/data-flow.md | 12 ++-- .../model-view-controller/folder-structure.md | 12 ++-- .../implementation-guide.md | 12 ++-- architectures/model-view-controller/readme.md | 6 +- .../model-view-controller/trade-offs.md | 12 ++-- .../monolithic-architecture/data-flow.md | 12 ++-- .../folder-structure.md | 12 ++-- .../implementation-guide.md | 65 ++++++++++++++++-- .../monolithic-architecture/readme.md | 6 +- .../monolithic-architecture/trade-offs.md | 12 ++-- architectures/readme.md | 17 ++++- architectures/serverless/data-flow.md | 12 ++-- architectures/serverless/folder-structure.md | 12 ++-- .../serverless/implementation-guide.md | 12 ++-- architectures/serverless/trade-offs.md | 12 ++-- 51 files changed, 287 insertions(+), 309 deletions(-) diff --git a/architectures/clean-architecture/data-flow.md b/architectures/clean-architecture/data-flow.md index 03dca27..9cfdbe3 100644 --- a/architectures/clean-architecture/data-flow.md +++ b/architectures/clean-architecture/data-flow.md @@ -6,11 +6,6 @@ version: Latest tags: [architecture, best-practices] ai_role: System Architect last_updated: 2026-03-22 -description: AI agent blueprint constraint -topic: Clean-architecture -complexity: Architect -last_evolution: 2026-03-22 -vibe_coding_ready: true --- --- diff --git a/architectures/clean-architecture/folder-structure.md b/architectures/clean-architecture/folder-structure.md index b54d0b3..a4ceaa2 100644 --- a/architectures/clean-architecture/folder-structure.md +++ b/architectures/clean-architecture/folder-structure.md @@ -6,11 +6,6 @@ version: Latest tags: [architecture, best-practices] ai_role: System Architect last_updated: 2026-03-22 -description: AI agent blueprint constraint -topic: Clean-architecture -complexity: Architect -last_evolution: 2026-03-22 -vibe_coding_ready: true --- --- diff --git a/architectures/clean-architecture/trade-offs.md b/architectures/clean-architecture/trade-offs.md index 9ccc480..bcf1866 100644 --- a/architectures/clean-architecture/trade-offs.md +++ b/architectures/clean-architecture/trade-offs.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Clean Architecture within the Architecture domain. -tags: [clean-architecture, architecture, best-practices, architecture] -topic: Clean Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Clean Architecture domain: Architecture level: Senior/Architect version: Latest +tags: [clean-architecture, architecture, best-practices, architecture] ai_role: Senior Clean Architecture Expert -last_updated: 2026-03-29---# Clean Architecture - Trade-offs +last_updated: 2026-03-29 +--- + +# Clean Architecture - Trade-offs ## Pros, Cons, and System Constraints ### Pros diff --git a/architectures/cqrs/data-flow.md b/architectures/cqrs/data-flow.md index f3a8aa1..7f16c3f 100644 --- a/architectures/cqrs/data-flow.md +++ b/architectures/cqrs/data-flow.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for CQRS within the Architecture domain. -tags: [cqrs, architecture, best-practices, architecture] -topic: CQRS -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: CQRS domain: Architecture level: Senior/Architect version: Latest +tags: [cqrs, architecture, best-practices, architecture] ai_role: Senior CQRS Expert -last_updated: 2026-03-29---# CQRS - Data Flow +last_updated: 2026-03-29 +--- + +# CQRS - Data Flow ## Request and Event Lifecycle ```mermaid diff --git a/architectures/cqrs/folder-structure.md b/architectures/cqrs/folder-structure.md index 85b5732..27fd120 100644 --- a/architectures/cqrs/folder-structure.md +++ b/architectures/cqrs/folder-structure.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for CQRS within the Architecture domain. -tags: [cqrs, architecture, best-practices, architecture] -topic: CQRS -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: CQRS domain: Architecture level: Senior/Architect version: Latest +tags: [cqrs, architecture, best-practices, architecture] ai_role: Senior CQRS Expert -last_updated: 2026-03-29---# CQRS - Folder Structure +last_updated: 2026-03-29 +--- + +# CQRS - Folder Structure ## Layering publisher/subscriber logic ```mermaid diff --git a/architectures/cqrs/readme.md b/architectures/cqrs/readme.md index 6993572..00cf7c5 100644 --- a/architectures/cqrs/readme.md +++ b/architectures/cqrs/readme.md @@ -1,5 +1,4 @@ --- - technology: CQRS (Command Query Responsibility Segregation) domain: Architecture level: Senior/Architect diff --git a/architectures/cqrs/trade-offs.md b/architectures/cqrs/trade-offs.md index 9848449..b0154d6 100644 --- a/architectures/cqrs/trade-offs.md +++ b/architectures/cqrs/trade-offs.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for CQRS within the Architecture domain. -tags: [cqrs, architecture, best-practices, architecture] -topic: CQRS -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: CQRS domain: Architecture level: Senior/Architect version: Latest +tags: [cqrs, architecture, best-practices, architecture] ai_role: Senior CQRS Expert -last_updated: 2026-03-29---# CQRS - Trade-offs +last_updated: 2026-03-29 +--- + +# CQRS - Trade-offs ## Pros, Cons, and System Constraints ### Pros diff --git a/architectures/domain-driven-design/data-flow.md b/architectures/domain-driven-design/data-flow.md index 926d919..ac7a1cb 100644 --- a/architectures/domain-driven-design/data-flow.md +++ b/architectures/domain-driven-design/data-flow.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for DDD within the Architecture domain. -tags: [ddd, architecture, best-practices, architecture] -topic: DDD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: DDD domain: Architecture level: Senior/Architect version: Latest +tags: [ddd, architecture, best-practices, architecture] ai_role: Senior DDD Expert -last_updated: 2026-03-29---# Domain-Driven Design - Data Flow +last_updated: 2026-03-29 +--- + +# Domain-Driven Design - Data Flow ## Request and Event Lifecycle ```mermaid diff --git a/architectures/domain-driven-design/folder-structure.md b/architectures/domain-driven-design/folder-structure.md index 65c0c94..4ae95a5 100644 --- a/architectures/domain-driven-design/folder-structure.md +++ b/architectures/domain-driven-design/folder-structure.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for DDD within the Architecture domain. -tags: [ddd, architecture, best-practices, architecture] -topic: DDD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: DDD domain: Architecture level: Senior/Architect version: Latest +tags: [ddd, architecture, best-practices, architecture] ai_role: Senior DDD Expert -last_updated: 2026-03-29---# Domain-Driven Design - Folder Structure +last_updated: 2026-03-29 +--- + +# Domain-Driven Design - Folder Structure ## Layering logic ```mermaid diff --git a/architectures/domain-driven-design/implementation-guide.md b/architectures/domain-driven-design/implementation-guide.md index a3ced79..23273d6 100644 --- a/architectures/domain-driven-design/implementation-guide.md +++ b/architectures/domain-driven-design/implementation-guide.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for DDD within the Architecture domain. -tags: [ddd, architecture, best-practices, architecture] -topic: DDD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: DDD domain: Architecture level: Senior/Architect version: Latest +tags: [ddd, architecture, best-practices, architecture] ai_role: Senior DDD Expert -last_updated: 2026-03-29---# Domain-Driven Design - Implementation Guide +last_updated: 2026-03-29 +--- + +# Domain-Driven Design - Implementation Guide ## Code patterns and Anti-patterns ### Entity Relationships @@ -29,3 +27,57 @@ classDiagram ### Rules - Ubiquitous language must be strictly used in code. + +### 1. Anemic Domain Model + +### ❌ Bad Practice +```typescript +class Order { + public id: string; + public totalAmount: number; + public items: OrderItem[]; + public status: string; +} + +class OrderService { + public addDiscount(order: Order, discount: number) { + if (order.status === 'PENDING') { + order.totalAmount -= discount; + } + } +} +``` + +### ⚠️ Problem +This is an anemic domain model. The `Order` entity is merely a data holder with public setters, and all the business logic is stripped out and placed in an external `OrderService`. This violates encapsulation, makes the system harder to reason about, and leads to business rules being scattered across multiple services. + +### βœ… Best Practice +```typescript +class Order { + private id: string; + private totalAmount: number; + private items: OrderItem[]; + private status: 'PENDING' | 'PAID' | 'SHIPPED'; + + constructor(id: string, items: OrderItem[]) { + this.id = id; + this.items = items; + this.status = 'PENDING'; + this.calculateTotal(); + } + + public applyDiscount(discount: number): void { + if (this.status !== 'PENDING') { + throw new Error('Cannot apply discount to non-pending order.'); + } + this.totalAmount -= discount; + } + + private calculateTotal(): void { + // calculation logic + } +} +``` + +### πŸš€ Solution +Create rich domain models. Business logic and rules that belong to an entity should be encapsulated within the entity itself. The entity should protect its invariants and expose business-meaningful methods (like `applyDiscount`) instead of public setters. diff --git a/architectures/domain-driven-design/readme.md b/architectures/domain-driven-design/readme.md index 1fae42f..e60a7e9 100644 --- a/architectures/domain-driven-design/readme.md +++ b/architectures/domain-driven-design/readme.md @@ -1,5 +1,4 @@ --- -description: Vibe coding guidelines and architectural constraints for Domain-Driven Design within the Architecture domain. technology: Domain-Driven Design domain: Architecture level: Senior/Architect @@ -7,10 +6,7 @@ version: Agnostic tags: [architecture, system-design, domain-driven-design, best-practices] ai_role: Senior Architect last_updated: 2026-03-22 -topic: DDD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true--- +---
diff --git a/architectures/domain-driven-design/trade-offs.md b/architectures/domain-driven-design/trade-offs.md index ef5ee8b..1f25125 100644 --- a/architectures/domain-driven-design/trade-offs.md +++ b/architectures/domain-driven-design/trade-offs.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for DDD within the Architecture domain. -tags: [ddd, architecture, best-practices, architecture] -topic: DDD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: DDD domain: Architecture level: Senior/Architect version: Latest +tags: [ddd, architecture, best-practices, architecture] ai_role: Senior DDD Expert -last_updated: 2026-03-29---# Domain-Driven Design - Trade-offs +last_updated: 2026-03-29 +--- + +# Domain-Driven Design - Trade-offs ## Pros, Cons, and System Constraints ### Pros diff --git a/architectures/event-driven-architecture/data-flow.md b/architectures/event-driven-architecture/data-flow.md index d15bddb..72a75e3 100644 --- a/architectures/event-driven-architecture/data-flow.md +++ b/architectures/event-driven-architecture/data-flow.md @@ -1,16 +1,12 @@ --- -description: Vibe coding guidelines for the asynchronous request and data flow lifecycle in an Event-Driven Architecture (EDA). technology: Event-Driven Architecture domain: Architecture -complexity: Architect -last_evolution: 2026-03-27 -vibe_coding_ready: true -tags: [eda, data-flow, sequence-diagram, asynchronous, messaging, event-lifecycle] -topic: Event-Driven Data Flow level: Senior/Architect version: Latest +tags: [eda, data-flow, sequence-diagram, asynchronous, messaging, event-lifecycle] ai_role: Senior Event-Driven Architecture Expert -last_updated: 2026-03-29--- +last_updated: 2026-03-29 +---
diff --git a/architectures/event-driven-architecture/folder-structure.md b/architectures/event-driven-architecture/folder-structure.md index 8d66dab..845387e 100644 --- a/architectures/event-driven-architecture/folder-structure.md +++ b/architectures/event-driven-architecture/folder-structure.md @@ -1,16 +1,12 @@ --- -description: Vibe coding guidelines for the folder structure and structural hierarchy of Event-Driven Architecture (EDA) projects. technology: Event-Driven Architecture domain: Architecture -complexity: Architect -last_evolution: 2026-03-27 -vibe_coding_ready: true -tags: [eda, folder-structure, architecture-hierarchy, backend, microservices] -topic: Event-Driven Folder Structure level: Senior/Architect version: Latest +tags: [eda, folder-structure, architecture-hierarchy, backend, microservices] ai_role: Senior Event-Driven Architecture Expert -last_updated: 2026-03-29--- +last_updated: 2026-03-29 +---
diff --git a/architectures/event-driven-architecture/implementation-guide.md b/architectures/event-driven-architecture/implementation-guide.md index 7546d9b..b0944e2 100644 --- a/architectures/event-driven-architecture/implementation-guide.md +++ b/architectures/event-driven-architecture/implementation-guide.md @@ -1,16 +1,12 @@ --- -description: Vibe coding implementation guidelines, strict rules, code patterns, and constraints for implementing Event-Driven Architecture (EDA) using 2026 standards. technology: Event-Driven Architecture domain: Architecture -complexity: Architect -last_evolution: 2026-03-27 -vibe_coding_ready: true -tags: [eda, implementation-guide, kafka, microservices, typescript, nestjs, architecture-patterns] -topic: Event-Driven Implementation Guide level: Senior/Architect version: Latest +tags: [eda, implementation-guide, kafka, microservices, typescript, nestjs, architecture-patterns] ai_role: Senior Event-Driven Architecture Expert -last_updated: 2026-03-29--- +last_updated: 2026-03-29 +---
diff --git a/architectures/event-driven-architecture/readme.md b/architectures/event-driven-architecture/readme.md index 0616dbc..380b6f4 100644 --- a/architectures/event-driven-architecture/readme.md +++ b/architectures/event-driven-architecture/readme.md @@ -1,16 +1,12 @@ --- -description: Vibe coding guidelines and architectural constraints for Event-Driven Architecture (EDA) within the Architecture domain. technology: Event-Driven Architecture domain: Architecture -complexity: Architect -last_evolution: 2026-03-27 -vibe_coding_ready: true -tags: [eda, event-driven, architecture, pub-sub, asynchronous, messaging, kafka, rabbitmq, system-design] -topic: Event-Driven Architecture level: Senior/Architect version: Latest +tags: [eda, event-driven, architecture, pub-sub, asynchronous, messaging, kafka, rabbitmq, system-design] ai_role: Senior Event-Driven Architecture Expert -last_updated: 2026-03-29--- +last_updated: 2026-03-29 +---
diff --git a/architectures/event-driven-architecture/trade-offs.md b/architectures/event-driven-architecture/trade-offs.md index 99fc8c7..24859c4 100644 --- a/architectures/event-driven-architecture/trade-offs.md +++ b/architectures/event-driven-architecture/trade-offs.md @@ -1,16 +1,12 @@ --- -description: Vibe coding guidelines and constraints for the trade-offs, pros, cons, and anti-patterns of Event-Driven Architecture (EDA). technology: Event-Driven Architecture domain: Architecture -complexity: Architect -last_evolution: 2026-03-27 -vibe_coding_ready: true -tags: [eda, trade-offs, architecture, messaging, kafka] -topic: Event-Driven Trade-offs level: Senior/Architect version: Latest +tags: [eda, trade-offs, architecture, messaging, kafka] ai_role: Senior Event-Driven Architecture Expert -last_updated: 2026-03-29--- +last_updated: 2026-03-29 +---
diff --git a/architectures/feature-sliced-design/data-flow.md b/architectures/feature-sliced-design/data-flow.md index fceffcd..79a8f6d 100644 --- a/architectures/feature-sliced-design/data-flow.md +++ b/architectures/feature-sliced-design/data-flow.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for FSD within the Architecture domain. -tags: [fsd, architecture, best-practices, architecture] -topic: FSD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: FSD domain: Architecture level: Senior/Architect version: Latest +tags: [fsd, architecture, best-practices, architecture] ai_role: Senior FSD Expert -last_updated: 2026-03-29---# Feature-Sliced Design (FSD) - Data Flow +last_updated: 2026-03-29 +--- + +# Feature-Sliced Design (FSD) - Data Flow ## Request and Event Lifecycle ```mermaid diff --git a/architectures/feature-sliced-design/folder-structure.md b/architectures/feature-sliced-design/folder-structure.md index 8c27f36..70e47c8 100644 --- a/architectures/feature-sliced-design/folder-structure.md +++ b/architectures/feature-sliced-design/folder-structure.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for FSD within the Architecture domain. -tags: [fsd, architecture, best-practices, architecture] -topic: FSD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: FSD domain: Architecture level: Senior/Architect version: Latest +tags: [fsd, architecture, best-practices, architecture] ai_role: Senior FSD Expert -last_updated: 2026-03-29---# Feature-Sliced Design (FSD) - Folder Structure +last_updated: 2026-03-29 +--- + +# Feature-Sliced Design (FSD) - Folder Structure ## Layering publisher/subscriber logic ```mermaid diff --git a/architectures/feature-sliced-design/implementation-guide.md b/architectures/feature-sliced-design/implementation-guide.md index 7ceeb4e..8b321d0 100644 --- a/architectures/feature-sliced-design/implementation-guide.md +++ b/architectures/feature-sliced-design/implementation-guide.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for FSD within the Architecture domain. -tags: [fsd, architecture, best-practices, architecture] -topic: FSD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: FSD domain: Architecture level: Senior/Architect version: Latest +tags: [fsd, architecture, best-practices, architecture] ai_role: Senior FSD Expert -last_updated: 2026-03-29---# Feature-Sliced Design (FSD) - Implementation Guide +last_updated: 2026-03-29 +--- + +# Feature-Sliced Design (FSD) - Implementation Guide ## Code patterns and Anti-patterns ### Entity Relationships diff --git a/architectures/feature-sliced-design/readme.md b/architectures/feature-sliced-design/readme.md index 2260d37..0c045b9 100644 --- a/architectures/feature-sliced-design/readme.md +++ b/architectures/feature-sliced-design/readme.md @@ -1,5 +1,4 @@ --- -description: Vibe coding guidelines and architectural constraints for Feature-Sliced Design within the Architecture domain. technology: Feature-Sliced Design domain: Architecture level: Senior/Architect @@ -7,10 +6,7 @@ version: Agnostic tags: [fsd, modular-architecture, frontend, system-design, clean-architecture] ai_role: Senior Frontend Architect last_updated: 2026-03-22 -topic: FSD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true--- +---
diff --git a/architectures/feature-sliced-design/trade-offs.md b/architectures/feature-sliced-design/trade-offs.md index 171c268..7436641 100644 --- a/architectures/feature-sliced-design/trade-offs.md +++ b/architectures/feature-sliced-design/trade-offs.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for FSD within the Architecture domain. -tags: [fsd, architecture, best-practices, architecture] -topic: FSD -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: FSD domain: Architecture level: Senior/Architect version: Latest +tags: [fsd, architecture, best-practices, architecture] ai_role: Senior FSD Expert -last_updated: 2026-03-29---# Feature-Sliced Design (FSD) - Trade-offs +last_updated: 2026-03-29 +--- + +# Feature-Sliced Design (FSD) - Trade-offs ## Pros, Cons, and System Constraints ### Pros diff --git a/architectures/hexagonal-architecture/data-flow.md b/architectures/hexagonal-architecture/data-flow.md index 326d370..be0ed9f 100644 --- a/architectures/hexagonal-architecture/data-flow.md +++ b/architectures/hexagonal-architecture/data-flow.md @@ -1,5 +1,4 @@ --- -description: Hexagonal Architecture Data Flow rules for AI agents and developers. Understanding execution sequences across Ports and Adapters. technology: Hexagonal Architecture domain: Architecture level: Senior/Architect @@ -7,10 +6,7 @@ version: Agnostic tags: [best-practices, data-flow, hexagonal-architecture, ports-and-adapters] ai_role: Senior Software Architect last_updated: 2026-03-22 -topic: Hexagonal Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true--- +--- # πŸ”„ Hexagonal Architecture Data Flow Best Practices diff --git a/architectures/hexagonal-architecture/folder-structure.md b/architectures/hexagonal-architecture/folder-structure.md index 979311e..30f2dde 100644 --- a/architectures/hexagonal-architecture/folder-structure.md +++ b/architectures/hexagonal-architecture/folder-structure.md @@ -1,5 +1,4 @@ --- -description: Hexagonal Architecture Folder Structure rules. Defining the exact directory blueprints for Ports and Adapters. technology: Hexagonal Architecture domain: Architecture level: Senior/Architect @@ -7,10 +6,7 @@ version: Agnostic tags: [best-practices, folder-structure, hexagonal-architecture, ports-and-adapters] ai_role: Senior Software Architect last_updated: 2026-03-22 -topic: Hexagonal Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true--- +--- # πŸ“ Folder Structure Best Practices for Hexagonal Architecture diff --git a/architectures/hexagonal-architecture/readme.md b/architectures/hexagonal-architecture/readme.md index f957afa..45572ea 100644 --- a/architectures/hexagonal-architecture/readme.md +++ b/architectures/hexagonal-architecture/readme.md @@ -1,5 +1,4 @@ --- -description: Hexagonal Architecture (Ports & Adapters) production-ready guidelines and modular breakdown for modern systems. technology: Hexagonal Architecture domain: Architecture level: Senior/Architect @@ -7,10 +6,7 @@ version: Agnostic tags: [best-practices, clean-code, hexagonal-architecture, ports-and-adapters, system-design, vibe-coding] ai_role: Senior Software Architect last_updated: 2026-03-22 -topic: Hexagonal Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true--- +--- # πŸ›‘ Hexagonal Architecture Production-Ready Best Practices # Context & Scope diff --git a/architectures/hexagonal-architecture/trade-offs.md b/architectures/hexagonal-architecture/trade-offs.md index 8b8c8af..8d4ee09 100644 --- a/architectures/hexagonal-architecture/trade-offs.md +++ b/architectures/hexagonal-architecture/trade-offs.md @@ -1,5 +1,4 @@ --- -description: Hexagonal Architecture Trade-offs, Pros, Cons, and Architectural constraints for modern software design. technology: Hexagonal Architecture domain: Architecture level: Senior/Architect @@ -7,10 +6,7 @@ version: Agnostic tags: [best-practices, trade-offs, hexagonal-architecture, ports-and-adapters] ai_role: Senior Software Architect last_updated: 2026-03-22 -topic: Hexagonal Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true--- +--- # βš–οΈ Hexagonal Architecture Trade-offs and Constraints diff --git a/architectures/micro-frontends/data-flow.md b/architectures/micro-frontends/data-flow.md index ae50d0d..8d5e21d 100644 --- a/architectures/micro-frontends/data-flow.md +++ b/architectures/micro-frontends/data-flow.md @@ -1,14 +1,9 @@ --- -description: Vibe coding guidelines and architectural constraints for Micro-frontends Data Flow within the Architecture domain. -tags: [micro-frontends, architecture, module-federation, frontend, data-flow, sequence-diagram, vibe-coding] -topic: Micro-frontends Data Flow -complexity: Architect -last_evolution: 2026-03-22 -vibe_coding_ready: true technology: Micro-frontends domain: Architecture level: Senior/Architect version: Agnostic +tags: [micro-frontends, architecture, module-federation, frontend, data-flow, sequence-diagram, vibe-coding] ai_role: Senior Architect last_updated: 2026-03-22 --- diff --git a/architectures/micro-frontends/folder-structure.md b/architectures/micro-frontends/folder-structure.md index 6b6f8ed..b4b9590 100644 --- a/architectures/micro-frontends/folder-structure.md +++ b/architectures/micro-frontends/folder-structure.md @@ -1,14 +1,9 @@ --- -description: Vibe coding guidelines and architectural constraints for Micro-frontends Folder Structure within the Architecture domain. -tags: [micro-frontends, architecture, module-federation, frontend, folder-structure, vibe-coding] -topic: Micro-frontends Folder Structure -complexity: Architect -last_evolution: 2026-03-22 -vibe_coding_ready: true technology: Micro-frontends domain: Architecture level: Senior/Architect version: Agnostic +tags: [micro-frontends, architecture, module-federation, frontend, folder-structure, vibe-coding] ai_role: Senior Architect last_updated: 2026-03-22 --- diff --git a/architectures/micro-frontends/implementation-guide.md b/architectures/micro-frontends/implementation-guide.md index 48732c7..af1db7e 100644 --- a/architectures/micro-frontends/implementation-guide.md +++ b/architectures/micro-frontends/implementation-guide.md @@ -1,14 +1,9 @@ --- -description: Vibe coding guidelines and architectural constraints for Micro-frontends Implementation Guide within the Architecture domain. -tags: [micro-frontends, architecture, module-federation, frontend, implementation, guide, vibe-coding] -topic: Micro-frontends Implementation Guide -complexity: Architect -last_evolution: 2026-03-22 -vibe_coding_ready: true technology: Micro-frontends domain: Architecture level: Senior/Architect version: Agnostic +tags: [micro-frontends, architecture, module-federation, frontend, implementation, guide, vibe-coding] ai_role: Senior Architect last_updated: 2026-03-22 --- diff --git a/architectures/micro-frontends/readme.md b/architectures/micro-frontends/readme.md index e1b0878..d45c97c 100644 --- a/architectures/micro-frontends/readme.md +++ b/architectures/micro-frontends/readme.md @@ -1,14 +1,9 @@ --- -description: Vibe coding guidelines and architectural constraints for Micro-frontends within the Architecture domain. -tags: [micro-frontends, architecture, module-federation, frontend, scalable, web-components, vibe-coding] -topic: Micro-frontends -complexity: Architect -last_evolution: 2026-03-22 -vibe_coding_ready: true technology: Micro-frontends domain: Architecture level: Senior/Architect version: Agnostic +tags: [micro-frontends, architecture, module-federation, frontend, scalable, web-components, vibe-coding] ai_role: Senior Architect last_updated: 2026-03-22 --- diff --git a/architectures/micro-frontends/trade-offs.md b/architectures/micro-frontends/trade-offs.md index ff24db8..72787f2 100644 --- a/architectures/micro-frontends/trade-offs.md +++ b/architectures/micro-frontends/trade-offs.md @@ -1,14 +1,9 @@ --- -description: Vibe coding guidelines and architectural constraints for Micro-frontends Trade-offs within the Architecture domain. -tags: [micro-frontends, architecture, module-federation, frontend, trade-offs, constraints, vibe-coding] -topic: Micro-frontends Trade-offs -complexity: Architect -last_evolution: 2026-03-22 -vibe_coding_ready: true technology: Micro-frontends domain: Architecture level: Senior/Architect version: Agnostic +tags: [micro-frontends, architecture, module-federation, frontend, trade-offs, constraints, vibe-coding] ai_role: Senior Architect last_updated: 2026-03-22 --- diff --git a/architectures/microservices/data-flow.md b/architectures/microservices/data-flow.md index 42f0f1d..5a3c79e 100644 --- a/architectures/microservices/data-flow.md +++ b/architectures/microservices/data-flow.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Vibe Coding within the Architecture domain. -tags: [vibe-coding, architecture, best-practices, architecture] -topic: Vibe Coding -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Vibe Coding domain: Architecture level: Senior/Architect version: Latest +tags: [vibe-coding, architecture, best-practices, architecture] ai_role: Senior Vibe Coding Expert -last_updated: 2026-03-29---# Microservices - Data Flow +last_updated: 2026-03-29 +--- + +# Microservices - Data Flow ## Request and Event Lifecycle ```mermaid diff --git a/architectures/microservices/folder-structure.md b/architectures/microservices/folder-structure.md index d5e8ae1..be5da0e 100644 --- a/architectures/microservices/folder-structure.md +++ b/architectures/microservices/folder-structure.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Vibe Coding within the Architecture domain. -tags: [vibe-coding, architecture, best-practices, architecture] -topic: Vibe Coding -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Vibe Coding domain: Architecture level: Senior/Architect version: Latest +tags: [vibe-coding, architecture, best-practices, architecture] ai_role: Senior Vibe Coding Expert -last_updated: 2026-03-29---# Microservices - Folder Structure +last_updated: 2026-03-29 +--- + +# Microservices - Folder Structure ## Layering logic ```mermaid diff --git a/architectures/microservices/implementation-guide.md b/architectures/microservices/implementation-guide.md index d7bf6ff..2c6c998 100644 --- a/architectures/microservices/implementation-guide.md +++ b/architectures/microservices/implementation-guide.md @@ -1,10 +1,9 @@ --- - -tags: [architecture, implementation, microservices, best-practices] technology: Microservices domain: Architecture level: Senior/Architect version: Agnostic +tags: [architecture, implementation, microservices, best-practices] ai_role: Senior Architect last_updated: 2026-03-29 --- diff --git a/architectures/microservices/readme.md b/architectures/microservices/readme.md index 29cce33..4ba8c4a 100644 --- a/architectures/microservices/readme.md +++ b/architectures/microservices/readme.md @@ -1,5 +1,4 @@ --- - technology: Microservices domain: Architecture level: Senior/Architect diff --git a/architectures/microservices/trade-offs.md b/architectures/microservices/trade-offs.md index 717478c..920956e 100644 --- a/architectures/microservices/trade-offs.md +++ b/architectures/microservices/trade-offs.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Vibe Coding within the Architecture domain. -tags: [vibe-coding, architecture, best-practices, architecture] -topic: Vibe Coding -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Vibe Coding domain: Architecture level: Senior/Architect version: Latest +tags: [vibe-coding, architecture, best-practices, architecture] ai_role: Senior Vibe Coding Expert -last_updated: 2026-03-29---# Microservices - Trade-offs +last_updated: 2026-03-29 +--- + +# Microservices - Trade-offs ## Pros, Cons, and System Constraints ### Pros diff --git a/architectures/model-view-controller/data-flow.md b/architectures/model-view-controller/data-flow.md index 51e97d5..2d1b913 100644 --- a/architectures/model-view-controller/data-flow.md +++ b/architectures/model-view-controller/data-flow.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for MVC within the Architecture domain. -tags: [mvc, architecture, best-practices, architecture] -topic: MVC -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: MVC domain: Architecture level: Senior/Architect version: Latest +tags: [mvc, architecture, best-practices, architecture] ai_role: Senior MVC Expert -last_updated: 2026-03-29---# Model-View-Controller (MVC) - Data Flow +last_updated: 2026-03-29 +--- + +# Model-View-Controller (MVC) - Data Flow ## Request and Event Lifecycle ```mermaid diff --git a/architectures/model-view-controller/folder-structure.md b/architectures/model-view-controller/folder-structure.md index 1527c10..396a83e 100644 --- a/architectures/model-view-controller/folder-structure.md +++ b/architectures/model-view-controller/folder-structure.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for MVC within the Architecture domain. -tags: [mvc, architecture, best-practices, architecture] -topic: MVC -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: MVC domain: Architecture level: Senior/Architect version: Latest +tags: [mvc, architecture, best-practices, architecture] ai_role: Senior MVC Expert -last_updated: 2026-03-29---# Model-View-Controller (MVC) - Folder Structure +last_updated: 2026-03-29 +--- + +# Model-View-Controller (MVC) - Folder Structure ## Layering publisher/subscriber logic ```mermaid diff --git a/architectures/model-view-controller/implementation-guide.md b/architectures/model-view-controller/implementation-guide.md index be16ea8..9d40d3b 100644 --- a/architectures/model-view-controller/implementation-guide.md +++ b/architectures/model-view-controller/implementation-guide.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for MVC within the Architecture domain. -tags: [mvc, architecture, best-practices, architecture] -topic: MVC -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: MVC domain: Architecture level: Senior/Architect version: Latest +tags: [mvc, architecture, best-practices, architecture] ai_role: Senior MVC Expert -last_updated: 2026-03-29---# Model-View-Controller (MVC) - Implementation Guide +last_updated: 2026-03-29 +--- + +# Model-View-Controller (MVC) - Implementation Guide ## Code patterns and Anti-patterns ### Entity Relationships diff --git a/architectures/model-view-controller/readme.md b/architectures/model-view-controller/readme.md index 118469e..379773b 100644 --- a/architectures/model-view-controller/readme.md +++ b/architectures/model-view-controller/readme.md @@ -1,5 +1,4 @@ --- -description: Vibe coding guidelines and architectural constraints for Model-View-Controller (MVC) within the Architecture domain. technology: Model-View-Controller (MVC) domain: Architecture level: Senior/Architect @@ -7,10 +6,7 @@ version: Agnostic tags: [best-practices, clean-code, architecture-patterns, vibe-coding, cursor-rules, typescript, software-architecture, system-design, solid-principles, production-ready, programming-standards, react-best-practices, node-js, design-patterns, scalable-code, windsurf-rules, ai-coding, fsd, ddd, enterprise-patterns, mvc-best-practise, angular-best-practise, expressjs-best-practise, ai-instructions, vibe-coding-instructions, mongodb, angular, nestjs, html, scss, javascript, js, typescript-best-practise, css, css3] ai_role: Senior Software Architect last_updated: 2026-03-22 -topic: MVC -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true--- +---
diff --git a/architectures/model-view-controller/trade-offs.md b/architectures/model-view-controller/trade-offs.md index 62e083d..6fc3dc2 100644 --- a/architectures/model-view-controller/trade-offs.md +++ b/architectures/model-view-controller/trade-offs.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for MVC within the Architecture domain. -tags: [mvc, architecture, best-practices, architecture] -topic: MVC -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: MVC domain: Architecture level: Senior/Architect version: Latest +tags: [mvc, architecture, best-practices, architecture] ai_role: Senior MVC Expert -last_updated: 2026-03-29---# Model-View-Controller (MVC) - Trade-offs +last_updated: 2026-03-29 +--- + +# Model-View-Controller (MVC) - Trade-offs ## Pros, Cons, and System Constraints ### Pros diff --git a/architectures/monolithic-architecture/data-flow.md b/architectures/monolithic-architecture/data-flow.md index 8cb74eb..0eff28b 100644 --- a/architectures/monolithic-architecture/data-flow.md +++ b/architectures/monolithic-architecture/data-flow.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Monolithic Architecture within the Architecture domain. -tags: [monolithic-architecture, architecture, best-practices, architecture] -topic: Monolithic Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Monolithic Architecture domain: Architecture level: Senior/Architect version: Latest +tags: [monolithic-architecture, architecture, best-practices, architecture] ai_role: Senior Monolithic Architecture Expert -last_updated: 2026-03-29---# Monolithic Architecture - Data Flow +last_updated: 2026-03-29 +--- + +# Monolithic Architecture - Data Flow ## Request and Event Lifecycle ```mermaid diff --git a/architectures/monolithic-architecture/folder-structure.md b/architectures/monolithic-architecture/folder-structure.md index 9cd71a2..a498a23 100644 --- a/architectures/monolithic-architecture/folder-structure.md +++ b/architectures/monolithic-architecture/folder-structure.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Monolithic Architecture within the Architecture domain. -tags: [monolithic-architecture, architecture, best-practices, architecture] -topic: Monolithic Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Monolithic Architecture domain: Architecture level: Senior/Architect version: Latest +tags: [monolithic-architecture, architecture, best-practices, architecture] ai_role: Senior Monolithic Architecture Expert -last_updated: 2026-03-29---# Monolithic Architecture - Folder Structure +last_updated: 2026-03-29 +--- + +# Monolithic Architecture - Folder Structure ## Layering logic ```mermaid diff --git a/architectures/monolithic-architecture/implementation-guide.md b/architectures/monolithic-architecture/implementation-guide.md index cc16076..1226561 100644 --- a/architectures/monolithic-architecture/implementation-guide.md +++ b/architectures/monolithic-architecture/implementation-guide.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Monolithic Architecture within the Architecture domain. -tags: [monolithic-architecture, architecture, best-practices, architecture] -topic: Monolithic Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Monolithic Architecture domain: Architecture level: Senior/Architect version: Latest +tags: [monolithic-architecture, architecture, best-practices, architecture] ai_role: Senior Monolithic Architecture Expert -last_updated: 2026-03-29---# Monolithic Architecture - Implementation Guide +last_updated: 2026-03-29 +--- + +# Monolithic Architecture - Implementation Guide ## Code patterns and Anti-patterns ### Entity Relationships @@ -28,3 +26,56 @@ classDiagram ### Rules - Adopt Modular Monolith principles over time. + +### 1. Tight Coupling via Global State + +### ❌ Bad Practice +```typescript +// Global state shared across the entire monolith +const globalAppCache = new Map(); + +class UserService { + getUser(id: string) { + if (globalAppCache.has(`user_${id}`)) { + return globalAppCache.get(`user_${id}`); + } + // Fetch from DB... + } +} + +class OrderService { + processOrder(order: any) { + // Arbitrarily mutating global state used by other domains + globalAppCache.set(`user_${order.userId}`, { lastOrder: Date.now() }); + } +} +``` + +### ⚠️ Problem +Using a shared global state or tightly coupling modules without clear boundaries in a monolith creates a "Big Ball of Mud". Changes in one domain (like `OrderService` mutating a cache) unexpectedly break another domain (`UserService`). This makes scaling, testing, and eventual extraction into microservices nearly impossible. + +### βœ… Best Practice +```typescript +// Define explicit interfaces and isolated storage per module +class UserService { + constructor(private readonly userCache: UserCache) {} + + getUser(id: string) { + // Uses isolated cache + } +} + +class OrderService { + constructor(private readonly eventBus: EventBus) {} + + processOrder(order: any) { + // Process order... + + // Emit an event instead of mutating other domains' state + this.eventBus.publish('OrderProcessed', { userId: order.userId, timestamp: Date.now() }); + } +} +``` + +### πŸš€ Solution +Build a "Modular Monolith". Even though the code runs in a single process, strictly isolate the data and state of different business domains. Modules should communicate with each other through explicit interfaces or an in-memory event bus, rather than sharing global variables or databases. diff --git a/architectures/monolithic-architecture/readme.md b/architectures/monolithic-architecture/readme.md index 4875e23..00db8c5 100644 --- a/architectures/monolithic-architecture/readme.md +++ b/architectures/monolithic-architecture/readme.md @@ -1,5 +1,4 @@ --- -description: Vibe coding guidelines and architectural constraints for Monolithic Architecture within the Architecture domain. technology: Monolithic Architecture domain: Architecture level: Senior/Architect @@ -7,10 +6,7 @@ version: Agnostic tags: [architecture, system-design, monolithic-architecture, best-practices] ai_role: Senior Architect last_updated: 2026-03-22 -topic: Monolithic Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true--- +---
diff --git a/architectures/monolithic-architecture/trade-offs.md b/architectures/monolithic-architecture/trade-offs.md index 160f31f..54fe095 100644 --- a/architectures/monolithic-architecture/trade-offs.md +++ b/architectures/monolithic-architecture/trade-offs.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Monolithic Architecture within the Architecture domain. -tags: [monolithic-architecture, architecture, best-practices, architecture] -topic: Monolithic Architecture -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Monolithic Architecture domain: Architecture level: Senior/Architect version: Latest +tags: [monolithic-architecture, architecture, best-practices, architecture] ai_role: Senior Monolithic Architecture Expert -last_updated: 2026-03-29---# Monolithic Architecture - Trade-offs +last_updated: 2026-03-29 +--- + +# Monolithic Architecture - Trade-offs ## Pros, Cons, and System Constraints ### Pros diff --git a/architectures/readme.md b/architectures/readme.md index 6ab63ad..d3f2bba 100644 --- a/architectures/readme.md +++ b/architectures/readme.md @@ -1,5 +1,4 @@ --- - technology: General Architecture domain: Architecture level: Senior/Architect @@ -7,6 +6,7 @@ version: Agnostic tags: [best-practices, clean-code, architecture-patterns, vibe-coding, cursor-rules, typescript, software-architecture, system-design, solid-principles, production-ready, programming-standards, react-best-practices, node-js, design-patterns, scalable-code, windsurf-rules, ai-coding, fsd, ddd, enterprise-patterns] ai_role: Senior Software Architect last_updated: 2026-03-29 +--- # Architecture Best Practices & Production-Ready Patterns # Context & Scope @@ -37,6 +37,21 @@ Don't know where to start? Here are a few golden rules: - **Match Your Team's Expertise:** Choose the approach that your team understands or is ready to learn. If everyone knows React inside out, use *FSD*. Lone wolves ruin team productivity. - **Embrace Change:** The perfect architecture allows you to painlessly swap your database (e.g., PostgreSQL for MongoDB) or your UI component library without rewriting the core. --- +## πŸ—ΊοΈ Map of Patterns + +- [Backend-For-Frontend (BFF)](./backend-for-frontend/readme.md) +- [Clean Architecture](./clean-architecture/readme.md) +- [CQRS](./cqrs/readme.md) +- [Domain-Driven Design (DDD)](./domain-driven-design/readme.md) +- [Event-Driven Architecture (EDA)](./event-driven-architecture/readme.md) +- [Feature-Sliced Design (FSD)](./feature-sliced-design/readme.md) +- [Hexagonal Architecture](./hexagonal-architecture/readme.md) +- [Micro-frontends](./micro-frontends/readme.md) +- [Microservices](./microservices/readme.md) +- [MVC (Model-View-Controller)](./model-view-controller/readme.md) +- [Monolithic Architecture](./monolithic-architecture/readme.md) +- [Serverless](./serverless/readme.md) + ## πŸ† Top 10 Best Architectural Approaches Below are the most popular architectural patterns along with examples, tips, technology stacks, and their logos. A Folder Tree is provided for each to give you a deep understanding of its structure. diff --git a/architectures/serverless/data-flow.md b/architectures/serverless/data-flow.md index 244dc22..848b55b 100644 --- a/architectures/serverless/data-flow.md +++ b/architectures/serverless/data-flow.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Serverless within the Architecture domain. -tags: [serverless, architecture, best-practices, architecture] -topic: Serverless -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Serverless domain: Architecture level: Senior/Architect version: Latest +tags: [serverless, architecture, best-practices, architecture] ai_role: Senior Serverless Expert -last_updated: 2026-03-29---# Serverless - Data Flow +last_updated: 2026-03-29 +--- + +# Serverless - Data Flow ## Request and Event Lifecycle ```mermaid diff --git a/architectures/serverless/folder-structure.md b/architectures/serverless/folder-structure.md index ec72b7e..5f2c1f1 100644 --- a/architectures/serverless/folder-structure.md +++ b/architectures/serverless/folder-structure.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Serverless within the Architecture domain. -tags: [serverless, architecture, best-practices, architecture] -topic: Serverless -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Serverless domain: Architecture level: Senior/Architect version: Latest +tags: [serverless, architecture, best-practices, architecture] ai_role: Senior Serverless Expert -last_updated: 2026-03-29---# Serverless - Folder Structure +last_updated: 2026-03-29 +--- + +# Serverless - Folder Structure ## Layering logic ```mermaid diff --git a/architectures/serverless/implementation-guide.md b/architectures/serverless/implementation-guide.md index 73678be..05c48fa 100644 --- a/architectures/serverless/implementation-guide.md +++ b/architectures/serverless/implementation-guide.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Serverless within the Architecture domain. -tags: [serverless, architecture, best-practices, architecture] -topic: Serverless -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Serverless domain: Architecture level: Senior/Architect version: Latest +tags: [serverless, architecture, best-practices, architecture] ai_role: Senior Serverless Expert -last_updated: 2026-03-29---# Serverless - Implementation Guide +last_updated: 2026-03-29 +--- + +# Serverless - Implementation Guide ## Code patterns and Anti-patterns ### Entity Relationships diff --git a/architectures/serverless/trade-offs.md b/architectures/serverless/trade-offs.md index 83c79ad..df01c09 100644 --- a/architectures/serverless/trade-offs.md +++ b/architectures/serverless/trade-offs.md @@ -1,16 +1,14 @@ --- -description: Vibe coding guidelines and architectural constraints for Serverless within the Architecture domain. -tags: [serverless, architecture, best-practices, architecture] -topic: Serverless -complexity: Architect -last_evolution: 2026-03-29 -vibe_coding_ready: true technology: Serverless domain: Architecture level: Senior/Architect version: Latest +tags: [serverless, architecture, best-practices, architecture] ai_role: Senior Serverless Expert -last_updated: 2026-03-29---# Serverless - Trade-offs +last_updated: 2026-03-29 +--- + +# Serverless - Trade-offs ## Pros, Cons, and System Constraints ### Pros