siesa-agents 1.0.0 → 1.0.2

package/bin/prepare-publish.js

@@ -1,27 +1,27 @@
-#!/usr/bin/env node
-
-const fs = require('fs-extra');
-const path = require('path');
-
-const rootDir = path.dirname(__dirname);
-
-// Renombrar carpetas que empiezan con punto para que npm las incluya
-const folderMappings = [
-  { from: '.bmad-core', to: 'bmad-core' },
-  { from: '.vscode', to: 'vscode' },
-  { from: '.github', to: 'github' }
-];
-
-console.log('📦 Preparando carpetas para publicación...');
-
-for (const mapping of folderMappings) {
-  const fromPath = path.join(rootDir, mapping.from);
-  const toPath = path.join(rootDir, mapping.to);
-
-  if (fs.existsSync(fromPath)) {
-    console.log(`📁 Renombrando ${mapping.from} -> ${mapping.to}`);
-    fs.moveSync(fromPath, toPath);
-  }
-}
-
+#!/usr/bin/env node
+
+const fs = require('fs-extra');
+const path = require('path');
+
+const rootDir = path.dirname(__dirname);
+
+// Renombrar carpetas que empiezan con punto para que npm las incluya
+const folderMappings = [
+  { from: '.bmad-core', to: 'bmad-core' },
+  { from: '.vscode', to: 'vscode' },
+  { from: '.github', to: 'github' }
+];
+
+console.log('📦 Preparando carpetas para publicación (siesa-agents)...');
+
+for (const mapping of folderMappings) {
+  const fromPath = path.join(rootDir, mapping.from);
+  const toPath = path.join(rootDir, mapping.to);
+
+  if (fs.existsSync(fromPath)) {
+    console.log(`📁 Renombrando ${mapping.from} -> ${mapping.to}`);
+    fs.moveSync(fromPath, toPath);
+  }
+}
+
 console.log('✅ Carpetas preparadas para publicación');

package/bin/restore-folders.js

@@ -1,27 +1,27 @@
-#!/usr/bin/env node
-
-const fs = require('fs-extra');
-const path = require('path');
-
-const rootDir = path.dirname(__dirname);
-
-// Restaurar nombres originales de las carpetas
-const folderMappings = [
-  { from: 'bmad-core', to: '.bmad-core' },
-  { from: 'vscode', to: '.vscode' },
-  { from: 'github', to: '.github' }
-];
-
-console.log('🔄 Restaurando nombres originales de carpetas...');
-
-for (const mapping of folderMappings) {
-  const fromPath = path.join(rootDir, mapping.from);
-  const toPath = path.join(rootDir, mapping.to);
-
-  if (fs.existsSync(fromPath)) {
-    console.log(`📁 Restaurando ${mapping.from} -> ${mapping.to}`);
-    fs.moveSync(fromPath, toPath);
-  }
-}
-
+#!/usr/bin/env node
+
+const fs = require('fs-extra');
+const path = require('path');
+
+const rootDir = path.dirname(__dirname);
+
+// Restaurar nombres originales de las carpetas
+const folderMappings = [
+  { from: 'bmad-core', to: '.bmad-core' },
+  { from: 'vscode', to: '.vscode' },
+  { from: 'github', to: '.github' }
+];
+
+console.log('🔄 Restaurando nombres originales de carpetas...');
+
+for (const mapping of folderMappings) {
+  const fromPath = path.join(rootDir, mapping.from);
+  const toPath = path.join(rootDir, mapping.to);
+
+  if (fs.existsSync(fromPath)) {
+    console.log(`📁 Restaurando ${mapping.from} -> ${mapping.to}`);
+    fs.moveSync(fromPath, toPath);
+  }
+}
+
 console.log('✅ Carpetas restauradas');

package/bmad-core/checklists/frontend-checklist.md

@@ -1,106 +1,106 @@
-# Frontend Development Checklist
-
-## Architecture & Structure
-- [ ] Clean Architecture layers properly separated (domain, application, infrastructure, presentation)
-- [ ] Domain layer contains only business entities and rules
-- [ ] Application layer manages use cases and orchestration
-- [ ] Infrastructure layer handles external concerns (API, storage, etc.)
-- [ ] Presentation layer contains only UI components and pages
-- [ ] No circular dependencies between layers
-- [ ] Dependency inversion principle followed
-
-## TypeScript & Code Quality
-- [ ] Strict TypeScript configuration enabled
-- [ ] All components have proper type definitions
-- [ ] No usage of `any` type
-- [ ] Props interfaces properly defined
-- [ ] Custom hooks have proper typing
-- [ ] API responses are properly typed
-- [ ] State management stores have type safety
-
-## Component Standards
-- [ ] Components follow single responsibility principle
-- [ ] Proper use of React.memo for performance
-- [ ] Components are composable and reusable
-- [ ] Props are properly documented with JSDoc
-- [ ] Default props are defined where appropriate
-- [ ] Components handle loading and error states
-
-## State Management
-- [ ] Zustand stores follow DDD patterns
-- [ ] Global vs local state properly separated
-- [ ] Actions call use cases from application layer
-- [ ] State updates are immutable
-- [ ] Store subscriptions are optimized
-
-## Styling & UI
-- [ ] TailwindCSS used consistently
-- [ ] Shadcn/ui components properly configured
-- [ ] Responsive design implemented
-- [ ] Design system patterns followed
-- [ ] Color scheme and theme support
-- [ ] Loading states have proper UI feedback
-
-## Performance
-- [ ] Components are lazily loaded where appropriate
-- [ ] Images are optimized and properly sized
-- [ ] Bundle size is within acceptable limits
-- [ ] React.memo used strategically
-- [ ] Expensive operations are memoized
-- [ ] Infinite scrolls or virtual lists for large datasets
-
-## Accessibility
-- [ ] ARIA labels and roles properly implemented
-- [ ] Keyboard navigation works correctly
-- [ ] Color contrast meets WCAG 2.1 AA standards
-- [ ] Screen reader compatibility tested
-- [ ] Focus management implemented
-- [ ] Form validation errors are accessible
-
-## Testing
-- [ ] Unit tests for all custom hooks
-- [ ] Component tests cover user interactions
-- [ ] Integration tests for feature workflows
-- [ ] Accessibility tests using jest-axe
-- [ ] Test coverage meets minimum threshold (80%)
-- [ ] Edge cases and error scenarios tested
-
-## API Integration
-- [ ] HTTP client properly configured
-- [ ] Error handling for network failures
-- [ ] Request/response interceptors for auth
-- [ ] API types match backend specifications
-- [ ] Loading states during API calls
-- [ ] Proper error messages displayed to users
-
-## PWA Features (if enabled)
-- [ ] Service worker configured correctly
-- [ ] Offline functionality works
-- [ ] App manifest is valid
-- [ ] Cache strategies implemented
-- [ ] App can be installed on devices
-- [ ] Push notifications work (if required)
-
-## Security
-- [ ] No secrets or API keys in frontend code
-- [ ] XSS prevention measures implemented
-- [ ] CSRF protection where needed
-- [ ] Secure authentication flow
-- [ ] Input validation and sanitization
-- [ ] Safe handling of user data
-
-## Development Experience
-- [ ] Hot reloading works correctly
-- [ ] TypeScript compilation is fast
-- [ ] Linting rules are enforced
-- [ ] Code formatting is consistent
-- [ ] Development tools are configured
-- [ ] Environment-specific configurations work
-
-## Documentation
-- [ ] README with setup instructions
-- [ ] Component documentation exists
-- [ ] API integration documented
-- [ ] Deployment guide available
-- [ ] Architecture decisions recorded
+# Frontend Development Checklist
+
+## Architecture & Structure
+- [ ] Clean Architecture layers properly separated (domain, application, infrastructure, presentation)
+- [ ] Domain layer contains only business entities and rules
+- [ ] Application layer manages use cases and orchestration
+- [ ] Infrastructure layer handles external concerns (API, storage, etc.)
+- [ ] Presentation layer contains only UI components and pages
+- [ ] No circular dependencies between layers
+- [ ] Dependency inversion principle followed
+
+## TypeScript & Code Quality
+- [ ] Strict TypeScript configuration enabled
+- [ ] All components have proper type definitions
+- [ ] No usage of `any` type
+- [ ] Props interfaces properly defined
+- [ ] Custom hooks have proper typing
+- [ ] API responses are properly typed
+- [ ] State management stores have type safety
+
+## Component Standards
+- [ ] Components follow single responsibility principle
+- [ ] Proper use of React.memo for performance
+- [ ] Components are composable and reusable
+- [ ] Props are properly documented with JSDoc
+- [ ] Default props are defined where appropriate
+- [ ] Components handle loading and error states
+
+## State Management
+- [ ] Zustand stores follow DDD patterns
+- [ ] Global vs local state properly separated
+- [ ] Actions call use cases from application layer
+- [ ] State updates are immutable
+- [ ] Store subscriptions are optimized
+
+## Styling & UI
+- [ ] TailwindCSS used consistently
+- [ ] Shadcn/ui components properly configured
+- [ ] Responsive design implemented
+- [ ] Design system patterns followed
+- [ ] Color scheme and theme support
+- [ ] Loading states have proper UI feedback
+
+## Performance
+- [ ] Components are lazily loaded where appropriate
+- [ ] Images are optimized and properly sized
+- [ ] Bundle size is within acceptable limits
+- [ ] React.memo used strategically
+- [ ] Expensive operations are memoized
+- [ ] Infinite scrolls or virtual lists for large datasets
+
+## Accessibility
+- [ ] ARIA labels and roles properly implemented
+- [ ] Keyboard navigation works correctly
+- [ ] Color contrast meets WCAG 2.1 AA standards
+- [ ] Screen reader compatibility tested
+- [ ] Focus management implemented
+- [ ] Form validation errors are accessible
+
+## Testing
+- [ ] Unit tests for all custom hooks
+- [ ] Component tests cover user interactions
+- [ ] Integration tests for feature workflows
+- [ ] Accessibility tests using jest-axe
+- [ ] Test coverage meets minimum threshold (80%)
+- [ ] Edge cases and error scenarios tested
+
+## API Integration
+- [ ] HTTP client properly configured
+- [ ] Error handling for network failures
+- [ ] Request/response interceptors for auth
+- [ ] API types match backend specifications
+- [ ] Loading states during API calls
+- [ ] Proper error messages displayed to users
+
+## PWA Features (if enabled)
+- [ ] Service worker configured correctly
+- [ ] Offline functionality works
+- [ ] App manifest is valid
+- [ ] Cache strategies implemented
+- [ ] App can be installed on devices
+- [ ] Push notifications work (if required)
+
+## Security
+- [ ] No secrets or API keys in frontend code
+- [ ] XSS prevention measures implemented
+- [ ] CSRF protection where needed
+- [ ] Secure authentication flow
+- [ ] Input validation and sanitization
+- [ ] Safe handling of user data
+
+## Development Experience
+- [ ] Hot reloading works correctly
+- [ ] TypeScript compilation is fast
+- [ ] Linting rules are enforced
+- [ ] Code formatting is consistent
+- [ ] Development tools are configured
+- [ ] Environment-specific configurations work
+
+## Documentation
+- [ ] README with setup instructions
+- [ ] Component documentation exists
+- [ ] API integration documented
+- [ ] Deployment guide available
+- [ ] Architecture decisions recorded
 - [ ] Troubleshooting guide provided

package/bmad-core/tasks/create-component.md

@@ -1,103 +1,103 @@
-# Create UI Component
-
-## Purpose
-Create a React component with TypeScript, accessibility features, and comprehensive tests.
-
-## Task Configuration
-```yaml
-elicit: true
-interactive: true
-required_params:
-  - component_name
-  - feature
-  - component_type
-optional_params:
-  - props
-  - accessibility_level
-```
-
-## Task Execution
-
-### Step 1: Elicit Component Requirements
-Ask user for:
-
-**Component Name**: What should the component be called? (use PascalCase)
-**Feature**: Which feature does this component belong to?
-**Component Type**: What type of component is this?
-- page: Full page component with routing
-- container: Logic container that manages state
-- presentation: Pure presentation component
-- form: Form component with validation
-- layout: Layout wrapper component
-
-**Props**: What props should this component accept? (optional)
-**Accessibility Level**: What accessibility level is needed?
-- basic: Basic ARIA labels and keyboard support
-- enhanced: Enhanced navigation and screen reader support
-- wcag-aa: Full WCAG 2.1 AA compliance
-
-### Step 2: Generate Component File
-Create component with:
-- TypeScript interface for props
-- Proper React.memo for performance
-- Forward refs if needed
-- Default props and prop validation
-
-### Step 3: Implement Accessibility Features
-Based on accessibility level:
-- Add proper ARIA attributes
-- Implement keyboard navigation
-- Ensure proper color contrast
-- Add screen reader support
-- Include focus management
-
-### Step 4: Add Styling
-- Use TailwindCSS for styling
-- Follow design system patterns
-- Implement responsive design
-- Add hover/focus states
-- Support theme variations
-
-### Step 5: Generate Tests
-Create comprehensive test suite:
-- Unit tests for component behavior
-- Accessibility tests (using jest-axe)
-- User interaction tests
-- Visual regression tests if needed
-- Performance tests for complex components
-
-### Step 6: Generate Documentation
-- Add JSDoc comments
-- Create Storybook stories if configured
-- Document props and usage examples
-- Add accessibility notes
-
-## Component Template Structure
-```typescript
-interface {ComponentName}Props {
-  // Props definition with proper typing
-  className?: string;
-  'data-testid'?: string;
-}
-
-export const {ComponentName} = memo<{ComponentName}Props>(({
-  className,
-  'data-testid': testId = '{component-name}'
-}) => {
-  // Component implementation
-  return (
-    <div className={cn('component-base-styles', className)} data-testid={testId}>
-      {/* Component content */}
-    </div>
-  );
-});
-
-{ComponentName}.displayName = '{ComponentName}';
-```
-
-## Completion Criteria
-- Component follows TypeScript best practices
-- Accessibility requirements met
-- Comprehensive test coverage
-- Proper styling and responsive design
+# Create UI Component
+
+## Purpose
+Create a React component with TypeScript, accessibility features, and comprehensive tests.
+
+## Task Configuration
+```yaml
+elicit: true
+interactive: true
+required_params:
+  - component_name
+  - feature
+  - component_type
+optional_params:
+  - props
+  - accessibility_level
+```
+
+## Task Execution
+
+### Step 1: Elicit Component Requirements
+Ask user for:
+
+**Component Name**: What should the component be called? (use PascalCase)
+**Feature**: Which feature does this component belong to?
+**Component Type**: What type of component is this?
+- page: Full page component with routing
+- container: Logic container that manages state
+- presentation: Pure presentation component
+- form: Form component with validation
+- layout: Layout wrapper component
+
+**Props**: What props should this component accept? (optional)
+**Accessibility Level**: What accessibility level is needed?
+- basic: Basic ARIA labels and keyboard support
+- enhanced: Enhanced navigation and screen reader support
+- wcag-aa: Full WCAG 2.1 AA compliance
+
+### Step 2: Generate Component File
+Create component with:
+- TypeScript interface for props
+- Proper React.memo for performance
+- Forward refs if needed
+- Default props and prop validation
+
+### Step 3: Implement Accessibility Features
+Based on accessibility level:
+- Add proper ARIA attributes
+- Implement keyboard navigation
+- Ensure proper color contrast
+- Add screen reader support
+- Include focus management
+
+### Step 4: Add Styling
+- Use TailwindCSS for styling
+- Follow design system patterns
+- Implement responsive design
+- Add hover/focus states
+- Support theme variations
+
+### Step 5: Generate Tests
+Create comprehensive test suite:
+- Unit tests for component behavior
+- Accessibility tests (using jest-axe)
+- User interaction tests
+- Visual regression tests if needed
+- Performance tests for complex components
+
+### Step 6: Generate Documentation
+- Add JSDoc comments
+- Create Storybook stories if configured
+- Document props and usage examples
+- Add accessibility notes
+
+## Component Template Structure
+```typescript
+interface {ComponentName}Props {
+  // Props definition with proper typing
+  className?: string;
+  'data-testid'?: string;
+}
+
+export const {ComponentName} = memo<{ComponentName}Props>(({
+  className,
+  'data-testid': testId = '{component-name}'
+}) => {
+  // Component implementation
+  return (
+    <div className={cn('component-base-styles', className)} data-testid={testId}>
+      {/* Component content */}
+    </div>
+  );
+});
+
+{ComponentName}.displayName = '{ComponentName}';
+```
+
+## Completion Criteria
+- Component follows TypeScript best practices
+- Accessibility requirements met
+- Comprehensive test coverage
+- Proper styling and responsive design
 - Documentation complete

package/bmad-core/tasks/create-feature.md

@@ -1,91 +1,91 @@
-# Create Frontend Feature
-
-## Purpose
-Create a complete feature following Clean Architecture + DDD principles with all necessary layers.
-
-## Task Configuration
-```yaml
-elicit: true
-interactive: true
-required_params:
-  - feature_name
-  - entities
-  - use_cases
-optional_params:
-  - api_endpoints
-  - ui_components
-```
-
-## Task Execution
-
-### Step 1: Elicit Feature Requirements
-Ask user for:
-
-**Feature Name**: What is the name of the feature? (use kebab-case)
-**Domain Entities**: What are the main business entities for this feature?
-**Use Cases**: What are the main use cases/operations users can perform?
-**API Endpoints**: What backend endpoints will this feature consume? (optional)
-**UI Components**: Any specific components you know you'll need? (optional)
-
-### Step 2: Create Feature Structure
-Generate the following structure:
-
-```
-src/features/{feature_name}/
-├── domain/
-│   ├── entities/
-│   ├── repositories/
-│   ├── services/
-│   └── types/
-├── application/
-│   ├── use-cases/
-│   ├── hooks/
-│   └── store/
-├── infrastructure/
-│   ├── repositories/
-│   ├── api/
-│   └── adapters/
-└── presentation/
-    ├── components/
-    ├── pages/
-    └── styles/
-```
-
-### Step 3: Generate Domain Layer
-For each entity:
-- Create TypeScript interfaces/types
-- Define value objects if needed
-- Create repository interfaces
-- Define domain services if complex business rules exist
-
-### Step 4: Generate Application Layer
-For each use case:
-- Create use case implementation
-- Create custom hooks that consume use cases
-- Setup Zustand store for feature state
-- Implement error handling and loading states
-
-### Step 5: Generate Infrastructure Layer
-- Implement repository concrete classes
-- Setup API clients with proper typing
-- Create adapters for external services
-- Configure error handling and retries
-
-### Step 6: Generate Presentation Layer
-- Create feature-specific components
-- Setup routing for feature pages
-- Implement accessibility features
-- Add loading and error states
-
-### Step 7: Generate Tests
-- Unit tests for domain entities and services
-- Integration tests for use cases
-- Component tests for presentation layer
-- API integration tests for infrastructure layer
-
-## Completion Criteria
-- All layers properly implemented
-- Clean Architecture dependencies respected
-- TypeScript compilation successful
-- All tests passing
+# Create Frontend Feature
+
+## Purpose
+Create a complete feature following Clean Architecture + DDD principles with all necessary layers.
+
+## Task Configuration
+```yaml
+elicit: true
+interactive: true
+required_params:
+  - feature_name
+  - entities
+  - use_cases
+optional_params:
+  - api_endpoints
+  - ui_components
+```
+
+## Task Execution
+
+### Step 1: Elicit Feature Requirements
+Ask user for:
+
+**Feature Name**: What is the name of the feature? (use kebab-case)
+**Domain Entities**: What are the main business entities for this feature?
+**Use Cases**: What are the main use cases/operations users can perform?
+**API Endpoints**: What backend endpoints will this feature consume? (optional)
+**UI Components**: Any specific components you know you'll need? (optional)
+
+### Step 2: Create Feature Structure
+Generate the following structure:
+
+```
+src/features/{feature_name}/
+├── domain/
+│   ├── entities/
+│   ├── repositories/
+│   ├── services/
+│   └── types/
+├── application/
+│   ├── use-cases/
+│   ├── hooks/
+│   └── store/
+├── infrastructure/
+│   ├── repositories/
+│   ├── api/
+│   └── adapters/
+└── presentation/
+    ├── components/
+    ├── pages/
+    └── styles/
+```
+
+### Step 3: Generate Domain Layer
+For each entity:
+- Create TypeScript interfaces/types
+- Define value objects if needed
+- Create repository interfaces
+- Define domain services if complex business rules exist
+
+### Step 4: Generate Application Layer
+For each use case:
+- Create use case implementation
+- Create custom hooks that consume use cases
+- Setup Zustand store for feature state
+- Implement error handling and loading states
+
+### Step 5: Generate Infrastructure Layer
+- Implement repository concrete classes
+- Setup API clients with proper typing
+- Create adapters for external services
+- Configure error handling and retries
+
+### Step 6: Generate Presentation Layer
+- Create feature-specific components
+- Setup routing for feature pages
+- Implement accessibility features
+- Add loading and error states
+
+### Step 7: Generate Tests
+- Unit tests for domain entities and services
+- Integration tests for use cases
+- Component tests for presentation layer
+- API integration tests for infrastructure layer
+
+## Completion Criteria
+- All layers properly implemented
+- Clean Architecture dependencies respected
+- TypeScript compilation successful
+- All tests passing
 - Feature integrated with main application

package/index.js

@@ -2,7 +2,6 @@
 
 const SiesaBmadInstaller = require('./bin/install.js');
 
-// Si el módulo es ejecutado directamente (npx siesa-bmad-agents)
 if (require.main === module) {
   const installer = new SiesaBmadInstaller();
   installer.install();

package/package.json

@@ -1,41 +1,38 @@
-{
-  "name": "siesa-agents",
-  "version": "1.0.0",
-  "description": "Paquete para instalar y configurar agentes SIESA BMAD en tu proyecto",
-  "main": "index.js",
-  "bin": {
-    "siesa-agents": "./bin/install.js"
-  },
-  "scripts": {
-    "postinstall": "node ./bin/install.js",
-    "prepublishOnly": "node ./bin/prepare-publish.js",
-    "postpublish": "node ./bin/restore-folders.js",
-    "build": "echo 'Build complete'"
-  },
-  "keywords": [
-    "siesa",
-    "bmad",
-    "agents",
-    "automation",
-    "cli"
-  ],
-  "author": "Sistemas de Información Empresarial",
-  "license": "MIT",
-  "files": [
-    "bmad-core/**/*",
-    "vscode/**/*",
-    "github/**/*",
-    "bin/**/*",
-    "README.md"
-  ],
-  "engines": {
-    "node": ">=14.0.0"
-  },
-  "dependencies": {
-    "fs-extra": "^11.1.1",
-    "path": "^0.12.7"
-  },
-  "devDependencies": {
-    "shadcn": "^3.3.1"
-  }
-}
+{
+  "name": "siesa-agents",
+  "version": "1.0.2",
+  "description": "Paquete para instalar y configurar agentes SIESA BMAD en tu proyecto",
+  "main": "index.js",
+  "bin": {
+    "siesa-agents": "./bin/install.js"
+  },
+  "scripts": {
+    "postinstall": "node ./bin/install.js",
+    "prepublishOnly": "node ./bin/prepare-publish.js",
+    "postpublish": "node ./bin/restore-folders.js",
+    "build": "echo 'Build complete'"
+  },
+  "keywords": [
+    "siesa",
+    "bmad",
+    "agents",
+    "automation",
+    "cli"
+  ],
+  "author": "Sistemas de Información Empresarial",
+  "license": "MIT",
+  "files": [
+    "bmad-core/**/*",
+    "vscode/**/*",
+    "github/**/*",
+    "bin/**/*",
+    "README.md"
+  ],
+  "engines": {
+    "node": ">=14.0.0"
+  },
+  "dependencies": {
+    "fs-extra": "^11.1.1",
+    "path": "^0.12.7"
+  }
+}

package/vscode/mcp.json

@@ -1,11 +1,11 @@
-{
-  "servers": {
-    "shadcn": {
-      "command": "npx",
-      "args": [
-        "shadcn@latest",
-        "mcp"
-      ]
-    }
-  }
-}
+{
+  "servers": {
+    "shadcn": {
+      "command": "npx",
+      "args": [
+        "shadcn@latest",
+        "mcp"
+      ]
+    }
+  }
+}