claude-autopm 1.20.0 → 1.21.0
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/README.md +255 -878
- package/autopm/.claude/agents/README.md +1 -1
- package/autopm/.claude/agents/decision-matrices/python-backend-selection.md +25 -25
- package/autopm/.claude/agents/decision-matrices/ui-framework-selection.md +43 -43
- package/autopm/.claude/agents/devops/github-operations-specialist.md +1 -1
- package/autopm/.claude/agents/frameworks/README.md +5 -5
- package/autopm/.claude/agents/frameworks/e2e-test-engineer.md +1 -1
- package/autopm/.claude/agents/frameworks/nats-messaging-expert.md +1 -1
- package/autopm/.claude/agents/frameworks/react-frontend-engineer.md +1 -1
- package/autopm/.claude/agents/frameworks/react-ui-expert.md +3 -3
- package/autopm/.claude/agents/frameworks/tailwindcss-expert.md +3 -3
- package/autopm/.claude/agents/frameworks/ux-design-expert.md +3 -3
- package/autopm/.claude/commands/infrastructure/traefik-setup.md +1 -1
- package/autopm/.claude/commands/playwright/test-scaffold.md +1 -1
- package/autopm/.claude/commands/pm/epic-sync.md +37 -4
- package/autopm/.claude/commands/ui/bootstrap-scaffold.md +6 -5
- package/autopm/.claude/commands/ui/tailwind-system.md +1 -1
- package/autopm/.claude/examples/mcp/playwright-mcp.md +2 -2
- package/autopm/.claude/examples/mcp-servers.example.json +2 -2
- package/autopm/.claude/hooks/docker-first-enforcement.sh +1 -1
- package/autopm/.claude/mcp/playwright-mcp.md +2 -2
- package/autopm/.claude/rules/agent-coordination.md +26 -24
- package/autopm/.claude/rules/docker-first-development.md +1 -1
- package/autopm/.claude/rules/framework-path-rules.md +180 -0
- package/autopm/.claude/rules/infrastructure-pipeline.md +1 -1
- package/autopm/.claude/rules/ui-development-standards.md +1 -1
- package/autopm/.claude/rules/visual-testing.md +3 -3
- package/autopm/.claude/scripts/pm/epic-sync/README.md +208 -0
- package/autopm/.claude/scripts/pm/epic-sync/create-epic-issue.sh +68 -192
- package/autopm/.claude/scripts/pm/epic-sync/create-task-issues.sh +60 -328
- package/autopm/.claude/scripts/pm/epic-sync/update-epic-file.sh +61 -354
- package/autopm/.claude/scripts/pm/epic-sync/update-references.sh +67 -305
- package/autopm/.claude/scripts/pm/epic-sync.sh +137 -0
- package/autopm/.claude/teams.json +3 -5
- package/autopm/.claude/templates/claude-templates/addons/devops-agents.md +2 -2
- package/autopm/.claude/templates/claude-templates/addons/docker-agents.md +4 -4
- package/autopm/.claude/templates/claude-templates/addons/minimal-agents.md +1 -1
- package/autopm/.claude/templates/issue-decomposition/api.yaml +2 -2
- package/autopm/.claude/templates/issue-decomposition/auth.yaml +4 -4
- package/autopm/.claude/templates/issue-decomposition/crud.yaml +3 -3
- package/autopm/.claude/templates/issue-decomposition/default.yaml +1 -1
- package/autopm/.claude/templates/issue-decomposition/ui-feature.yaml +2 -2
- package/package.json +4 -3
- package/scripts/validate-framework-paths.sh +104 -0
|
@@ -57,7 +57,7 @@ Language-specific development:
|
|
|
57
57
|
Framework specialists:
|
|
58
58
|
|
|
59
59
|
- `react-frontend-engineer` - React/Next.js expert
|
|
60
|
-
- `
|
|
60
|
+
- `frontend-testing-engineer` - E2E testing expert
|
|
61
61
|
- *Planned: angular, vue, django, spring, express*
|
|
62
62
|
|
|
63
63
|
### Cloud (4 agents, 5+ planned)
|
|
@@ -1,8 +1,8 @@
|
|
|
1
|
-
# Python Backend
|
|
1
|
+
# Python Backend Framework Selection Guide
|
|
2
2
|
|
|
3
3
|
## Quick Selection Guide
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
The `python-backend-engineer` agent supports both **FastAPI** and **Flask** frameworks. Use this guide to choose the right framework for your project:
|
|
6
6
|
|
|
7
7
|
| Requirement | FastAPI | Flask |
|
|
8
8
|
|-------------|---------|-------|
|
|
@@ -27,9 +27,9 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
27
27
|
- ⚙️ **Moderate/Possible**: Doable with some effort
|
|
28
28
|
- ⚠️ **Limited**: Has constraints or limitations
|
|
29
29
|
|
|
30
|
-
## Detailed
|
|
30
|
+
## Detailed Framework Comparison
|
|
31
31
|
|
|
32
|
-
###
|
|
32
|
+
### FastAPI (use python-backend-engineer with framework=fastapi)
|
|
33
33
|
|
|
34
34
|
**Best For:**
|
|
35
35
|
- **Modern APIs**: REST/GraphQL APIs with auto-documentation
|
|
@@ -55,7 +55,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
55
55
|
- IoT data ingestion APIs
|
|
56
56
|
- Modern single-page app backends
|
|
57
57
|
|
|
58
|
-
###
|
|
58
|
+
### Flask (use python-backend-engineer with framework=flask)
|
|
59
59
|
|
|
60
60
|
**Best For:**
|
|
61
61
|
- **Traditional Web Applications**: Server-rendered applications
|
|
@@ -86,7 +86,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
86
86
|
### 1. What type of application are you building?
|
|
87
87
|
|
|
88
88
|
#### API-Only Applications
|
|
89
|
-
→ **
|
|
89
|
+
→ **FastAPI** (python-backend-engineer with framework=fastapi)
|
|
90
90
|
**Reasoning:**
|
|
91
91
|
- Auto-generated API documentation
|
|
92
92
|
- Built-in request/response validation
|
|
@@ -94,7 +94,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
94
94
|
- Native async support for database operations
|
|
95
95
|
|
|
96
96
|
#### Web Applications with Templates
|
|
97
|
-
→ **
|
|
97
|
+
→ **Flask** (python-backend-engineer with framework=flask)
|
|
98
98
|
**Reasoning:**
|
|
99
99
|
- Mature template engine (Jinja2)
|
|
100
100
|
- Server-side rendering capabilities
|
|
@@ -103,13 +103,13 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
103
103
|
|
|
104
104
|
#### Hybrid (API + Web)
|
|
105
105
|
→ **Consider both or choose based on primary focus:**
|
|
106
|
-
- API-heavy →
|
|
107
|
-
- Web-heavy →
|
|
106
|
+
- API-heavy → FastAPI (python-backend-engineer with framework=fastapi)
|
|
107
|
+
- Web-heavy → Flask (python-backend-engineer with framework=flask)
|
|
108
108
|
|
|
109
109
|
### 2. What are your performance requirements?
|
|
110
110
|
|
|
111
111
|
#### High Performance Required
|
|
112
|
-
→ **
|
|
112
|
+
→ **FastAPI** (python-backend-engineer with framework=fastapi)
|
|
113
113
|
**Use When:**
|
|
114
114
|
- 1000+ requests per second expected
|
|
115
115
|
- Low latency requirements (< 100ms)
|
|
@@ -117,7 +117,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
117
117
|
- Concurrent user handling important
|
|
118
118
|
|
|
119
119
|
#### Standard Performance Acceptable
|
|
120
|
-
→ **
|
|
120
|
+
→ **Flask** (python-backend-engineer with framework=flask)
|
|
121
121
|
**Use When:**
|
|
122
122
|
- < 1000 requests per second
|
|
123
123
|
- Response time requirements moderate
|
|
@@ -127,7 +127,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
127
127
|
### 3. What is your team's experience level?
|
|
128
128
|
|
|
129
129
|
#### Python Beginners to Intermediate
|
|
130
|
-
→ **
|
|
130
|
+
→ **Flask** (python-backend-engineer with framework=flask)
|
|
131
131
|
**Reasoning:**
|
|
132
132
|
- Simpler concepts and patterns
|
|
133
133
|
- Extensive tutorials and examples
|
|
@@ -135,7 +135,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
135
135
|
- Gradual learning curve
|
|
136
136
|
|
|
137
137
|
#### Python Advanced or Performance-Focused Teams
|
|
138
|
-
→ **
|
|
138
|
+
→ **FastAPI** (python-backend-engineer with framework=fastapi)
|
|
139
139
|
**Reasoning:**
|
|
140
140
|
- Leverages advanced Python features
|
|
141
141
|
- Type hints and modern patterns
|
|
@@ -145,7 +145,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
145
145
|
### 4. What are your integration requirements?
|
|
146
146
|
|
|
147
147
|
#### Modern Stack (React, Vue, Mobile Apps)
|
|
148
|
-
→ **
|
|
148
|
+
→ **FastAPI** (python-backend-engineer with framework=fastapi)
|
|
149
149
|
**Features:**
|
|
150
150
|
- Auto-generated API clients
|
|
151
151
|
- OpenAPI specification
|
|
@@ -153,7 +153,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
153
153
|
- CORS handling built-in
|
|
154
154
|
|
|
155
155
|
#### Traditional Stack (Server-rendered, jQuery)
|
|
156
|
-
→ **
|
|
156
|
+
→ **Flask** (python-backend-engineer with framework=flask)
|
|
157
157
|
**Features:**
|
|
158
158
|
- Template inheritance
|
|
159
159
|
- Form handling with WTForms
|
|
@@ -165,7 +165,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
165
165
|
### API Development
|
|
166
166
|
|
|
167
167
|
#### RESTful API for Mobile App
|
|
168
|
-
**Choice**:
|
|
168
|
+
**Choice**: FastAPI (python-backend-engineer with framework=fastapi)
|
|
169
169
|
**Reasoning:**
|
|
170
170
|
- Auto-generated API documentation
|
|
171
171
|
- Request/response validation
|
|
@@ -173,7 +173,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
173
173
|
- Easy async database operations
|
|
174
174
|
|
|
175
175
|
#### Enterprise API with Complex Business Logic
|
|
176
|
-
**Choice**:
|
|
176
|
+
**Choice**: FastAPI (python-backend-engineer with framework=fastapi)
|
|
177
177
|
**Reasoning:**
|
|
178
178
|
- Type safety for complex data structures
|
|
179
179
|
- Dependency injection for business services
|
|
@@ -183,7 +183,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
183
183
|
### Web Applications
|
|
184
184
|
|
|
185
185
|
#### Content Management System
|
|
186
|
-
**Choice**:
|
|
186
|
+
**Choice**: Flask (python-backend-engineer with framework=flask)
|
|
187
187
|
**Reasoning:**
|
|
188
188
|
- Server-side rendering capabilities
|
|
189
189
|
- Admin interface patterns
|
|
@@ -191,7 +191,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
191
191
|
- Traditional web architecture
|
|
192
192
|
|
|
193
193
|
#### E-commerce Platform
|
|
194
|
-
**Choice**:
|
|
194
|
+
**Choice**: Flask (python-backend-engineer with framework=flask)
|
|
195
195
|
**Reasoning:**
|
|
196
196
|
- Complex form handling (checkout, admin)
|
|
197
197
|
- Server-side rendering for SEO
|
|
@@ -201,7 +201,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
201
201
|
### Hybrid Applications
|
|
202
202
|
|
|
203
203
|
#### SaaS Platform (Web + API)
|
|
204
|
-
**Primary Choice**:
|
|
204
|
+
**Primary Choice**: FastAPI (python-backend-engineer with framework=fastapi)
|
|
205
205
|
**Reasoning:**
|
|
206
206
|
- API-first for modern frontend
|
|
207
207
|
- WebSocket for real-time features
|
|
@@ -215,7 +215,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
215
215
|
### Specific Scenarios
|
|
216
216
|
|
|
217
217
|
#### Microservices Architecture
|
|
218
|
-
**Choice**:
|
|
218
|
+
**Choice**: FastAPI (python-backend-engineer with framework=fastapi)
|
|
219
219
|
**Features:**
|
|
220
220
|
- Smaller, focused services
|
|
221
221
|
- Async communication between services
|
|
@@ -223,7 +223,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
223
223
|
- High performance per service
|
|
224
224
|
|
|
225
225
|
#### Machine Learning API
|
|
226
|
-
**Choice**:
|
|
226
|
+
**Choice**: FastAPI (python-backend-engineer with framework=fastapi)
|
|
227
227
|
**Features:**
|
|
228
228
|
- Async model inference
|
|
229
229
|
- Request validation for ML inputs
|
|
@@ -231,7 +231,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
231
231
|
- WebSocket for real-time predictions
|
|
232
232
|
|
|
233
233
|
#### Legacy System Integration
|
|
234
|
-
**Choice**:
|
|
234
|
+
**Choice**: Flask (python-backend-engineer with framework=flask)
|
|
235
235
|
**Features:**
|
|
236
236
|
- Established integration patterns
|
|
237
237
|
- Flexible architecture for custom needs
|
|
@@ -240,8 +240,8 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
|
|
|
240
240
|
|
|
241
241
|
#### Startup MVP
|
|
242
242
|
**Choice**: Depends on team and product
|
|
243
|
-
- **Technical team building API**:
|
|
244
|
-
- **Mixed team building web app**:
|
|
243
|
+
- **Technical team building API**: FastAPI (python-backend-engineer with framework=fastapi)
|
|
244
|
+
- **Mixed team building web app**: Flask (python-backend-engineer with framework=flask)
|
|
245
245
|
|
|
246
246
|
## Performance Comparison
|
|
247
247
|
|
|
@@ -31,26 +31,26 @@ Use this matrix to choose the right UI framework agent based on your project req
|
|
|
31
31
|
### Project Type
|
|
32
32
|
|
|
33
33
|
#### Enterprise Applications
|
|
34
|
-
**Primary Choice:
|
|
34
|
+
**Primary Choice: react-ui-expert**
|
|
35
35
|
- Pre-built complex components (ProTable, ProForm)
|
|
36
36
|
- Enterprise-grade data management
|
|
37
37
|
- Professional design language
|
|
38
38
|
- Built-in admin patterns
|
|
39
39
|
|
|
40
|
-
**Alternative:
|
|
40
|
+
**Alternative: react-frontend-engineer**
|
|
41
41
|
- Material Design consistency
|
|
42
42
|
- DataGrid for complex tables
|
|
43
43
|
- Strong TypeScript support
|
|
44
44
|
- Large ecosystem
|
|
45
45
|
|
|
46
46
|
#### Startup/MVP
|
|
47
|
-
**Primary Choice:
|
|
47
|
+
**Primary Choice: react-ui-expert**
|
|
48
48
|
- Fastest development time
|
|
49
49
|
- Extensive pre-built templates
|
|
50
50
|
- Strong community resources
|
|
51
51
|
- Easy developer onboarding
|
|
52
52
|
|
|
53
|
-
**Alternative:
|
|
53
|
+
**Alternative: react-frontend-engineer**
|
|
54
54
|
- Modern developer experience
|
|
55
55
|
- Excellent component composition
|
|
56
56
|
- Built-in accessibility
|
|
@@ -63,7 +63,7 @@ Use this matrix to choose the right UI framework agent based on your project req
|
|
|
63
63
|
- Utility-first approach
|
|
64
64
|
- Optimal performance
|
|
65
65
|
|
|
66
|
-
**Alternative:
|
|
66
|
+
**Alternative: react-frontend-engineer**
|
|
67
67
|
- Styled-system approach
|
|
68
68
|
- Design tokens
|
|
69
69
|
- Easy customization
|
|
@@ -72,43 +72,43 @@ Use this matrix to choose the right UI framework agent based on your project req
|
|
|
72
72
|
### Team Expertise
|
|
73
73
|
|
|
74
74
|
#### Junior Developers
|
|
75
|
-
1. **
|
|
76
|
-
2. **
|
|
77
|
-
3. **
|
|
75
|
+
1. **react-ui-expert** - Familiar patterns, extensive docs
|
|
76
|
+
2. **react-frontend-engineer** - Intuitive API, good defaults
|
|
77
|
+
3. **react-frontend-engineer** - Material Design guidelines
|
|
78
78
|
|
|
79
79
|
#### Senior/Design Teams
|
|
80
80
|
1. **tailwindcss-expert** - Full control, custom systems
|
|
81
|
-
2. **
|
|
82
|
-
3. **
|
|
81
|
+
2. **react-frontend-engineer** - Balanced flexibility/productivity
|
|
82
|
+
3. **react-frontend-engineer** - Advanced patterns, customization
|
|
83
83
|
|
|
84
84
|
### Technical Requirements
|
|
85
85
|
|
|
86
86
|
#### Performance Critical
|
|
87
87
|
1. **tailwindcss-expert** - Purged CSS, optimal bundles
|
|
88
|
-
2. **
|
|
89
|
-
3. **
|
|
88
|
+
2. **react-frontend-engineer** - Tree-shakeable, efficient
|
|
89
|
+
3. **react-ui-expert** - Minimal JS overhead
|
|
90
90
|
|
|
91
91
|
#### Accessibility Required
|
|
92
|
-
1. **
|
|
93
|
-
2. **
|
|
94
|
-
3. **
|
|
92
|
+
1. **react-frontend-engineer** - Accessibility-first design
|
|
93
|
+
2. **react-frontend-engineer** - ARIA compliance built-in
|
|
94
|
+
3. **react-ui-expert** - Enterprise accessibility
|
|
95
95
|
|
|
96
96
|
#### Mobile-First
|
|
97
97
|
1. **tailwindcss-expert** - Mobile-first utilities
|
|
98
|
-
2. **
|
|
99
|
-
3. **
|
|
98
|
+
2. **react-ui-expert** - Mobile-first grid
|
|
99
|
+
3. **react-frontend-engineer** - Responsive design patterns
|
|
100
100
|
|
|
101
101
|
### Industry/Domain
|
|
102
102
|
|
|
103
103
|
#### Financial Services
|
|
104
|
-
**Primary:
|
|
104
|
+
**Primary: react-ui-expert**
|
|
105
105
|
- Data-heavy interfaces
|
|
106
106
|
- Professional appearance
|
|
107
107
|
- Complex forms/tables
|
|
108
108
|
- Enterprise features
|
|
109
109
|
|
|
110
110
|
#### Healthcare
|
|
111
|
-
**Primary:
|
|
111
|
+
**Primary: react-frontend-engineer**
|
|
112
112
|
- Accessibility compliance
|
|
113
113
|
- Professional UI standards
|
|
114
114
|
- Form-heavy applications
|
|
@@ -122,7 +122,7 @@ Use this matrix to choose the right UI framework agent based on your project req
|
|
|
122
122
|
- Marketing integration
|
|
123
123
|
|
|
124
124
|
#### SaaS Products
|
|
125
|
-
**Primary:
|
|
125
|
+
**Primary: react-frontend-engineer**
|
|
126
126
|
- Modern user expectations
|
|
127
127
|
- Dashboard interfaces
|
|
128
128
|
- Component flexibility
|
|
@@ -138,13 +138,13 @@ Use this matrix to choose the right UI framework agent based on your project req
|
|
|
138
138
|
|
|
139
139
|
#### From Material-UI v4 → v5
|
|
140
140
|
- **Reason**: Keep existing investment
|
|
141
|
-
- **Agent**:
|
|
141
|
+
- **Agent**: react-frontend-engineer
|
|
142
142
|
- **Effort**: Moderate (migration guide available)
|
|
143
143
|
- **Benefits**: Better performance, new features
|
|
144
144
|
|
|
145
145
|
#### From Custom CSS → Component Library
|
|
146
146
|
- **Reason**: Faster development, consistency
|
|
147
|
-
- **Agent**:
|
|
147
|
+
- **Agent**: react-frontend-engineer (modern) or react-ui-expert (familiar)
|
|
148
148
|
- **Effort**: Moderate to High
|
|
149
149
|
- **Benefits**: Accessibility, maintainability
|
|
150
150
|
|
|
@@ -153,41 +153,41 @@ Use this matrix to choose the right UI framework agent based on your project req
|
|
|
153
153
|
Ask these questions to determine the best agent:
|
|
154
154
|
|
|
155
155
|
1. **What is the primary use case?**
|
|
156
|
-
- Admin dashboard →
|
|
157
|
-
- Marketing site →
|
|
158
|
-
- SaaS product →
|
|
156
|
+
- Admin dashboard → react-ui-expert
|
|
157
|
+
- Marketing site → react-ui-expert or tailwindcss-expert
|
|
158
|
+
- SaaS product → react-frontend-engineer or react-frontend-engineer
|
|
159
159
|
|
|
160
160
|
2. **What is the team's experience level?**
|
|
161
|
-
- Junior team →
|
|
162
|
-
- Senior team → tailwindcss-expert or
|
|
161
|
+
- Junior team → react-ui-expert or react-frontend-engineer
|
|
162
|
+
- Senior team → tailwindcss-expert or react-frontend-engineer
|
|
163
163
|
|
|
164
164
|
3. **How important is design flexibility?**
|
|
165
165
|
- Critical → tailwindcss-expert
|
|
166
|
-
- Important →
|
|
167
|
-
- Standard →
|
|
168
|
-
- Basic →
|
|
166
|
+
- Important → react-frontend-engineer
|
|
167
|
+
- Standard → react-frontend-engineer or react-ui-expert
|
|
168
|
+
- Basic → react-ui-expert
|
|
169
169
|
|
|
170
170
|
4. **What are the performance requirements?**
|
|
171
|
-
- Critical → tailwindcss-expert or
|
|
172
|
-
- Important →
|
|
173
|
-
- Standard →
|
|
171
|
+
- Critical → tailwindcss-expert or react-frontend-engineer
|
|
172
|
+
- Important → react-frontend-engineer (with optimization)
|
|
173
|
+
- Standard → react-ui-expert or react-frontend-engineer
|
|
174
174
|
|
|
175
175
|
5. **Is accessibility a requirement?**
|
|
176
|
-
- Critical →
|
|
177
|
-
- Important →
|
|
178
|
-
- Standard →
|
|
176
|
+
- Critical → react-frontend-engineer or react-ui-expert
|
|
177
|
+
- Important → react-ui-expert
|
|
178
|
+
- Standard → react-ui-expert or tailwindcss-expert (with extra work)
|
|
179
179
|
|
|
180
180
|
6. **What type of data interfaces are needed?**
|
|
181
|
-
- Complex tables →
|
|
181
|
+
- Complex tables → react-ui-expert or react-frontend-engineer
|
|
182
182
|
- Forms → All frameworks suitable
|
|
183
|
-
- Charts/visualization →
|
|
184
|
-
- Simple content →
|
|
183
|
+
- Charts/visualization → react-frontend-engineer or tailwindcss-expert
|
|
184
|
+
- Simple content → react-ui-expert or react-frontend-engineer
|
|
185
185
|
|
|
186
186
|
## Agent Selection Examples
|
|
187
187
|
|
|
188
188
|
### Example 1: B2B SaaS Dashboard
|
|
189
189
|
**Requirements**: Professional look, complex data tables, user management, responsive
|
|
190
|
-
**Choice**:
|
|
190
|
+
**Choice**: react-ui-expert
|
|
191
191
|
**Reasoning**: ProTable for data, enterprise components, professional design
|
|
192
192
|
|
|
193
193
|
### Example 2: Consumer Mobile App
|
|
@@ -197,15 +197,15 @@ Ask these questions to determine the best agent:
|
|
|
197
197
|
|
|
198
198
|
### Example 3: Startup MVP
|
|
199
199
|
**Requirements**: Fast development, standard UI patterns, small team, limited budget
|
|
200
|
-
**Choice**:
|
|
200
|
+
**Choice**: react-ui-expert
|
|
201
201
|
**Reasoning**: Fastest development, familiar patterns, extensive resources
|
|
202
202
|
|
|
203
203
|
### Example 4: Design System Creation
|
|
204
204
|
**Requirements**: Component library, design tokens, accessibility, maintainability
|
|
205
|
-
**Choice**:
|
|
205
|
+
**Choice**: react-frontend-engineer
|
|
206
206
|
**Reasoning**: Built for design systems, accessibility-first, component composition
|
|
207
207
|
|
|
208
208
|
### Example 5: Material Design Application
|
|
209
209
|
**Requirements**: Google Material Design, complex components, data visualization
|
|
210
|
-
**Choice**:
|
|
210
|
+
**Choice**: react-frontend-engineer
|
|
211
211
|
**Reasoning**: Official Material Design implementation, advanced components
|
|
@@ -300,7 +300,7 @@ Before delivering GitHub configurations:
|
|
|
300
300
|
|
|
301
301
|
- **react-frontend-engineer**: Frontend deployment workflows
|
|
302
302
|
- **python-backend-engineer**: Backend CI/CD pipelines
|
|
303
|
-
- **
|
|
303
|
+
- **frontend-testing-engineer**: E2E testing in workflows
|
|
304
304
|
- **kubernetes-orchestrator**: Deployment to K8s clusters
|
|
305
305
|
- **azure-devops-specialist**: Cross-platform integration
|
|
306
306
|
|
|
@@ -9,22 +9,22 @@ Specialized agents for specific frameworks and libraries. These agents understan
|
|
|
9
9
|
- **Styling**: Tailwind CSS, CSS-in-JS, responsive design
|
|
10
10
|
- **Features**: SSR/SSG, performance optimization, accessibility
|
|
11
11
|
|
|
12
|
-
### 🎭
|
|
12
|
+
### 🎭 frontend-testing-engineer
|
|
13
13
|
- **Expertise**: Playwright, E2E testing, visual regression
|
|
14
14
|
- **Features**: Cross-browser testing, parallel execution
|
|
15
15
|
- **Integration**: MCP browser control, CI/CD pipelines
|
|
16
16
|
|
|
17
|
-
### 🎭
|
|
17
|
+
### 🎭 frontend-testing-engineer
|
|
18
18
|
- **Expertise**: Advanced Playwright with MCP browser control
|
|
19
19
|
- **Features**: Visual testing, accessibility audits, UX validation
|
|
20
20
|
- **Specialties**: Real browser control, performance monitoring, WCAG compliance
|
|
21
21
|
|
|
22
|
-
### 🚀
|
|
22
|
+
### 🚀 python-backend-engineer
|
|
23
23
|
- **Expertise**: FastAPI, Pydantic, async Python, OpenAPI
|
|
24
24
|
- **Features**: High-performance APIs, WebSockets, background tasks
|
|
25
25
|
- **Integration**: SQLAlchemy, Redis, Celery, authentication
|
|
26
26
|
|
|
27
|
-
### 🍶
|
|
27
|
+
### 🍶 python-backend-engineer
|
|
28
28
|
- **Expertise**: Flask, Blueprints, Flask extensions ecosystem
|
|
29
29
|
- **Features**: Web apps, REST APIs, Jinja2 templates
|
|
30
30
|
- **Integration**: Flask-SQLAlchemy, Flask-Login, Flask-RESTful
|
|
@@ -43,7 +43,7 @@ Specialized agents for specific frameworks and libraries. These agents understan
|
|
|
43
43
|
- **Expertise**: Next.js 14+, App Router, Server Components
|
|
44
44
|
- **Features**: ISR, API routes, middleware
|
|
45
45
|
|
|
46
|
-
### 🔥
|
|
46
|
+
### 🔥 python-backend-engineer
|
|
47
47
|
- **Expertise**: FastAPI, Pydantic, async Python
|
|
48
48
|
- **Features**: OpenAPI, WebSocket, background tasks
|
|
49
49
|
|
|
@@ -192,7 +192,7 @@ test('visual regression', async ({ page }) => {
|
|
|
192
192
|
- mcp__playwright__fill
|
|
193
193
|
|
|
194
194
|
## Integration Points
|
|
195
|
-
- Tests applications from: react-
|
|
195
|
+
- Tests applications from: react-frontend-engineer, python-backend-engineer
|
|
196
196
|
- Validates deployments by: kubernetes-orchestrator
|
|
197
197
|
- Reports to: github-operations-specialist
|
|
198
198
|
- Uses infrastructure from: docker-containerization-expert
|
|
@@ -130,7 +130,7 @@ Use these queries:
|
|
|
130
130
|
|
|
131
131
|
## Integration Points
|
|
132
132
|
|
|
133
|
-
- Works with: kubernetes-orchestrator, docker-expert, nodejs-backend-engineer, python-backend-engineer, github-operations-specialist
|
|
133
|
+
- Works with: kubernetes-orchestrator, docker-containerization-expert, nodejs-backend-engineer, python-backend-engineer, github-operations-specialist
|
|
134
134
|
- Provides to: Microservices, event systems, real-time apps, distributed systems
|
|
135
135
|
- Client libraries: Go, Python, Node.js, Java, C#, Rust
|
|
136
136
|
|
|
@@ -191,7 +191,7 @@ Before delivering code:
|
|
|
191
191
|
**Integration with Other Agents:**
|
|
192
192
|
|
|
193
193
|
- **python-backend-engineer**: API contract definition and type generation
|
|
194
|
-
- **
|
|
194
|
+
- **frontend-testing-engineer**: E2E test scenarios and component interaction testing
|
|
195
195
|
- **azure-devops-specialist**: CI/CD pipeline for build and deployment
|
|
196
196
|
- **github-operations-specialist**: PR workflows and code review automation
|
|
197
197
|
|
|
@@ -137,9 +137,9 @@ accessibility_level:
|
|
|
137
137
|
- Agent
|
|
138
138
|
|
|
139
139
|
## Integration Points
|
|
140
|
-
- Works with: react-frontend-engineer,
|
|
141
|
-
- Provides UI for: python-backend-
|
|
142
|
-
- Tested by:
|
|
140
|
+
- Works with: react-frontend-engineer, frontend-testing-engineer
|
|
141
|
+
- Provides UI for: python-backend-engineer, nodejs-backend-engineer
|
|
142
|
+
- Tested by: frontend-testing-engineer
|
|
143
143
|
|
|
144
144
|
## Example Invocation
|
|
145
145
|
|
|
@@ -60,8 +60,8 @@ Access Tailwind CSS documentation through context7:
|
|
|
60
60
|
- Long-term maintainability and scalability are important
|
|
61
61
|
|
|
62
62
|
**Consider alternatives when:**
|
|
63
|
-
- Need rapid development with pre-built components (→ bootstrap-ui-expert or
|
|
64
|
-
- Material Design is required (→
|
|
63
|
+
- Need rapid development with pre-built components (→ bootstrap-ui-expert or react-frontend-engineer)
|
|
64
|
+
- Material Design is required (→ react-frontend-engineer)
|
|
65
65
|
- Enterprise data components needed (→ antd-react-expert)
|
|
66
66
|
- Team lacks advanced CSS skills (→ component-based alternatives)
|
|
67
67
|
|
|
@@ -737,5 +737,5 @@ module.exports = {
|
|
|
737
737
|
## Integration Points
|
|
738
738
|
|
|
739
739
|
- Works with: react-frontend-engineer, ux-design-expert, bootstrap-ui-expert
|
|
740
|
-
- Hands off to:
|
|
740
|
+
- Hands off to: frontend-testing-engineer for testing
|
|
741
741
|
- Receives from: design system specifications and UI mockups
|
|
@@ -153,9 +153,9 @@ Access UX design and accessibility documentation:
|
|
|
153
153
|
|
|
154
154
|
### Works With
|
|
155
155
|
- **react-frontend-engineer**: Implementation of designs
|
|
156
|
-
- **
|
|
157
|
-
- **tailwindcss-expert
|
|
158
|
-
- **
|
|
156
|
+
- **react-ui-expert**: Component styling and design systems
|
|
157
|
+
- **tailwindcss-expert**: Utility-first CSS framework
|
|
158
|
+
- **frontend-testing-engineer**: Usability testing automation
|
|
159
159
|
- **javascript-frontend-engineer**: Interactive features
|
|
160
160
|
|
|
161
161
|
### Provides To
|
|
@@ -38,5 +38,5 @@ Parameters: environment=production, ssl=letsencrypt, discovery=docker, features=
|
|
|
38
38
|
```
|
|
39
39
|
|
|
40
40
|
## Related Agents
|
|
41
|
-
- docker-expert: For container configuration
|
|
41
|
+
- docker-containerization-expert: For container configuration
|
|
42
42
|
- kubernetes-orchestrator: For K8s integration
|
|
@@ -18,4 +18,4 @@ Creates Playwright test suite with Page Object Model.
|
|
|
18
18
|
- Adds visual regression setup
|
|
19
19
|
- Creates CI/CD integration scripts
|
|
20
20
|
|
|
21
|
-
Use the
|
|
21
|
+
Use the frontend-testing-engineer agent to create comprehensive E2E test suite.
|
|
@@ -11,6 +11,21 @@ Push epic and tasks to GitHub as issues using modular scripts.
|
|
|
11
11
|
/pm:epic-sync <feature_name>
|
|
12
12
|
```
|
|
13
13
|
|
|
14
|
+
## Quick Start
|
|
15
|
+
|
|
16
|
+
The simplest way to sync an epic to GitHub:
|
|
17
|
+
|
|
18
|
+
```bash
|
|
19
|
+
# Full automated sync (recommended)
|
|
20
|
+
bash .claude/scripts/pm/epic-sync.sh "$ARGUMENTS"
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
This orchestration script automatically runs all 4 steps:
|
|
24
|
+
1. Creates epic issue
|
|
25
|
+
2. Creates task issues
|
|
26
|
+
3. Renames files to issue numbers
|
|
27
|
+
4. Updates all references
|
|
28
|
+
|
|
14
29
|
## Quick Check
|
|
15
30
|
|
|
16
31
|
```bash
|
|
@@ -32,7 +47,14 @@ If no tasks found: "❌ No tasks to sync. Run: /pm:epic-decompose $ARGUMENTS"
|
|
|
32
47
|
|
|
33
48
|
## Instructions
|
|
34
49
|
|
|
35
|
-
|
|
50
|
+
**⚡ Quick Command:**
|
|
51
|
+
```bash
|
|
52
|
+
bash .claude/scripts/pm/epic-sync.sh "$ARGUMENTS"
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
The epic sync process is modularized into 4 specialized scripts that handle different aspects of the synchronization. Each script is designed for reliability, testability, and maintainability.
|
|
56
|
+
|
|
57
|
+
The orchestration script (`.claude/scripts/pm/epic-sync.sh`) automatically runs all 4 steps in sequence. The individual scripts are documented below for reference and debugging.
|
|
36
58
|
|
|
37
59
|
### Processing Mode Detection
|
|
38
60
|
|
|
@@ -158,13 +180,24 @@ echo "✅ Created branch: epic/$ARGUMENTS"
|
|
|
158
180
|
|
|
159
181
|
## Complete Workflow Examples
|
|
160
182
|
|
|
161
|
-
### Single Epic Workflow
|
|
183
|
+
### Single Epic Workflow (Automated - Recommended)
|
|
184
|
+
|
|
185
|
+
The **easiest way** is to use the orchestration script that handles everything:
|
|
186
|
+
|
|
187
|
+
```bash
|
|
188
|
+
# One command does it all!
|
|
189
|
+
bash .claude/scripts/pm/epic-sync.sh "$ARGUMENTS"
|
|
190
|
+
```
|
|
191
|
+
|
|
192
|
+
This automatically runs all 4 steps and provides a complete summary.
|
|
193
|
+
|
|
194
|
+
### Single Epic Workflow (Manual Steps)
|
|
162
195
|
|
|
163
|
-
|
|
196
|
+
If you need to run steps individually for debugging:
|
|
164
197
|
|
|
165
198
|
```bash
|
|
166
199
|
#!/bin/bash
|
|
167
|
-
# Complete epic sync using modular scripts
|
|
200
|
+
# Complete epic sync using modular scripts (manual)
|
|
168
201
|
|
|
169
202
|
EPIC_NAME="$ARGUMENTS"
|
|
170
203
|
|
|
@@ -8,7 +8,7 @@ Create a complete Bootstrap-based UI structure with responsive components and th
|
|
|
8
8
|
```
|
|
9
9
|
|
|
10
10
|
## Purpose
|
|
11
|
-
Use the
|
|
11
|
+
Use the react-ui-expert agent (with framework=bootstrap) to create a complete Bootstrap application scaffold with modern components, responsive design, and customizable themes.
|
|
12
12
|
|
|
13
13
|
## Parameters
|
|
14
14
|
- `theme`: Theme variant (light, dark, corporate, minimal)
|
|
@@ -18,7 +18,7 @@ Use the bootstrap-ui-expert agent to create a complete Bootstrap application sca
|
|
|
18
18
|
|
|
19
19
|
## Agent Usage
|
|
20
20
|
```
|
|
21
|
-
Use the
|
|
21
|
+
Use the react-ui-expert agent with framework=bootstrap to create a complete Bootstrap application scaffold.
|
|
22
22
|
```
|
|
23
23
|
|
|
24
24
|
## Expected Outcome
|
|
@@ -32,10 +32,11 @@ Use the bootstrap-ui-expert agent to create a complete Bootstrap application sca
|
|
|
32
32
|
## Example Usage
|
|
33
33
|
```
|
|
34
34
|
Task: Create Bootstrap dashboard with sidebar navigation, responsive cards grid, and contact forms
|
|
35
|
-
Agent:
|
|
36
|
-
Parameters: theme=corporate, components=navbar,sidebar,cards,forms,modals, responsive=all, features=dark-mode,validation
|
|
35
|
+
Agent: react-ui-expert
|
|
36
|
+
Parameters: framework=bootstrap, theme=corporate, components=navbar,sidebar,cards,forms,modals, responsive=all, features=dark-mode,validation
|
|
37
37
|
```
|
|
38
38
|
|
|
39
39
|
## Related Agents
|
|
40
40
|
- tailwindcss-expert: For utility-first alternative
|
|
41
|
-
- react-frontend-engineer: For React + Bootstrap integration
|
|
41
|
+
- react-frontend-engineer: For React + Bootstrap integration
|
|
42
|
+
- react-ui-expert: Main agent for UI component architecture
|
|
@@ -37,5 +37,5 @@ Parameters: theme=modern, utilities=custom-spacing,gradients,animations, compone
|
|
|
37
37
|
```
|
|
38
38
|
|
|
39
39
|
## Related Agents
|
|
40
|
-
-
|
|
40
|
+
- react-ui-expert: For component-based alternative
|
|
41
41
|
- react-frontend-engineer: For React + Tailwind integration
|
|
@@ -74,7 +74,7 @@ autopm mcp sync
|
|
|
74
74
|
### Integration with Agents
|
|
75
75
|
|
|
76
76
|
Used extensively with:
|
|
77
|
-
- `
|
|
77
|
+
- `frontend-testing-engineer` - For E2E test creation
|
|
78
78
|
- `react-frontend-engineer` - For UI testing
|
|
79
79
|
- `ux-design-expert` - For visual regression
|
|
80
80
|
|
|
@@ -309,4 +309,4 @@ npx playwright show-trace trace.zip
|
|
|
309
309
|
|
|
310
310
|
- [Playwright Documentation](https://playwright.dev)
|
|
311
311
|
- [MCP Browser Control](https://modelcontextprotocol.org/browser)
|
|
312
|
-
- [E2E Test Engineer Agent](../agents/frameworks/
|
|
312
|
+
- [E2E Test Engineer Agent](../agents/frameworks/frontend-testing-engineer.md)
|