siesa-agents 2.1.51 → 2.1.52
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.
- package/bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards/technical-preferences-ux.md +2 -2
- package/bmad/bmm/workflows/3-solutioning/create-architecture/data/project-types.csv +1 -1
- package/bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md +3 -3
- package/bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md +15 -13
- package/bmad/bmm/workflows/generate-project-context/steps/step-01-discover.md +1 -1
- package/bmad/bmm/workflows/generate-project-context/steps/step-02-generate.md +1 -1
- package/bmad/bmm/workflows/testarch/framework/checklist.md +1 -1
- package/bmad/bmm/workflows/testarch/framework/instructions.md +1 -1
- package/package.json +1 -1
|
@@ -4,10 +4,10 @@
|
|
|
4
4
|
Based on Frontend Development Standards and Clean Architecture Implementation
|
|
5
5
|
|
|
6
6
|
### Technology Stack
|
|
7
|
-
- **Framework**:
|
|
7
|
+
- **Framework**: Vite 6+ with TanStack Router
|
|
8
8
|
- **Language**: TypeScript (strict mode)
|
|
9
9
|
- **Styling**: TailwindCSS + Shadcn/ui + Radix UI
|
|
10
|
-
- **State Management**: Zustand
|
|
10
|
+
- **State Management**: Zustand + TanStack Query
|
|
11
11
|
- **Testing**: Vitest + React Testing Library
|
|
12
12
|
- **Architecture**: Clean Architecture with DDD patterns
|
|
13
13
|
- **Loading States**: React Loading Skeleton (for placeholders/preloading)
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
project_type,detection_signals,description,typical_starters
|
|
2
|
-
web_app,"website,web application,browser,frontend,UI,interface",Web-based applications running in browsers,
|
|
2
|
+
web_app,"website,web application,browser,frontend,UI,interface",Web-based applications running in browsers,Vite, Remix
|
|
3
3
|
mobile_app,"mobile,iOS,Android,app,smartphone,tablet",Native mobile applications,React Native, Expo, Flutter
|
|
4
4
|
api_backend,"API,REST,GraphQL,backend,service,microservice",Backend services and APIs,NestJS, Express, Fastify
|
|
5
5
|
full_stack,"full-stack,complete,web+mobile,frontend+backend",Applications with both frontend and backend,T3 App, RedwoodJS, Blitz
|
|
@@ -87,7 +87,7 @@ No existing technical preferences found in project context file. We'll establish
|
|
|
87
87
|
{{primary_technology_category}} Preferences:
|
|
88
88
|
|
|
89
89
|
- **Languages**: Do you have preferences between TypeScript/JavaScript, Python, Go, Rust, etc.?
|
|
90
|
-
- **Frameworks**: Any existing familiarity or preferences (React, Vue, Angular,
|
|
90
|
+
- **Frameworks**: Any existing familiarity or preferences (React, Vue, Angular, Vite, etc.)?
|
|
91
91
|
- **Databases**: Any preferences or existing infrastructure (PostgreSQL, MongoDB, MySQL, etc.)?
|
|
92
92
|
|
|
93
93
|
**Development Experience:**
|
|
@@ -111,11 +111,11 @@ These preferences will help me recommend the most suitable starter templates and
|
|
|
111
111
|
|
|
112
112
|
Based on project context analysis and technical preferences, identify the primary technology stack:
|
|
113
113
|
|
|
114
|
-
- **Web application** → Look for
|
|
114
|
+
- **Web application** → Look for Vite, Remix, SvelteKit starters
|
|
115
115
|
- **Mobile app** → Look for React Native, Expo, Flutter starters
|
|
116
116
|
- **API/Backend** → Look for NestJS, Express, Fastify, Supabase starters
|
|
117
117
|
- **CLI tool** → Look for CLI framework starters (oclif, commander, etc.)
|
|
118
|
-
- **Full-stack** → Look for T3, RedwoodJS, Blitz
|
|
118
|
+
- **Full-stack** → Look for T3, RedwoodJS, Blitz starters
|
|
119
119
|
- **Desktop** → Look for Electron, Tauri starters
|
|
120
120
|
|
|
121
121
|
### 2. UX Requirements Consideration
|
|
@@ -133,39 +133,41 @@ Generate a comprehensive directory structure showing all files and directories:
|
|
|
133
133
|
|
|
134
134
|
**Technology-Specific Structure Examples:**
|
|
135
135
|
|
|
136
|
-
**
|
|
136
|
+
**Vite + TanStack Full-Stack:**
|
|
137
137
|
|
|
138
138
|
```
|
|
139
139
|
project-name/
|
|
140
140
|
├── README.md
|
|
141
141
|
├── package.json
|
|
142
|
-
├──
|
|
142
|
+
├── vite.config.ts
|
|
143
143
|
├── tailwind.config.js
|
|
144
144
|
├── tsconfig.json
|
|
145
|
-
├── .env
|
|
145
|
+
├── .env
|
|
146
146
|
├── .env.example
|
|
147
147
|
├── .gitignore
|
|
148
148
|
├── .github/
|
|
149
149
|
│ └── workflows/
|
|
150
150
|
│ └── ci.yml
|
|
151
151
|
├── src/
|
|
152
|
-
│ ├──
|
|
153
|
-
│
|
|
154
|
-
│
|
|
155
|
-
│
|
|
152
|
+
│ ├── main.tsx
|
|
153
|
+
│ ├── App.tsx
|
|
154
|
+
│ ├── index.css
|
|
155
|
+
│ ├── assets/
|
|
156
156
|
│ ├── components/
|
|
157
157
|
│ │ ├── ui/
|
|
158
158
|
│ │ ├── forms/
|
|
159
159
|
│ │ └── features/
|
|
160
|
+
│ ├── hooks/
|
|
160
161
|
│ ├── lib/
|
|
161
|
-
│ │ ├──
|
|
162
|
+
│ │ ├── query-client.ts
|
|
162
163
|
│ │ ├── auth.ts
|
|
163
164
|
│ │ └── utils.ts
|
|
164
|
-
│ ├──
|
|
165
|
-
│
|
|
166
|
-
├──
|
|
167
|
-
│
|
|
168
|
-
│
|
|
165
|
+
│ ├── routes/
|
|
166
|
+
│ │ ├── __root.tsx
|
|
167
|
+
│ │ ├── index.tsx
|
|
168
|
+
│ │ └── ...
|
|
169
|
+
│ ├── stores/
|
|
170
|
+
│ └── types/
|
|
169
171
|
├── tests/
|
|
170
172
|
│ ├── __mocks__/
|
|
171
173
|
│ ├── components/
|
|
@@ -79,7 +79,7 @@ When loading company standards, specifically look for and highlight:
|
|
|
79
79
|
- 🔴 **siesa-ui-kit requirement** - Must check siesa-ui-kit before creating components
|
|
80
80
|
- 🔴 **Spanish UI text** - All user-facing text must be in Spanish
|
|
81
81
|
- 🔴 **DateTimeOffset** - Use DateTimeOffset not DateTime for PostgreSQL
|
|
82
|
-
- Technology stack versions (.NET 10,
|
|
82
|
+
- Technology stack versions (.NET 10, Vite 6+, etc.)
|
|
83
83
|
|
|
84
84
|
Report: "✅ Estándares corporativos cargados: {count} archivos con {rules_count} reglas críticas"
|
|
85
85
|
|
|
@@ -125,7 +125,7 @@ Document framework-specific patterns:
|
|
|
125
125
|
Should I add any other React-specific rules?"
|
|
126
126
|
|
|
127
127
|
**Other Framework Rules:**
|
|
128
|
-
Adapt for Vue, Angular,
|
|
128
|
+
Adapt for Vue, Angular, Vite, Express, etc.
|
|
129
129
|
|
|
130
130
|
### 4. Testing Rules
|
|
131
131
|
|
|
@@ -10,7 +10,7 @@ Before starting the workflow:
|
|
|
10
10
|
|
|
11
11
|
- [ ] Project root contains valid `package.json`
|
|
12
12
|
- [ ] No existing modern E2E framework detected (`playwright.config.*`, `cypress.config.*`)
|
|
13
|
-
- [ ] Project type identifiable (React, Vue, Angular,
|
|
13
|
+
- [ ] Project type identifiable (React, Vue, Angular, Vite, Node, etc.)
|
|
14
14
|
- [ ] Bundler identifiable (Vite, Webpack, Rollup, esbuild) or not applicable
|
|
15
15
|
- [ ] User has write permissions to create directories and files
|
|
16
16
|
|
|
@@ -29,7 +29,7 @@ Initialize a production-ready test framework architecture (Playwright or Cypress
|
|
|
29
29
|
|
|
30
30
|
1. **Validate package.json**
|
|
31
31
|
- Read `{project-root}/package.json`
|
|
32
|
-
- Extract project type (React, Vue, Angular,
|
|
32
|
+
- Extract project type (React, Vue, Angular, Vite, Node, etc.)
|
|
33
33
|
- Identify bundler (Vite, Webpack, Rollup, esbuild)
|
|
34
34
|
- Note existing test dependencies
|
|
35
35
|
|