Validate Architecture Command

Perform a comprehensive architecture validation of a StyleMate microservice to ensure it follows all platform standards.

Usage

/validate-architecture [service-name]

If no service name provided, you'll be prompted to select from available services.

What Gets Validated

.NET API Validation

• Clean Architecture Structure

  • Domain/ exists with entities and interfaces
  • Application/ with DTOs and services
  • Infrastructure/ with repositories and DbContext
  • Controllers/ for API endpoints
  • No circular dependencies

• JWT Authentication

  • JWT validation configured in Program.cs
  • Authorization policies defined
  • All controllers have [Authorize] attribute
  • Business isolation via businessId claim

• Database Configuration

  • EF Core DbContext properly configured
  • Migrations directory exists
  • Connection string in appsettings.json
  • Business scoping on all queries

• Docker Setup

  • Multi-stage Dockerfile exists
  • Health check configured
  • Proper port exposure
  • Environment variables defined

• API Standards

  • Async/await on all I/O operations
  • DTOs used instead of entities
  • Proper error handling middleware
  • Swagger with JWT security scheme
  • Health endpoint at /health

React UI Validation

• Module Federation

  • federation.config.ts properly configured
  • Routes exposed at './routes'
  • Shared dependencies with singleton
  • Unique module name

• Component Structure

  • Atomic design folders (atoms, molecules, organisms, pages)
  • TypeScript strict mode enabled
  • No direct DOM manipulation
  • Proper React hooks usage

• JWT Integration

  • Axios interceptors for token injection
  • Token refresh logic implemented
  • Route guards based on roles
  • Business context from JWT

• Responsive Design

  • MUI Grid system used
  • Mobile breakpoints configured
  • Touch-friendly targets (44px min)
  • Theme inheritance from shell

• Build Configuration

  • Vite config with proxy settings
  • Production build optimization
  • Environment variables handled
  • Lint configuration present

• Docker Setup

  • Multi-stage build (Node → Nginx)
  • Static files served via nginx
  • Health check on /remoteEntry.js
  • Proper nginx.conf

Infrastructure Validation

• Nginx Configuration

  • Location blocks for UI remote
  • Location blocks for API endpoints
  • Security headers configured
  • Proxy settings correct

• Docker Compose

  • Service definitions for API and UI
  • Network configuration (stylemate_net)
  • Environment variables passed
  • Health checks defined
  • Port mappings correct

• Integration

  • Shell consumes the remote
  • Routes registered in shell router
  • Navigation menu items added
  • Deep linking works

Output Report

Example Report

=== Architecture Validation Report ===
Service: scheduling
Date: 2025-01-19

✓ .NET API - Clean Architecture
  ✓ Domain layer structure correct
  ✓ No circular dependencies
  ✓ Entities use proper encapsulation
  ⚠ Warning: Some DTOs missing validation attributes

✓ .NET API - JWT Authentication
  ✓ JWT validation configured
  ✓ Authorization policies defined
  ✗ FAIL: StaffController missing [Authorize] attribute

✓ .NET API - Database
  ✓ DbContext configured correctly
  ✓ Migrations present
  ⚠ Warning: Missing index on ScheduleDate column

✓ React UI - Module Federation
  ✓ federation.config.ts correct
  ✓ Routes properly exposed
  ✗ FAIL: Missing singleton on react-router-dom

✓ React UI - Components
  ✓ Atomic design structure
  ✓ TypeScript strict mode
  ⚠ Warning: 3 components missing React.memo

✓ Infrastructure
  ✓ Nginx configuration correct
  ✓ Docker Compose definitions
  ✗ FAIL: Missing health check in API Dockerfile

=== Summary ===
Total Checks: 42
Passed: 35
Warnings: 4
Failed: 3

Critical Issues:
1. StaffController missing authorization - SECURITY RISK
2. Missing singleton on react-router-dom - RUNTIME ERROR
3. Missing API health check - MONITORING GAP

Recommended Actions:
1. Add [Authorize] to StaffController line 15
2. Update federation.config.ts: react-router-dom singleton: true
3. Add HEALTHCHECK to scheduling-api/Dockerfile

Auto-Fix Option

After validation, optionally run:

/validate-architecture scheduling --fix

This will:

• Apply automatic fixes for common issues
• Generate corrected configuration files
• Update missing attributes
• Add missing health checks

Best Practices Enforced

• Clean Architecture layer separation
• Async/await on all I/O
• JWT on all protected endpoints
• Business data isolation
• Module Federation best practices
• Responsive mobile-first design
• Docker health checks
• Security headers

Use this command regularly to maintain architectural integrity across your microservices.