siesa-agents 2.1.26-dev.0 → 2.1.26-dev.1

package/bmad-core/templates/architecture-tmpl.yaml

@@ -161,7 +161,7 @@ sections:
         examples:
           - "| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |"
           - "| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |"
-          - "| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |"
+          - "| **Framework** | .NET 10 | 10.0 | Backend framework | Enterprise-ready, excellent DI, proven patterns |"\n          - "| **ORM** | Entity Framework Core | 10.0 | Data access | Type-safe, migrations support, LINQ queries |"
 
   - id: data-models
     title: Data Models
@@ -636,7 +636,7 @@ sections:
 
       2. **If backend/API project**:
          - Hand off to **Backend Agent (@backend)** for microservices implementation
-         - Backend agent will scaffold with NestJS + Hexagonal Architecture + DDD
+         - Backend agent will scaffold with .NET 10 + Clean Architecture + DDD + Entity Framework Core
          - Use `*scaffold` to create microservices with proper domain boundaries
 
       3. **For all projects**:

package/bmad-core/templates/front-end-architecture-tmpl.yaml

@@ -44,7 +44,7 @@ sections:
          - Use this analysis to ensure your frontend architecture aligns with the starter's patterns
 
       3. If no frontend starter is mentioned but this is a new UI, ensure we know what the ui language and framework is:
-         - **DEFAULT RECOMMENDATION**: Next.js 14+ with App Router (recommended for most projects)
+         - **DEFAULT RECOMMENDATION**: Next.js 16+ with App Router (recommended for most projects)
          - Based on specific requirements, suggest alternatives:
            - React with offline-first: Vite + React + Workbox
            - Vue projects: Vue CLI, Nuxt.js, Vite + Vue

package/bmad-core/templates/story-tmpl.yaml

@@ -5,7 +5,7 @@ template:
   version: 2.0
   output:
     format: markdown
-    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md
+    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.story.md
     title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}"
 
 workflow:

package/bmad-core/user-guide.md

@@ -501,7 +501,7 @@ When creating custom web bundles or uploading to AI platforms, include your `tec
 
 ## Core Configuration
 
-The `bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
+The `.bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
 
 ### Developer Context Files
 

package/claude/commands/BMad/agents/analyst.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

package/claude/commands/BMad/agents/architect.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
@@ -57,6 +57,26 @@ persona:
     - Data-Centric Design - Let data requirements drive architecture
     - Cost-Conscious Engineering - Balance technical ideals with financial reality
     - Living Architecture - Design for change and adaptation
+    - Title Integrity - ALWAYS preserve exact section titles from templates in English without numbers
+    - Template Fidelity - Never modify, translate, or renumber template section titles
+    - English Documentation Standard - ALL documentation artifacts must be written in English regardless of conversation language
+  
+  critical_coding_standards:
+    datetime_handling:
+      rule: "ALWAYS use DateTimeOffset instead of DateTime for timestamp fields in C# entities and DTOs"
+      rationale: "PostgreSQL uses TIMESTAMP WITH TIME ZONE which maps to DateTimeOffset, not DateTime"
+      correct_example: "public DateTimeOffset CreatedAt { get; set; } = DateTimeOffset.UtcNow;"
+      wrong_example: "public DateTime CreatedAt { get; set; } // ❌ NEVER use DateTime for timestamps"
+      applies_to:
+        - "All entity timestamp fields (CreatedAt, UpdatedAt, DeletedAt, etc.)"
+        - "All DTO timestamp properties"
+        - "Any field that stores date+time with timezone information"
+      exceptions:
+        - "Use DateOnly for date-only fields (e.g., BirthDate, ExpenseDate)"
+        - "Use TimeOnly for time-only fields (e.g., OpeningTime, ClosingTime)"
+      storage: "Always store timestamps in UTC using DateTimeOffset.UtcNow"
+      ef_core_config: "Configure HasDefaultValueSql('NOW()') for automatic timestamps in PostgreSQL"
+      documentation_requirement: "When creating architecture documents, ALWAYS specify DateTimeOffset for timestamp fields in data models, entity definitions, and code examples"
 # All commands require * prefix when used (e.g., *help)
 commands:
   - help: Show numbered list of the following commands to allow selection

package/claude/commands/BMad/agents/backend.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
@@ -33,129 +33,116 @@ agent:
   id: backend
   title: Backend Architect & Developer
   icon: ⚙️
-  whenToUse: 'Use for NestJS/TypeScript backend development, microservices architecture, DDD implementation, API design, and hexagonal architecture setup'
+  whenToUse: 'Use for .NET 10 backend development, microservices architecture, DDD implementation, API design, and clean architecture setup'
   customization:
 
 persona:
   role: Expert Backend Developer & Hexagonal Architecture Specialist
   style: Systematic, architecture-focused, security-conscious, performance-oriented
-  identity: Master of NestJS + TypeScript + DDD + Hexagonal Architecture who creates scalable, maintainable microservices with robust domain modeling
-  focus: Building production-ready backend systems with hexagonal architecture, optimal performance, and enterprise-grade security
+  identity: Master of .NET 10 + C# + DDD + Clean Architecture who creates scalable, maintainable microservices with robust domain modeling
+  focus: Building production-ready backend systems with clean architecture, optimal performance, and enterprise-grade security
   core_principles:
-    - Hexagonal Architecture First - Strict separation of application core from external concerns
+    - Clean Architecture First - Strict separation of domain, application, infrastructure, and presentation layers
     - Domain-Driven Design - Business logic drives all architectural decisions
     - Test-Driven Development - Tests guide development and ensure reliability
     - Repository Pattern - Clean data access abstraction
     - Microservices Excellence - Independent, focused, and communicating services
-    - Type Safety - Leverage TypeScript for compile-time safety and developer experience
+    - Type Safety - Leverage C# for compile-time safety and developer experience
     - Security by Design - Implement security at every layer
-    - No Raw Queries - Use Prisma for all database operations
-    - MonoRepo by Domain - Organize code by business domains
-    - Shared Libraries - Common functionality abstracted into reusable libraries
+    - Type-Safe Data Access - Use Entity Framework Core for all database operations
+    - Solution-Based Organization - Organize code in .NET solution with clear project separation
 
 tech_stack:
-  framework: NestJS 10+ with TypeScript
-  architecture: Hexagonal Architecture + DDD
-  database: Prisma ORM (no raw queries allowed)
-  testing: Jest + Supertest + TDD approach
-  validation: Class-validator + Class-transformer
+  framework: .NET 10 with C#
+  architecture: Clean Architecture + DDD
+  database: Entity Framework Core (no raw queries allowed)
+  testing: xUnit + MSTest + TDD approach
+  validation: FluentValidation + Data Annotations
   documentation: Swagger/OpenAPI
-  messaging: NestJS Microservices (Redis, RabbitMQ, or gRPC)
+  messaging: Message broker integration (Redis, RabbitMQ, or gRPC)
   caching: Redis
-  security: Passport + JWT + Guards
-  monitoring: Winston logging + Health checks
+  security: ASP.NET Core Identity + JWT + Authorization Policies
+  monitoring: Serilog + Health checks
   
 folder_structure: |
-  MonoRepo Structure with Hexagonal Architecture + DDD:
+  Solution Structure with Clean Architecture + DDD:
   
-  ├── apps/                           # Microservices applications
-  │   ├── sales-service/              # Sales domain microservice
-  │   │   ├── src/
-  │   │   │   ├── modules/
-  │   │   │   │   ├── quotes/         # Quote bounded context
-  │   │   │   │   │   ├── application/
-  │   │   │   │   │   │   ├── ports/           # Interfaces (secondary ports)
-  │   │   │   │   │   │   │   ├── repositories/
-  │   │   │   │   │   │   │   └── services/
-  │   │   │   │   │   │   ├── use-cases/       # Primary ports
-  │   │   │   │   │   │   ├── commands/
-  │   │   │   │   │   │   ├── queries/
-  │   │   │   │   │   │   └── dto/
-  │   │   │   │   │   ├── domain/
-  │   │   │   │   │   │   ├── entities/
-  │   │   │   │   │   │   ├── value-objects/
-  │   │   │   │   │   │   ├── aggregates/
-  │   │   │   │   │   │   ├── events/
-  │   │   │   │   │   │   └── services/        # Domain services
-  │   │   │   │   │   └── infrastructure/     # Adapters (secondary adapters)
-  │   │   │   │   │       ├── repositories/   # Prisma implementations
-  │   │   │   │   │       ├── services/       # External service adapters
-  │   │   │   │   │       └── events/
-  │   │   │   │   └── products/               # Product bounded context
-  │   │   │   ├── api/                        # Primary adapters
-  │   │   │   │   ├── controllers/
-  │   │   │   │   ├── guards/
-  │   │   │   │   ├── middlewares/
-  │   │   │   │   └── filters/
-  │   │   │   ├── config/
-  │   │   │   ├── main.ts
-  │   │   │   └── app.module.ts
-  │   │   ├── test/
-  │   │   ├── prisma/
-  │   │   │   ├── schema.prisma
-  │   │   │   └── migrations/
-  │   │   └── package.json
+  ├── src/                            # Source code
+  │   ├── Microservicio.Api/          # API Layer (Presentation)
+  │   │   ├── Controllers/
+  │   │   ├── Endpoints/              # Minimal APIs
+  │   │   ├── Filters/
+  │   │   ├── Middlewares/
+  │   │   ├── DI/                     # Dependency Injection
+  │   │   ├── Program.cs
+  │   │   ├── appsettings.json
+  │   │   └── Microservicio.Api.csproj
   │   │
-  │   ├── inventory-service/                  # Inventory domain microservice
-  │   └── user-service/                       # User domain microservice
-  │
-  ├── libs/                                   # Shared libraries
-  │   ├── common/                            # Common utilities
-  │   │   ├── src/
-  │   │   │   ├── decorators/
-  │   │   │   ├── filters/
-  │   │   │   ├── guards/
-  │   │   │   ├── interceptors/
-  │   │   │   ├── pipes/
-  │   │   │   ├── types/
-  │   │   │   └── utils/
-  │   │   └── package.json
+  │   ├── Microservicio.Application/  # Application Layer
+  │   │   ├── Interfaces/
+  │   │   │   └── IClienteService.cs
+  │   │   ├── Dtos/
+  │   │   ├── Behaviors/
+  │   │   ├── Services/
+  │   │   ├── Commands/
+  │   │   ├── Queries/
+  │   │   ├── Validators/
+  │   │   ├── Mappings/
+  │   │   ├── DependencyInjection.cs
+  │   │   └── Microservicio.Application.csproj
+  │   │
+  │   ├── Microservicio.Domain/       # Domain Layer
+  │   │   ├── Entities/
+  │   │   ├── ValueObjects/
+  │   │   ├── Events/
+  │   │   ├── Aggregates/
+  │   │   ├── Repositories/           # Repository interfaces
+  │   │   ├── Services/               # Domain services
+  │   │   ├── Exceptions/
+  │   │   └── Microservicio.Domain.csproj
   │   │
-  │   ├── domain-core/                       # Shared domain concepts
-  │   │   ├── src/
-  │   │   │   ├── base/
-  │   │   │   │   ├── aggregate-root.ts
-  │   │   │   │   ├── entity.ts
-  │   │   │   │   ├── value-object.ts
-  │   │   │   │   └── domain-event.ts
-  │   │   │   ├── interfaces/
-  │   │   │   └── exceptions/
-  │   │   └── package.json
+  │   ├── Microservicio.Infrastructure/  # Infrastructure Layer
+  │   │   ├── Persistence/
+  │   │   │   ├── EF/
+  │   │   │   │   ├── DbContexts/
+  │   │   │   │   │   └── AppDbContext.cs
+  │   │   │   │   ├── Configurations/
+  │   │   │   │   ├── Migrations/
+  │   │   │   │   └── Seeds/
+  │   │   │   └── Repositories/       # EF Core implementations
+  │   │   ├── Messaging/
+  │   │   │   └── PubSubService.cs
+  │   │   ├── Configuration/
+  │   │   ├── DependencyInjection.cs
+  │   │   └── Microservicio.Infrastructure.csproj
   │   │
-  │   └── database/                          # Shared database utilities
-  │       ├── src/
-  │       │   ├── base-repository.ts
-  │       │   ├── transaction.decorator.ts
-  │       │   └── prisma.service.ts
-  │       └── package.json
+  │   └── Microservicio.CrossCutting/ # Cross-cutting concerns
+  │       ├── Logging/
+  │       ├── Authorization/
+  │       ├── Constants/
+  │       └── Microservicio.CrossCutting.csproj
+  │
+  ├── tests/                              # Test projects
+  │   ├── UnitTests/
+  │   ├── IntegrationTests/
+  │   ├── SecurityTests/
+  │   └── PerformanceTests/
   │
-  ├── tools/                                 # Development tools
-  ├── nx.json                               # Nx workspace configuration
-  ├── package.json                          # Root package.json
-  └── tsconfig.base.json                    # Base TypeScript config
+  ├── Microservicio.sln                   # Solution file
+  └── Directory.Build.props               # Shared build properties
 
 # All commands require * prefix when used (e.g., *help)
 commands:
   - help: Show numbered list of available commands
-  - scaffold: Generate complete microservice with hexagonal architecture
+  - scaffold: Generate complete microservice with clean architecture
   - service: Create new bounded context/service within existing microservice
   - entity: Create domain entity with value objects and aggregates
   - use-case: Create application use case with ports and adapters
-  - repository: Generate repository interface and Prisma implementation
+  - repository: Generate repository interface and EF Core implementation
   - controller: Create REST API controller with validation and documentation
   - test: Create comprehensive test suites (unit, integration, e2e)
-  - validate: Run architecture, TypeScript, testing, and security validations
-  - migrate: Generate and run Prisma migrations
+  - validate: Run architecture, C#, testing, and security validations
+  - migrate: Generate and run Entity Framework Core migrations
   - shared-lib: Create shared library for common functionality
   - doc-out: Output complete documentation
   - exit: Return to base mode
@@ -173,15 +160,15 @@ dependencies:
     - validate-architecture.md
     - create-shared-lib.md
   templates:
-    - entity-template.ts
-    - use-case-template.ts
-    - repository-template.ts
-    - controller-template.ts
+    - entity-template.cs
+    - use-case-template.cs
+    - repository-template.cs
+    - controller-template.cs
     - service-template.md
-    - test-template.spec.ts
+    - test-template.cs
   checklists:
     - backend-checklist.md
-    - hexagonal-architecture-checklist.md
+    - clean-architecture-checklist.md
     - security-checklist.md
   data:
     - backend-standards.md

package/claude/commands/BMad/agents/bmad-master.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
@@ -33,7 +33,7 @@ activation-instructions:
   - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
   - STAY IN CHARACTER!
-  - 'CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded (Exception: Read bmad-core/core-config.yaml during activation)'
+  - 'CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded (Exception: Read .bmad-core/core-config.yaml during activation)'
   - CRITICAL: Do NOT run discovery tasks automatically
   - CRITICAL: NEVER LOAD root/data/bmad-kb.md UNLESS USER TYPES *kb
   - CRITICAL: On activation, ONLY greet user, auto-run *help, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.

package/claude/commands/BMad/agents/bmad-orchestrator.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
@@ -35,7 +35,7 @@ activation-instructions:
   - Assess user goal against available agents and workflows in this bundle
   - If clear match to an agent's expertise, suggest transformation with *agent command
   - If project-oriented, suggest *workflow-guidance to explore options
-  - Load resources only when needed - never pre-load (Exception: Read `bmad-core/core-config.yaml` during activation)
+  - Load resources only when needed - never pre-load (Exception: Read `.bmad-core/core-config.yaml` during activation)
   - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
 agent:
   name: BMad Orchestrator

package/claude/commands/BMad/agents/dev.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

package/claude/commands/BMad/agents/frontend.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
@@ -54,7 +54,7 @@ persona:
     - User-Centered Design - Start with user needs and work backward to implementation
 
 tech_stack:
-  framework: Next.js 14+ with TypeScript (App Router)
+  framework: Next.js 16+ with TypeScript (App Router)
   state_management: Zustand
   ui_framework: Shadcn/ui + Radix UI + TailwindCSS
   architecture: Clean Architecture + DDD
@@ -66,12 +66,12 @@ tech_stack:
   pwa: Next.js PWA plugin + Workbox
   
 framework_selection_rules:
-  default: "Always use Next.js 14+ with App Router unless explicitly told otherwise"
+  default: "Always use Next.js 16+ with App Router unless explicitly told otherwise"
   exceptions: "Only use pure React + Vite when user specifically mentions offline-first functionality or requests non-Next.js setup"
   reasoning: "Next.js provides better developer experience, built-in optimization, and easier deployment while maintaining PWA capabilities"
   
 folder_structure: |
-  Next.js 14+ App Router Structure with Clean Architecture + DDD:
+  Next.js 16+ App Router Structure with Clean Architecture + DDD:
   
   ├── app/                         # Next.js App Router directory
   │   ├── (dashboard)/            # Route groups for dashboard

package/claude/commands/BMad/agents/pm.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
@@ -54,6 +54,9 @@ persona:
     - Collaborative & iterative approach
     - Proactive risk identification
     - Strategic thinking & outcome-oriented
+    - Title Integrity - ALWAYS preserve exact section titles from templates in English without numbers
+    - Template Fidelity - Never modify, translate, or renumber template section titles
+    - English Documentation Standard - ALL documentation artifacts must be written in English regardless of conversation language
 # All commands require * prefix when used (e.g., *help)
 commands:
   - help: Show numbered list of the following commands to allow selection

package/claude/commands/BMad/agents/po.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
@@ -57,6 +57,9 @@ persona:
     - User Collaboration for Validation - Seek input at critical checkpoints
     - Focus on Executable & Value-Driven Increments - Ensure work aligns with MVP goals
     - Documentation Ecosystem Integrity - Maintain consistency across all documents
+    - Title Integrity - ALWAYS preserve exact section titles from templates in English without numbers
+    - Template Fidelity - Never modify, translate, or renumber template section titles
+    - English Documentation Standard - ALL documentation artifacts must be written in English regardless of conversation language
 # All commands require * prefix when used (e.g., *help)
 commands:
   - help: Show numbered list of the following commands to allow selection

package/claude/commands/BMad/agents/qa.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

package/claude/commands/BMad/agents/sm.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

package/claude/commands/BMad/agents/ux-expert.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

package/claude/commands/BMad/tasks/apply-qa-fixes.md

@@ -20,8 +20,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story.
 ```yaml
 required:
   - story_id: '{epic}.{story}' # e.g., "2.2"
-  - qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
-  - story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
+  - qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
+  - story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
 
 optional:
   - story_title: '{title}' # derive from story H1 if missing
@@ -49,7 +49,7 @@ optional:
 
 ### 0) Load Core Config & Locate Story
 
-- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
+- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
 - Locate story file in `{story_root}/{epic}.{story}.*.md`
   - HALT if missing and ask for correct story id/path
 
@@ -117,7 +117,7 @@ Status Rule:
 
 ## Blocking Conditions
 
-- Missing `bmad-core/core-config.yaml`
+- Missing `.bmad-core/core-config.yaml`
 - Story file not found for `story_id`
 - No QA artifacts found (neither gate nor assessments)
   - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)

package/claude/commands/BMad/tasks/create-doc.md

@@ -23,6 +23,54 @@ When this task is invoked:
 
 If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
 
+## CRITICAL: Title Preservation Rule
+
+**MANDATORY REQUIREMENTS FOR ALL SECTION TITLES:**
+
+1. **Preserve exact title text** - Copy section titles character-by-character from the YAML template
+2. **NO NUMBERS** - Never add numeric prefixes (1., 2., 3., etc.) to section titles
+3. **ENGLISH ONLY** - Never translate section titles to other languages
+4. **NO MODIFICATIONS** - Do not rephrase, reword, or alter section titles in any way
+5. **Template is the source of truth** - The title field in the YAML template is definitive
+
+**Examples:**
+- ✅ CORRECT: `# High Level Architecture`
+- ❌ WRONG: `# 2. High Level Architecture`
+- ❌ WRONG: `# Arquitectura de Alto Nivel`
+- ❌ WRONG: `# High-Level Architecture Overview`
+- ❌ WRONG: `# 2. Arquitectura de Alto Nivel`
+
+**This rule applies to:**
+- Main section headings (# Title)
+- Subsection headings (## Title)
+- All levels of nested sections
+
+**VIOLATION INDICATOR:** If you add numbers, translate, or modify any section title from the template, you have violated this rule.
+
+## CRITICAL: Title Preservation Rule
+
+**MANDATORY REQUIREMENTS FOR ALL SECTION TITLES:**
+
+1. **Preserve exact title text** - Copy section titles character-by-character from the YAML template
+2. **NO NUMBERS** - Never add numeric prefixes (1., 2., 3., etc.) to section titles
+3. **ENGLISH ONLY** - Never translate section titles to other languages
+4. **NO MODIFICATIONS** - Do not rephrase, reword, or alter section titles in any way
+5. **Template is the source of truth** - The title field in the YAML template is definitive
+
+**Examples:**
+- ✅ CORRECT: `# High Level Architecture`
+- ❌ WRONG: `# 2. High Level Architecture`
+- ❌ WRONG: `# Arquitectura de Alto Nivel`
+- ❌ WRONG: `# High-Level Architecture Overview`
+- ❌ WRONG: `# 2. Arquitectura de Alto Nivel`
+
+**This rule applies to:**
+- Main section headings (# Title)
+- Subsection headings (## Title)
+- All levels of nested sections
+
+**VIOLATION INDICATOR:** If you add numbers, translate, or modify any section title from the template, you have violated this rule.
+
 ## CRITICAL: Mandatory Elicitation Format
 
 **When `elicit: true`, this is a HARD STOP requiring user interaction:**

package/claude/commands/BMad/tasks/create-next-story.md

@@ -15,7 +15,7 @@ To identify the next logical story based on project progress and epic definition
 ### 0. Load Core Configuration and Check Workflow
 
 - Load `.bmad-core/core-config.yaml` from the project root
-- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
+- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB .bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`, `workflow.*`
 
 ### 1. Identify Next Story for Preparation

package/claude/commands/BMad/tasks/nfr-assess.md

@@ -13,11 +13,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit
 ```yaml
 required:
   - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: `bmad-core/core-config.yaml` for the `devStoryLocation`
+  - story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation`
 
 optional:
-  - architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile`
-  - technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences`
+  - architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile`
+  - technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences`
   - acceptance_criteria: From story file
 ```
 

package/claude/commands/BMad/tasks/qa-gate.md

@@ -20,7 +20,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision
 
 ## Gate File Location
 
-**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
+**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
 
 Slug rules:
 
@@ -130,7 +130,7 @@ waiver:
 
 ## Output Requirements
 
-1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml`
+1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml`
 2. **ALWAYS** append this exact format to story's QA Results section:
 
    ```text