siesa-agents 2.1.23 → 2.1.24

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -29,6 +29,7 @@ activation-instructions:
29
29
  - 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.
30
30
  - 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
31
31
  - STAY IN CHARACTER!
32
+ - CRITICAL: ALWAYS load bmad-core/data/frontend-standards.md first (contains language standards for all user-facing content)
32
33
  - CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - .bmad-core/core-config.yaml devLoadAlwaysFiles list
33
34
  - CRITICAL: Do NOT load any other files during startup aside from the assigned story and devLoadAlwaysFiles items, unless user requested you do or the following contradicts
34
35
  - CRITICAL: Do NOT begin development until a story is not in draft mode and you are told to proceed
@@ -52,6 +53,7 @@ core_principles:
52
53
  - CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
53
54
  - CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
54
55
  - CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
56
+ - CRITICAL: ALL user-facing text MUST be in Spanish. Code MUST be in English. See bmad-core/data/frontend-standards.md for complete guidelines.
55
57
  - Numbered Options - Always use numbered lists when presenting choices to the user
56
58
 
57
59
  # All commands require * prefix when used (e.g., *help)
@@ -37,6 +37,7 @@ The goal is quality delivery, not just checking boxes.]]
37
37
  - [ ] All new/modified code aligns with `Project Structure` (file locations, naming, etc.).
38
38
  - [ ] Adherence to `Tech Stack` for technologies/versions used (if story introduces or modifies tech usage).
39
39
  - [ ] Adherence to `Api Reference` and `Data Models` (if story involves API or data model changes).
40
+ - [ ] **CRITICAL: All user-facing text (UI labels, buttons, error messages, validations, notifications, etc.) is in Spanish. Code (variables, functions, classes, comments) is in English. No mixed-language text in UI.**
40
41
  - [ ] Basic security best practices (e.g., input validation, proper error handling, no hardcoded secrets) applied for new/modified code.
41
42
  - [ ] No new linter errors or warnings introduced.
42
43
  - [ ] Code is well-commented where necessary (clarifying complex logic, not obvious statements).
@@ -335,4 +335,40 @@ import { Button } from '@/components/ui/button';
335
335
  - Cache-first for static assets
336
336
  - Network-first for dynamic data
337
337
  - Fallback pages for offline scenarios
338
- - Sync when connection restored
338
+ - Sync when connection restored
339
+
340
+ ## Language Standards (Frontend & Backend)
341
+
342
+ ### Spanish for All User-Facing Content (CRITICAL RULE)
343
+
344
+ **MANDATORY: All text visible to end users MUST be in Spanish.**
345
+
346
+ #### ✅ Spanish Required:
347
+ - UI labels, buttons, forms, messages, notifications
348
+ - API responses, validation errors, email templates
349
+ - Any text the user sees (frontend or backend)
350
+
351
+ #### ✅ English Required:
352
+ - Code (variables, functions, classes)
353
+ - Technical logs, comments, git commits
354
+ - Developer documentation
355
+
356
+ #### ❌ Never mix languages in user-facing text
357
+
358
+ **Examples:**
359
+ ```typescript
360
+ // ✅ CORRECT
361
+ <Button>Guardar</Button>
362
+ toast.success("Datos guardados correctamente");
363
+ throw new BadRequestException('No se pudo crear el usuario');
364
+
365
+ // ❌ INCORRECT
366
+ <Button>Save cambios</Button>
367
+ toast.error("Failed al guardar");
368
+ throw new BadRequestException('Invalid datos proporcionados');
369
+ ```
370
+
371
+ **Implementation:**
372
+ - Create message constants in Spanish
373
+ - Validate all user-facing text before story completion
374
+ - Technical logs stay in English, user messages in Spanish
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "siesa-agents",
3
- "version": "2.1.23",
3
+ "version": "2.1.24",
4
4
  "description": "Paquete para instalar y configurar agentes SIESA en tu proyecto",
5
5
  "main": "index.js",
6
6
  "bin": {