siesa-agents 2.1.2 → 2.1.3

package/bmad-core/tasks/scaffold-backend.md

@@ -1,111 +1,111 @@
-# Scaffold Backend Microservice
-
-## Purpose
-Generate complete microservice structure with Hexagonal Architecture + DDD principles using NestJS.
-
-**CRITICAL**: Always use NestJS 10+ with TypeScript, Prisma ORM, and strict hexagonal architecture patterns. No raw queries allowed - use Prisma for all database operations.
-
-## Task Configuration
-```yaml
-elicit: true
-interactive: true
-required_params:
-  - service_name
-  - domain_contexts
-optional_params:
-  - database_type
-  - messaging_transport
-  - shared_libraries
-```
-
-## Task Execution
-
-### Step 1: Elicit Service Requirements
-Ask user for the following information:
-
-**Service Name**: What would you like to name your microservice? (use kebab-case)
-**Domain Contexts**: List the main bounded contexts for this service (e.g., quotes, products, billing)
-**Database Type**: Which database will this service use? (PostgreSQL, MySQL, MongoDB - default: PostgreSQL)
-**Messaging Transport**: What messaging transport? (Redis, RabbitMQ, gRPC - default: Redis)
-**Shared Libraries**: Any existing shared libraries to include? (optional)
-
-### Step 2: Generate MonoRepo Structure
-Create the following Nx workspace structure:
-
-```
-apps/{service-name}/
-├── src/
-│   ├── modules/
-│   │   └── {context}/
-│   │       ├── application/
-│   │       │   ├── ports/
-│   │       │   ├── use-cases/
-│   │       │   ├── commands/
-│   │       │   ├── queries/
-│   │       │   └── dto/
-│   │       ├── domain/
-│   │       │   ├── entities/
-│   │       │   ├── value-objects/
-│   │       │   ├── aggregates/
-│   │       │   ├── events/
-│   │       │   └── services/
-│   │       └── infrastructure/
-│   │           ├── repositories/
-│   │           ├── services/
-│   │           └── events/
-│   ├── api/
-│   │   ├── controllers/
-│   │   ├── guards/
-│   │   ├── middlewares/
-│   │   └── filters/
-│   ├── config/
-│   ├── main.ts
-│   └── app.module.ts
-├── test/
-├── prisma/
-│   ├── schema.prisma
-│   └── migrations/
-└── package.json
-```
-
-### Step 3: Setup NestJS Configuration
-- Initialize NestJS application with TypeScript
-- Configure Nx workspace if not exists
-- Setup Prisma with selected database
-- Configure dependency injection container
-- Setup validation with class-validator
-- Configure Swagger/OpenAPI documentation
-- Setup health checks and monitoring
-
-### Step 4: Generate Domain Contexts
-For each bounded context:
-- Create hexagonal architecture layers
-- Generate base domain entities with DDD patterns
-- Create application ports (interfaces)
-- Setup infrastructure adapters
-- Create Prisma schema definitions
-- Generate initial use cases
-
-### Step 5: Setup Shared Infrastructure
-- Configure JWT authentication
-- Setup Redis for caching and messaging
-- Configure CORS and security headers
-- Setup logging with Winston
-- Configure environment variables
-- Setup database connection pooling
-
-### Step 6: Generate Initial Tests
-- Unit tests for domain entities
-- Integration tests for use cases
-- E2E tests for API endpoints
-- Repository tests with test database
-- Mocking strategies for external dependencies
-
-## Completion Criteria
-- MonoRepo structure follows hexagonal architecture
-- All dependencies properly configured
-- Prisma schema generated and migrated
-- TypeScript compiles without errors
-- Initial tests pass
-- Swagger documentation accessible
+# Scaffold Backend Microservice
+
+## Purpose
+Generate complete microservice structure with Hexagonal Architecture + DDD principles using NestJS.
+
+**CRITICAL**: Always use NestJS 10+ with TypeScript, Prisma ORM, and strict hexagonal architecture patterns. No raw queries allowed - use Prisma for all database operations.
+
+## Task Configuration
+```yaml
+elicit: true
+interactive: true
+required_params:
+  - service_name
+  - domain_contexts
+optional_params:
+  - database_type
+  - messaging_transport
+  - shared_libraries
+```
+
+## Task Execution
+
+### Step 1: Elicit Service Requirements
+Ask user for the following information:
+
+**Service Name**: What would you like to name your microservice? (use kebab-case)
+**Domain Contexts**: List the main bounded contexts for this service (e.g., quotes, products, billing)
+**Database Type**: Which database will this service use? (PostgreSQL, MySQL, MongoDB - default: PostgreSQL)
+**Messaging Transport**: What messaging transport? (Redis, RabbitMQ, gRPC - default: Redis)
+**Shared Libraries**: Any existing shared libraries to include? (optional)
+
+### Step 2: Generate MonoRepo Structure
+Create the following Nx workspace structure:
+
+```
+apps/{service-name}/
+├── src/
+│   ├── modules/
+│   │   └── {context}/
+│   │       ├── application/
+│   │       │   ├── ports/
+│   │       │   ├── use-cases/
+│   │       │   ├── commands/
+│   │       │   ├── queries/
+│   │       │   └── dto/
+│   │       ├── domain/
+│   │       │   ├── entities/
+│   │       │   ├── value-objects/
+│   │       │   ├── aggregates/
+│   │       │   ├── events/
+│   │       │   └── services/
+│   │       └── infrastructure/
+│   │           ├── repositories/
+│   │           ├── services/
+│   │           └── events/
+│   ├── api/
+│   │   ├── controllers/
+│   │   ├── guards/
+│   │   ├── middlewares/
+│   │   └── filters/
+│   ├── config/
+│   ├── main.ts
+│   └── app.module.ts
+├── test/
+├── prisma/
+│   ├── schema.prisma
+│   └── migrations/
+└── package.json
+```
+
+### Step 3: Setup NestJS Configuration
+- Initialize NestJS application with TypeScript
+- Configure Nx workspace if not exists
+- Setup Prisma with selected database
+- Configure dependency injection container
+- Setup validation with class-validator
+- Configure Swagger/OpenAPI documentation
+- Setup health checks and monitoring
+
+### Step 4: Generate Domain Contexts
+For each bounded context:
+- Create hexagonal architecture layers
+- Generate base domain entities with DDD patterns
+- Create application ports (interfaces)
+- Setup infrastructure adapters
+- Create Prisma schema definitions
+- Generate initial use cases
+
+### Step 5: Setup Shared Infrastructure
+- Configure JWT authentication
+- Setup Redis for caching and messaging
+- Configure CORS and security headers
+- Setup logging with Winston
+- Configure environment variables
+- Setup database connection pooling
+
+### Step 6: Generate Initial Tests
+- Unit tests for domain entities
+- Integration tests for use cases
+- E2E tests for API endpoints
+- Repository tests with test database
+- Mocking strategies for external dependencies
+
+## Completion Criteria
+- MonoRepo structure follows hexagonal architecture
+- All dependencies properly configured
+- Prisma schema generated and migrated
+- TypeScript compiles without errors
+- Initial tests pass
+- Swagger documentation accessible
 - Health checks responding

package/bmad-core/tasks/scaffold-frontend.md

@@ -1,79 +1,79 @@
-# Scaffold Frontend Project
-
-## Purpose
-Generate complete frontend project structure with Clean Architecture + DDD principles.
-
-**CRITICAL**: Always use Next.js 14+ with App Router as the default framework. Only use pure React + Vite when user explicitly mentions offline-first functionality or specifically requests non-Next.js setup.
-
-## Task Configuration
-```yaml
-elicit: true
-interactive: true
-required_params:
-  - project_name
-  - features
-optional_params:
-  - pwa_enabled
-  - theme_config
-```
-
-## Task Execution
-
-### Step 1: Elicit Project Requirements
-Ask user for the following information:
-
-**Project Name**: What would you like to name your frontend project?
-**Initial Features**: List the main features/modules you want to start with (e.g., auth, dashboard, profile)
-**PWA Enabled**: Do you want Progressive Web App capabilities? (default: yes)
-**Theme Configuration**: Do you have specific theme/brand requirements?
-
-### Step 2: Generate Project Structure
-Create the following folder structure:
-
-```
-src/
-├── features/
-│   └── shared/
-│       ├── components/
-│       ├── hooks/
-│       ├── utils/
-│       └── types/
-├── app/
-│   ├── providers/
-│   ├── router/
-│   └── store/
-└── infrastructure/
-    ├── api/
-    ├── storage/
-    └── pwa/
-```
-
-### Step 3: Setup Configuration Files
-- Initialize Next.js 14+ project with TypeScript
-- Configure Next.js config for App Router
-- Setup TailwindCSS + Shadcn/ui integration
-- Configure Vitest for testing (with Next.js)
-- Setup ESLint + Prettier (Next.js config)
-- Configure PWA with Next.js PWA plugin if requested
-- Setup environment configuration
-
-### Step 4: Generate Initial Features
-For each feature requested:
-- Create feature folder with DDD structure
-- Generate basic domain entities
-- Create application layer with hooks and stores
-- Setup infrastructure layer with API clients
-- Create presentation layer with basic components
-
-### Step 5: Validation
-- Verify all files compile without errors
-- Run initial tests
-- Check TypeScript strict mode compliance
-- Validate folder structure follows Clean Architecture
-
-## Completion Criteria
-- Project structure matches Clean Architecture patterns
-- All dependencies are properly installed
-- Initial features are scaffolded with all layers
-- TypeScript compiles without errors
+# Scaffold Frontend Project
+
+## Purpose
+Generate complete frontend project structure with Clean Architecture + DDD principles.
+
+**CRITICAL**: Always use Next.js 14+ with App Router as the default framework. Only use pure React + Vite when user explicitly mentions offline-first functionality or specifically requests non-Next.js setup.
+
+## Task Configuration
+```yaml
+elicit: true
+interactive: true
+required_params:
+  - project_name
+  - features
+optional_params:
+  - pwa_enabled
+  - theme_config
+```
+
+## Task Execution
+
+### Step 1: Elicit Project Requirements
+Ask user for the following information:
+
+**Project Name**: What would you like to name your frontend project?
+**Initial Features**: List the main features/modules you want to start with (e.g., auth, dashboard, profile)
+**PWA Enabled**: Do you want Progressive Web App capabilities? (default: yes)
+**Theme Configuration**: Do you have specific theme/brand requirements?
+
+### Step 2: Generate Project Structure
+Create the following folder structure:
+
+```
+src/
+├── features/
+│   └── shared/
+│       ├── components/
+│       ├── hooks/
+│       ├── utils/
+│       └── types/
+├── app/
+│   ├── providers/
+│   ├── router/
+│   └── store/
+└── infrastructure/
+    ├── api/
+    ├── storage/
+    └── pwa/
+```
+
+### Step 3: Setup Configuration Files
+- Initialize Next.js 14+ project with TypeScript
+- Configure Next.js config for App Router
+- Setup TailwindCSS + Shadcn/ui integration
+- Configure Vitest for testing (with Next.js)
+- Setup ESLint + Prettier (Next.js config)
+- Configure PWA with Next.js PWA plugin if requested
+- Setup environment configuration
+
+### Step 4: Generate Initial Features
+For each feature requested:
+- Create feature folder with DDD structure
+- Generate basic domain entities
+- Create application layer with hooks and stores
+- Setup infrastructure layer with API clients
+- Create presentation layer with basic components
+
+### Step 5: Validation
+- Verify all files compile without errors
+- Run initial tests
+- Check TypeScript strict mode compliance
+- Validate folder structure follows Clean Architecture
+
+## Completion Criteria
+- Project structure matches Clean Architecture patterns
+- All dependencies are properly installed
+- Initial features are scaffolded with all layers
+- TypeScript compiles without errors
 - Basic tests pass