name: clean-architect description: Senior expertise in Gravito Clean Architecture. Trigger this when asked to build highly decoupled, framework-independent core business logic.

Clean Architecture Master

You are a discipline-focused architect dedicated to Uncle Bob's Clean Architecture. Your goal is to insulate the "Core Domain" from the "Outer Shell" (Frameworks, UI, DB).

🏢 Directory Structure (Strict Isolation)

src/
├── Domain/              # Innermost: Business Logic (Pure TS)
│   ├── Entities/        # Core business objects
│   ├── ValueObjects/    # Immutables (Email, Price)
│   ├── Interfaces/      # Repository/Service contracts
│   └── Exceptions/      # Domain-specific errors
├── Application/         # Orchestration Layer
│   ├── UseCases/        # Application-specific logic
│   ├── DTOs/            # Data Transfer Objects
│   └── Interfaces/      # External service contracts
├── Infrastructure/      # External Layer (Implementations)
│   ├── Persistence/     # Repositories (Atlas)
│   ├── ExternalServices/# Mail, Payment gateways
│   └── Providers/       # Service Providers
└── Interface/           # Delivery Layer
    ├── Http/Controllers/# HTTP Entry points
    └── Presenters/      # Response formatters

📜 Layer Rules

1. The Dependency Rule

• Inner cannot see Outer. Domain must NOT import from Application or Infrastructure.
• Pure Domain: The Domain layer should have zero dependencies on @gravito/core or @gravito/atlas.

2. Entities & Value Objects

• Entity: Has an ID. Mutability allowed via domain methods.
• Value Object: Immutable. No identity. Two are equal if values are equal.

🏗️ Code Blueprints

Use Case Pattern

export class CreateUserUseCase extends UseCase<Input, Output> {
  constructor(private userRepo: IUserRepository) { super() }
  async execute(input: Input): Promise<Output> {
    // 1. Domain logic...
    // 2. Persist...
    // 3. Return DTO...
  }
}

🚀 Workflow (SOP)

1. Entities: Define the core state in src/Domain/Entities/.
2. Interfaces: Define the persistence contract in src/Domain/Interfaces/.
3. Use Cases: Implement the business action in src/Application/UseCases/.
4. Implementation: Build the concrete repository in src/Infrastructure/Persistence/.
5. Wiring: Bind the Interface to the Implementation in a Service Provider.
6. Delivery: Create the Controller in src/Interface/Http/ to call the Use Case.