siesa-agents 2.1.41 → 2.1.43

package/bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md

@@ -42,19 +42,89 @@ This step will generate content and present choices:
 - User journeys from step 10 identify component needs
 - Focus on defining custom components and implementation strategy
 
+## 🔴 CRITICAL: SIESA-UI-KIT MANDATORY CHECK
+
+**BEFORE defining ANY component strategy, you MUST:**
+
+1. **Load Company Standards** from `{company_standards_path}/frontend-standards.md`
+2. **Check siesa-ui-kit FIRST** for every component need identified
+3. **Follow the Component Decision Protocol** below
+
+### Component Decision Protocol
+
+For EVERY component needed in the UX specification:
+
+```
+┌─────────────────────────────────────────┐
+│  Component Needed: [Component Name]      │
+└─────────────────────────────────────────┘
+                    │
+                    ▼
+┌─────────────────────────────────────────┐
+│  Is it in siesa-ui-kit?                 │
+└─────────────────────────────────────────┘
+          │                    │
+         YES                   NO
+          │                    │
+          ▼                    ▼
+┌─────────────────┐  ┌─────────────────────────┐
+│ USE siesa-ui-kit │  │ ASK USER:               │
+│ component AS-IS  │  │ [1] Use shadcn directly │
+└─────────────────┘  │ [2] Create custom for   │
+                     │     siesa-ui-kit (MR)   │
+                     └─────────────────────────┘
+```
+
+### Why This Matters
+
+| Rule | Impact |
+|------|--------|
+| **siesa-ui-kit first** | 90% fewer bugs vs manual creation |
+| **Consistency** | Unified experience across all Siesa products |
+| **Maintenance** | Platform team maintains shared components |
+| **Compliance** | Meets company visual and accessibility standards |
+
+### UI Text Language Rule
+
+🔴 **MANDATORY**: All user-facing text in UX specifications MUST be in Spanish.
+
+**✅ CORRECT:**
+- Buttons: "Guardar", "Cancelar", "Enviar"
+- Labels: "Nombre de usuario", "Contraseña"
+- Messages: "Datos guardados correctamente"
+
+**❌ INCORRECT:**
+- Mixed: "Save cambios", "Failed al guardar"
+- English: "Save", "Cancel", "Submit"
+
 ## YOUR TASK:
 
 Define component library strategy and design custom components not covered by the design system.
 
 ## COMPONENT STRATEGY SEQUENCE:
 
-### 1. Analyze Design System Coverage
+### 1. Load siesa-ui-kit and Company Standards
+
+🔴 **FIRST**: Before any analysis, load:
+- `{company_standards_path}/frontend-standards.md`
+- Check if siesa-ui-kit documentation exists in project
+
+"Before we analyze components, let me load the company standards and siesa-ui-kit to ensure we follow Siesa's component guidelines."
 
-Review what components are available vs. needed:
-"Based on our chosen design system [design system from step 6], let's identify what components are already available and what we need to create custom.
+### 2. Analyze Component Coverage (siesa-ui-kit FIRST)
 
-**Available from Design System:**
-[List of components available in chosen design system]
+Review components in this priority order:
+1. **siesa-ui-kit** (company shared components) - USE FIRST
+2. **Design System** from step 6 (shadcn/Radix) - fallback
+3. **Custom components** - only if not in above
+
+"Based on siesa-ui-kit and our chosen design system, let's identify what components are already available.
+
+**🟢 Available from siesa-ui-kit:**
+[List components from siesa-ui-kit that match our needs - THESE MUST BE USED]
+
+**🟡 Available from Design System (shadcn/Radix):**
+[List of components available but NOT in siesa-ui-kit]
 
 **Components Needed for {{project_name}}:**
 Looking at our user journeys and design direction, we need:
@@ -63,12 +133,13 @@ Looking at our user journeys and design direction, we need:
 - [Component need 2 from design requirements]
 - [Component need 3 from core experience]
 
-**Gap Analysis:**
+**Gap Analysis (Components NOT in siesa-ui-kit or Design System):**
 
-- [Gap 1 - needed but not available]
-- [Gap 2 - needed but not available]"
+For each gap, we need to ask:
+- [Gap 1] → [1] Use shadcn directly OR [2] Create for siesa-ui-kit?
+- [Gap 2] → [1] Use shadcn directly OR [2] Create for siesa-ui-kit?"
 
-### 2. Design Custom Components
+### 3. Design Custom Components
 
 For each custom component needed, design thoroughly:
 
@@ -84,7 +155,7 @@ For each custom component needed, design thoroughly:
 
 Let's walk through each custom component systematically."
 
-### 3. Document Component Specifications
+### 4. Document Component Specifications
 
 Create detailed specifications for each component:
 
@@ -103,7 +174,7 @@ Create detailed specifications for each component:
 **Interaction Behavior:** [How users interact]
 ```
 
-### 4. Define Component Strategy
+### 5. Define Component Strategy
 
 Establish overall component library approach:
 "**Component Strategy:**
@@ -125,7 +196,7 @@ Establish overall component library approach:
 - Follow accessibility best practices
 - Create reusable patterns for common use cases"
 
-### 5. Plan Implementation Roadmap
+### 6. Plan Implementation Roadmap
 
 Define how and when to build components:
 "**Implementation Roadmap:**
@@ -147,7 +218,7 @@ Define how and when to build components:
 
 This roadmap helps prioritize development based on user journey criticality."
 
-### 6. Generate Component Strategy Content
+### 7. Generate Component Strategy Content
 
 Prepare the content to append to the document:
 
@@ -158,24 +229,30 @@ When saving to document, append these Level 2 and Level 3 sections:
 ```markdown
 ## Component Strategy
 
-### Design System Components
+### siesa-ui-kit Components (Priority 1)
+
+[List all components from siesa-ui-kit that will be used - THESE ARE MANDATORY]
+
+### Design System Components (Priority 2)
 
-[Analysis of available design system components based on conversation]
+[Components from shadcn/Radix not covered by siesa-ui-kit]
 
-### Custom Components
+### Custom Components (Priority 3)
 
-[Custom component specifications based on conversation]
+[Custom component specifications - only for gaps not covered above]
+[Include decision: shadcn direct OR create for siesa-ui-kit MR]
 
 ### Component Implementation Strategy
 
 [Component implementation strategy based on conversation]
+[Include UI text language: Spanish for all user-facing text]
 
 ### Implementation Roadmap
 
 [Implementation roadmap based on conversation]
 ```
 
-### 7. Present Content and Menu
+### 8. Present Content and Menu
 
 Show the generated component strategy content and present choices:
 "I've defined the component strategy for {{project_name}}. This balances using proven design system components with custom components for your unique needs.
@@ -189,7 +266,7 @@ Show the generated component strategy content and present choices:
 [P] Party Mode - Bring technical perspectives on component design
 [C] Continue - Save this to the document and move to UX patterns
 
-### 8. Handle Menu Selection
+### 9. Handle Menu Selection
 
 #### If 'A' (Advanced Elicitation):
 
@@ -219,9 +296,12 @@ When user selects 'C', append the content directly to the document using the str
 
 ## SUCCESS METRICS:
 
-✅ Design system coverage properly analyzed
+✅ **siesa-ui-kit checked FIRST** before any component decisions
+✅ Company standards loaded from `{company_standards_path}`
+✅ Design system coverage properly analyzed (siesa-ui-kit → shadcn → custom)
 ✅ All custom components thoroughly specified
-✅ Component strategy clearly defined
+✅ Component strategy clearly defined with priority hierarchy
+✅ **All UI text in Spanish** for user-facing elements
 ✅ Implementation roadmap prioritized by user need
 ✅ Accessibility considered for all components
 ✅ A/P/C menu presented and handled correctly
@@ -229,6 +309,10 @@ When user selects 'C', append the content directly to the document using the str
 
 ## FAILURE MODES:
 
+❌ **CRITICAL**: NOT checking siesa-ui-kit FIRST - creates components that already exist
+❌ **CRITICAL**: Creating custom components without asking user (shadcn vs siesa-ui-kit MR)
+❌ **CRITICAL**: UI text in English instead of Spanish
+❌ Not loading company standards from `{company_standards_path}`
 ❌ Not analyzing design system coverage properly
 ❌ Custom components not thoroughly specified
 ❌ Missing accessibility considerations

package/bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md

@@ -36,6 +36,22 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `installed_path` = `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design`
 - `template_path` = `{installed_path}/ux-design-template.md`
 - `default_output_file` = `{planning_artifacts}/ux-design-specification.md`
+- `company_standards_path` = `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards`
+
+### Company Standards Integration
+
+🔴 **CRITICAL**: Load company standards for UX specifications:
+
+If `{company_standards_path}` exists, load these files:
+- `frontend-standards.md` - Contains **siesa-ui-kit** rules and component strategy
+- `technical-preferences-ux.md` - UX/UI preferences and patterns
+
+**Priority Rules from Company Standards:**
+| Priority | Rule | Why Critical |
+|----------|------|--------------|
+| 🔴 P0 | **siesa-ui-kit obligatorio** | Must check siesa-ui-kit before creating ANY component |
+| 🔴 P0 | **UI text in Spanish** | All user-facing text MUST be in Spanish |
+| 🟡 P1 | Design system tokens | Use company-defined colors, spacing, typography |
 
 ## EXECUTION
 

package/bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards/architecture-patterns.md

@@ -120,7 +120,7 @@ Use MCP to install Shadcn components instead of creating manually.
 
 ### Technology Stack
 - **.NET 10** with **C# Minimal API**
-- **Entity Framework Core** with **PostgreSQL**
+- **Entity Framework Core** with **PostgreSQL 18+**
 - **UUID (Guid)** primary keys mandatory
 - **linq2db**, **DynamicLinq**, **LinqKit** for advanced queries
 - **FluentValidation** for validation
@@ -300,7 +300,7 @@ public class InventoryServiceClient
 ### Database per Microservice Pattern
 
 **Key Principles:**
-- Each microservice has its own PostgreSQL database
+- Each microservice has its own PostgreSQL database (v18+)
 - No direct database access between services
 - Data consistency via eventual consistency and sagas
 - Each database uses UUID (Guid) primary keys
@@ -359,7 +359,7 @@ public class QuoteConfiguration : IEntityTypeConfiguration<QuoteEntity>
 #### Test-Driven Development
 - Write xUnit tests before or alongside implementation
 - Use EF Core InMemory for fast unit tests
-- Use PostgreSQL Test Containers for integration tests
+- Use PostgreSQL 18+ Test Containers for integration tests
 - Mock external dependencies
 
 #### FluentValidation Usage
@@ -398,10 +398,10 @@ app.MapScalarApiReference();  // NOT app.UseSwagger()
 ### Backend
 - **Framework**: .NET 10 with C# Minimal API
 - **Architecture**: Clean Architecture + DDD + Microservices
-- **Database**: PostgreSQL (one per microservice)
+- **Database**: PostgreSQL 18+ (one per microservice)
 - **ORM**: Entity Framework Core + linq2db + DynamicLinq + LinqKit
 - **Validation**: FluentValidation
-- **Testing**: xUnit + EF Core InMemory + PostgreSQL Test Containers
+- **Testing**: xUnit + EF Core InMemory + PostgreSQL 18+ Test Containers
 - **Documentation**: Scalar (NO Swagger)
 - **Primary Keys**: UUID (Guid) mandatory
 - **PDF Generation**: QuestPDF

package/bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards/backend-standards.md

@@ -13,7 +13,7 @@
 
 ### Framework Standards
 - **Default Framework**: .NET 10 with C# Minimal API
-- **Database**: PostgreSQL with Entity Framework Core 10 (mandatory)
+- **Database**: PostgreSQL 18+ with Entity Framework Core 10 (mandatory)
 - **ORM Extensions**: 
   - **linq2db**: For highly optimized complex queries requiring maximum performance
   - **DynamicLinq**: For runtime dynamic filters from user input or configurable scenarios

package/bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards/technology-stack.md

@@ -176,7 +176,7 @@ Use MCP to install Shadcn components instead of creating manually
 - **REST API** - Primary communication protocol
 
 ### Database & Data Management
-- **PostgreSQL** - Primary relational database (mandatory)
+- **PostgreSQL 18+** - Primary relational database (mandatory)
 - **Database per Microservice** - Each microservice has its own isolated database
 - **Primary Keys UUID** - Universal unique identifiers for all entities
 - **EF Core 10 Migrations** - Entity Framework migrations package for schema version control
@@ -184,7 +184,7 @@ Use MCP to install Shadcn components instead of creating manually
 ### Testing
 - **xUnit** - Unit and integration testing framework
 - **EF Core 10 InMemory** - In-memory database for fast tests
-- **PostgreSQL Test Containers** - PostgreSQL containers for real integration tests
+- **PostgreSQL 18+ Test Containers** - PostgreSQL containers for real integration tests
 
 ### Additional Libraries
 - **QuestPDF** - PDF document generation
@@ -218,7 +218,7 @@ Business logic drives architecture decisions
 
 ### Microservices Isolation
 - Each service is independent
-- Own PostgreSQL database per service
+- Own PostgreSQL 18+ database per service
 - No shared databases between services
 
 ### UUID Primary Keys

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "siesa-agents",
-  "version": "2.1.41",
+  "version": "2.1.43",
   "description": "Paquete para instalar y configurar agentes SIESA en tu proyecto",
   "main": "index.js",
   "bin": {