codingbuddy-rules 3.1.1 → 3.1.2
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/.ai-rules/adapters/antigravity.md +48 -0
- package/.ai-rules/adapters/claude-code.md +48 -0
- package/.ai-rules/adapters/codex.md +48 -0
- package/.ai-rules/adapters/cursor.md +48 -0
- package/.ai-rules/adapters/kiro.md +48 -0
- package/.ai-rules/adapters/q.md +48 -0
- package/.ai-rules/agents/accessibility-specialist.json +0 -4
- package/.ai-rules/agents/act-mode.json +0 -15
- package/.ai-rules/agents/agent-architect.json +0 -14
- package/.ai-rules/agents/ai-ml-engineer.json +0 -17
- package/.ai-rules/agents/architecture-specialist.json +0 -4
- package/.ai-rules/agents/backend-developer.json +0 -22
- package/.ai-rules/agents/code-quality-specialist.json +0 -4
- package/.ai-rules/agents/code-reviewer.json +0 -50
- package/.ai-rules/agents/data-engineer.json +0 -18
- package/.ai-rules/agents/devops-engineer.json +0 -14
- package/.ai-rules/agents/documentation-specialist.json +0 -4
- package/.ai-rules/agents/eval-mode.json +0 -15
- package/.ai-rules/agents/event-architecture-specialist.json +0 -4
- package/.ai-rules/agents/frontend-developer.json +0 -21
- package/.ai-rules/agents/i18n-specialist.json +0 -4
- package/.ai-rules/agents/integration-specialist.json +0 -4
- package/.ai-rules/agents/migration-specialist.json +0 -4
- package/.ai-rules/agents/mobile-developer.json +0 -18
- package/.ai-rules/agents/observability-specialist.json +0 -4
- package/.ai-rules/agents/performance-specialist.json +0 -4
- package/.ai-rules/agents/plan-mode.json +0 -13
- package/.ai-rules/agents/platform-engineer.json +0 -16
- package/.ai-rules/agents/security-specialist.json +0 -4
- package/.ai-rules/agents/seo-specialist.json +0 -4
- package/.ai-rules/agents/solution-architect.json +0 -14
- package/.ai-rules/agents/technical-planner.json +0 -15
- package/.ai-rules/agents/test-strategy-specialist.json +0 -4
- package/.ai-rules/agents/tooling-engineer.json +0 -13
- package/.ai-rules/agents/ui-ux-designer.json +0 -12
- package/.ai-rules/keyword-modes.json +18 -4
- package/.ai-rules/skills/README.md +6 -0
- package/.ai-rules/skills/pr-all-in-one/SKILL.md +364 -0
- package/.ai-rules/skills/pr-all-in-one/configuration-guide.md +316 -0
- package/.ai-rules/skills/pr-all-in-one/issue-patterns.md +40 -0
- package/.ai-rules/skills/pr-all-in-one/pr-templates.md +154 -0
- package/package.json +1 -1
|
@@ -189,6 +189,54 @@ AI: # Mode: EVAL
|
|
|
189
189
|
- ✅ Access to all specialist agent knowledge
|
|
190
190
|
- ✅ Easy to update: change `.ai-rules/` once, all tools benefit
|
|
191
191
|
|
|
192
|
+
## PR All-in-One Skill
|
|
193
|
+
|
|
194
|
+
Unified commit and PR workflow that:
|
|
195
|
+
- Auto-commits uncommitted changes (grouped logically)
|
|
196
|
+
- Creates or updates PRs with smart issue linking
|
|
197
|
+
- Supports multiple languages (en/ko/bilingual)
|
|
198
|
+
|
|
199
|
+
### Usage
|
|
200
|
+
|
|
201
|
+
```
|
|
202
|
+
/pr-all-in-one [target-branch] [issue-id]
|
|
203
|
+
```
|
|
204
|
+
|
|
205
|
+
**Examples:**
|
|
206
|
+
- `/pr-all-in-one` - PR to default branch, issue from branch name
|
|
207
|
+
- `/pr-all-in-one develop` - PR to develop branch
|
|
208
|
+
- `/pr-all-in-one PROJ-123` - PR with specific issue ID
|
|
209
|
+
- `/pr-all-in-one main PROJ-123` - PR to main with issue ID
|
|
210
|
+
|
|
211
|
+
### Configuration
|
|
212
|
+
|
|
213
|
+
Create `.claude/pr-config.json` in your project root. Required settings:
|
|
214
|
+
- `defaultTargetBranch`: Target branch for PRs
|
|
215
|
+
- `issueTracker`: `jira`, `github`, `linear`, `gitlab`, or `custom`
|
|
216
|
+
- `issuePattern`: Regex pattern for issue ID extraction
|
|
217
|
+
- `prLanguage`: `en`, `ko`, or `bilingual`
|
|
218
|
+
|
|
219
|
+
See `packages/rules/.ai-rules/skills/pr-all-in-one/configuration-guide.md` for all options.
|
|
220
|
+
|
|
221
|
+
### First-time Setup
|
|
222
|
+
|
|
223
|
+
If no config file exists, the skill guides you through interactive setup:
|
|
224
|
+
1. Select PR target branch
|
|
225
|
+
2. Choose issue tracker
|
|
226
|
+
3. Set PR description language
|
|
227
|
+
4. (Optional) Configure issue URL template
|
|
228
|
+
|
|
229
|
+
### Skill Files
|
|
230
|
+
|
|
231
|
+
- `SKILL.md` - Main workflow documentation
|
|
232
|
+
- `configuration-guide.md` - Detailed config options
|
|
233
|
+
- `issue-patterns.md` - Supported issue tracker patterns
|
|
234
|
+
- `pr-templates.md` - PR description templates
|
|
235
|
+
|
|
236
|
+
### Platform-Specific Note
|
|
237
|
+
|
|
238
|
+
Access skill files directly from `.ai-rules/skills/pr-all-in-one/` directory in your project.
|
|
239
|
+
|
|
192
240
|
## AUTO Mode
|
|
193
241
|
|
|
194
242
|
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
@@ -487,6 +487,54 @@ Each workflow mode activates different specialist agents:
|
|
|
487
487
|
|
|
488
488
|
**Important:** Specialists from one mode do NOT carry over to the next mode. Each mode has its own recommended specialist set.
|
|
489
489
|
|
|
490
|
+
## PR All-in-One Skill
|
|
491
|
+
|
|
492
|
+
Unified commit and PR workflow that:
|
|
493
|
+
- Auto-commits uncommitted changes (grouped logically)
|
|
494
|
+
- Creates or updates PRs with smart issue linking
|
|
495
|
+
- Supports multiple languages (en/ko/bilingual)
|
|
496
|
+
|
|
497
|
+
### Usage
|
|
498
|
+
|
|
499
|
+
```
|
|
500
|
+
/pr-all-in-one [target-branch] [issue-id]
|
|
501
|
+
```
|
|
502
|
+
|
|
503
|
+
**Examples:**
|
|
504
|
+
- `/pr-all-in-one` - PR to default branch, issue from branch name
|
|
505
|
+
- `/pr-all-in-one develop` - PR to develop branch
|
|
506
|
+
- `/pr-all-in-one PROJ-123` - PR with specific issue ID
|
|
507
|
+
- `/pr-all-in-one main PROJ-123` - PR to main with issue ID
|
|
508
|
+
|
|
509
|
+
### Configuration
|
|
510
|
+
|
|
511
|
+
Create `.claude/pr-config.json` in your project root. Required settings:
|
|
512
|
+
- `defaultTargetBranch`: Target branch for PRs
|
|
513
|
+
- `issueTracker`: `jira`, `github`, `linear`, `gitlab`, or `custom`
|
|
514
|
+
- `issuePattern`: Regex pattern for issue ID extraction
|
|
515
|
+
- `prLanguage`: `en`, `ko`, or `bilingual`
|
|
516
|
+
|
|
517
|
+
See `packages/rules/.ai-rules/skills/pr-all-in-one/configuration-guide.md` for all options.
|
|
518
|
+
|
|
519
|
+
### First-time Setup
|
|
520
|
+
|
|
521
|
+
If no config file exists, the skill guides you through interactive setup:
|
|
522
|
+
1. Select PR target branch
|
|
523
|
+
2. Choose issue tracker
|
|
524
|
+
3. Set PR description language
|
|
525
|
+
4. (Optional) Configure issue URL template
|
|
526
|
+
|
|
527
|
+
### Skill Files
|
|
528
|
+
|
|
529
|
+
- `SKILL.md` - Main workflow documentation
|
|
530
|
+
- `configuration-guide.md` - Detailed config options
|
|
531
|
+
- `issue-patterns.md` - Supported issue tracker patterns
|
|
532
|
+
- `pr-templates.md` - PR description templates
|
|
533
|
+
|
|
534
|
+
### Platform-Specific Note
|
|
535
|
+
|
|
536
|
+
Use MCP tool `get_skill("pr-all-in-one")` to access skill documentation.
|
|
537
|
+
|
|
490
538
|
## AUTO Mode
|
|
491
539
|
|
|
492
540
|
AUTO mode enables autonomous iteration through PLAN -> ACT -> EVAL cycles until quality criteria are met.
|
|
@@ -148,6 +148,54 @@ Skills are located in `.ai-rules/skills/`. To use a skill:
|
|
|
148
148
|
- `dispatching-parallel-agents` - Handle parallel tasks
|
|
149
149
|
- `frontend-design` - Build production-grade UI
|
|
150
150
|
|
|
151
|
+
## PR All-in-One Skill
|
|
152
|
+
|
|
153
|
+
Unified commit and PR workflow that:
|
|
154
|
+
- Auto-commits uncommitted changes (grouped logically)
|
|
155
|
+
- Creates or updates PRs with smart issue linking
|
|
156
|
+
- Supports multiple languages (en/ko/bilingual)
|
|
157
|
+
|
|
158
|
+
### Usage
|
|
159
|
+
|
|
160
|
+
```
|
|
161
|
+
/pr-all-in-one [target-branch] [issue-id]
|
|
162
|
+
```
|
|
163
|
+
|
|
164
|
+
**Examples:**
|
|
165
|
+
- `/pr-all-in-one` - PR to default branch, issue from branch name
|
|
166
|
+
- `/pr-all-in-one develop` - PR to develop branch
|
|
167
|
+
- `/pr-all-in-one PROJ-123` - PR with specific issue ID
|
|
168
|
+
- `/pr-all-in-one main PROJ-123` - PR to main with issue ID
|
|
169
|
+
|
|
170
|
+
### Configuration
|
|
171
|
+
|
|
172
|
+
Create `.claude/pr-config.json` in your project root. Required settings:
|
|
173
|
+
- `defaultTargetBranch`: Target branch for PRs
|
|
174
|
+
- `issueTracker`: `jira`, `github`, `linear`, `gitlab`, or `custom`
|
|
175
|
+
- `issuePattern`: Regex pattern for issue ID extraction
|
|
176
|
+
- `prLanguage`: `en`, `ko`, or `bilingual`
|
|
177
|
+
|
|
178
|
+
See `packages/rules/.ai-rules/skills/pr-all-in-one/configuration-guide.md` for all options.
|
|
179
|
+
|
|
180
|
+
### First-time Setup
|
|
181
|
+
|
|
182
|
+
If no config file exists, the skill guides you through interactive setup:
|
|
183
|
+
1. Select PR target branch
|
|
184
|
+
2. Choose issue tracker
|
|
185
|
+
3. Set PR description language
|
|
186
|
+
4. (Optional) Configure issue URL template
|
|
187
|
+
|
|
188
|
+
### Skill Files
|
|
189
|
+
|
|
190
|
+
- `SKILL.md` - Main workflow documentation
|
|
191
|
+
- `configuration-guide.md` - Detailed config options
|
|
192
|
+
- `issue-patterns.md` - Supported issue tracker patterns
|
|
193
|
+
- `pr-templates.md` - PR description templates
|
|
194
|
+
|
|
195
|
+
### Platform-Specific Note
|
|
196
|
+
|
|
197
|
+
Use `cat .ai-rules/skills/pr-all-in-one/SKILL.md` to access skill documentation directly.
|
|
198
|
+
|
|
151
199
|
## AUTO Mode
|
|
152
200
|
|
|
153
201
|
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
@@ -166,6 +166,54 @@ This project uses codingbuddy MCP server to manage AI Agents.
|
|
|
166
166
|
|
|
167
167
|
See `AGENTS.md` in project root for details.
|
|
168
168
|
|
|
169
|
+
## PR All-in-One Skill
|
|
170
|
+
|
|
171
|
+
Unified commit and PR workflow that:
|
|
172
|
+
- Auto-commits uncommitted changes (grouped logically)
|
|
173
|
+
- Creates or updates PRs with smart issue linking
|
|
174
|
+
- Supports multiple languages (en/ko/bilingual)
|
|
175
|
+
|
|
176
|
+
### Usage
|
|
177
|
+
|
|
178
|
+
```
|
|
179
|
+
/pr-all-in-one [target-branch] [issue-id]
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
**Examples:**
|
|
183
|
+
- `/pr-all-in-one` - PR to default branch, issue from branch name
|
|
184
|
+
- `/pr-all-in-one develop` - PR to develop branch
|
|
185
|
+
- `/pr-all-in-one PROJ-123` - PR with specific issue ID
|
|
186
|
+
- `/pr-all-in-one main PROJ-123` - PR to main with issue ID
|
|
187
|
+
|
|
188
|
+
### Configuration
|
|
189
|
+
|
|
190
|
+
Create `.claude/pr-config.json` in your project root. Required settings:
|
|
191
|
+
- `defaultTargetBranch`: Target branch for PRs
|
|
192
|
+
- `issueTracker`: `jira`, `github`, `linear`, `gitlab`, or `custom`
|
|
193
|
+
- `issuePattern`: Regex pattern for issue ID extraction
|
|
194
|
+
- `prLanguage`: `en`, `ko`, or `bilingual`
|
|
195
|
+
|
|
196
|
+
See `packages/rules/.ai-rules/skills/pr-all-in-one/configuration-guide.md` for all options.
|
|
197
|
+
|
|
198
|
+
### First-time Setup
|
|
199
|
+
|
|
200
|
+
If no config file exists, the skill guides you through interactive setup:
|
|
201
|
+
1. Select PR target branch
|
|
202
|
+
2. Choose issue tracker
|
|
203
|
+
3. Set PR description language
|
|
204
|
+
4. (Optional) Configure issue URL template
|
|
205
|
+
|
|
206
|
+
### Skill Files
|
|
207
|
+
|
|
208
|
+
- `SKILL.md` - Main workflow documentation
|
|
209
|
+
- `configuration-guide.md` - Detailed config options
|
|
210
|
+
- `issue-patterns.md` - Supported issue tracker patterns
|
|
211
|
+
- `pr-templates.md` - PR description templates
|
|
212
|
+
|
|
213
|
+
### Platform-Specific Note
|
|
214
|
+
|
|
215
|
+
Use @file reference: `@packages/rules/.ai-rules/skills/pr-all-in-one/SKILL.md` to access skill documentation.
|
|
216
|
+
|
|
169
217
|
## AUTO Mode
|
|
170
218
|
|
|
171
219
|
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
@@ -122,6 +122,54 @@ Kiro will generate code following:
|
|
|
122
122
|
2. Update `.kiro/rules/guidelines.md` only for Kiro-specific features
|
|
123
123
|
3. Common rules propagate automatically to all Kiro sessions
|
|
124
124
|
|
|
125
|
+
## PR All-in-One Skill
|
|
126
|
+
|
|
127
|
+
Unified commit and PR workflow that:
|
|
128
|
+
- Auto-commits uncommitted changes (grouped logically)
|
|
129
|
+
- Creates or updates PRs with smart issue linking
|
|
130
|
+
- Supports multiple languages (en/ko/bilingual)
|
|
131
|
+
|
|
132
|
+
### Usage
|
|
133
|
+
|
|
134
|
+
```
|
|
135
|
+
/pr-all-in-one [target-branch] [issue-id]
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
**Examples:**
|
|
139
|
+
- `/pr-all-in-one` - PR to default branch, issue from branch name
|
|
140
|
+
- `/pr-all-in-one develop` - PR to develop branch
|
|
141
|
+
- `/pr-all-in-one PROJ-123` - PR with specific issue ID
|
|
142
|
+
- `/pr-all-in-one main PROJ-123` - PR to main with issue ID
|
|
143
|
+
|
|
144
|
+
### Configuration
|
|
145
|
+
|
|
146
|
+
Create `.claude/pr-config.json` in your project root. Required settings:
|
|
147
|
+
- `defaultTargetBranch`: Target branch for PRs
|
|
148
|
+
- `issueTracker`: `jira`, `github`, `linear`, `gitlab`, or `custom`
|
|
149
|
+
- `issuePattern`: Regex pattern for issue ID extraction
|
|
150
|
+
- `prLanguage`: `en`, `ko`, or `bilingual`
|
|
151
|
+
|
|
152
|
+
See `packages/rules/.ai-rules/skills/pr-all-in-one/configuration-guide.md` for all options.
|
|
153
|
+
|
|
154
|
+
### First-time Setup
|
|
155
|
+
|
|
156
|
+
If no config file exists, the skill guides you through interactive setup:
|
|
157
|
+
1. Select PR target branch
|
|
158
|
+
2. Choose issue tracker
|
|
159
|
+
3. Set PR description language
|
|
160
|
+
4. (Optional) Configure issue URL template
|
|
161
|
+
|
|
162
|
+
### Skill Files
|
|
163
|
+
|
|
164
|
+
- `SKILL.md` - Main workflow documentation
|
|
165
|
+
- `configuration-guide.md` - Detailed config options
|
|
166
|
+
- `issue-patterns.md` - Supported issue tracker patterns
|
|
167
|
+
- `pr-templates.md` - PR description templates
|
|
168
|
+
|
|
169
|
+
### Platform-Specific Note
|
|
170
|
+
|
|
171
|
+
Reference skill files in Kiro by accessing `.ai-rules/skills/pr-all-in-one/` directory.
|
|
172
|
+
|
|
125
173
|
## AUTO Mode
|
|
126
174
|
|
|
127
175
|
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
package/.ai-rules/adapters/q.md
CHANGED
|
@@ -119,6 +119,54 @@ Combine Q's AWS expertise with project rules:
|
|
|
119
119
|
- Let Q provide AWS-specific security guidance
|
|
120
120
|
- Apply `.ai-rules/agents/devops-engineer.json` for deployment patterns
|
|
121
121
|
|
|
122
|
+
## PR All-in-One Skill
|
|
123
|
+
|
|
124
|
+
Unified commit and PR workflow that:
|
|
125
|
+
- Auto-commits uncommitted changes (grouped logically)
|
|
126
|
+
- Creates or updates PRs with smart issue linking
|
|
127
|
+
- Supports multiple languages (en/ko/bilingual)
|
|
128
|
+
|
|
129
|
+
### Usage
|
|
130
|
+
|
|
131
|
+
```
|
|
132
|
+
/pr-all-in-one [target-branch] [issue-id]
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
**Examples:**
|
|
136
|
+
- `/pr-all-in-one` - PR to default branch, issue from branch name
|
|
137
|
+
- `/pr-all-in-one develop` - PR to develop branch
|
|
138
|
+
- `/pr-all-in-one PROJ-123` - PR with specific issue ID
|
|
139
|
+
- `/pr-all-in-one main PROJ-123` - PR to main with issue ID
|
|
140
|
+
|
|
141
|
+
### Configuration
|
|
142
|
+
|
|
143
|
+
Create `.claude/pr-config.json` in your project root. Required settings:
|
|
144
|
+
- `defaultTargetBranch`: Target branch for PRs
|
|
145
|
+
- `issueTracker`: `jira`, `github`, `linear`, `gitlab`, or `custom`
|
|
146
|
+
- `issuePattern`: Regex pattern for issue ID extraction
|
|
147
|
+
- `prLanguage`: `en`, `ko`, or `bilingual`
|
|
148
|
+
|
|
149
|
+
See `packages/rules/.ai-rules/skills/pr-all-in-one/configuration-guide.md` for all options.
|
|
150
|
+
|
|
151
|
+
### First-time Setup
|
|
152
|
+
|
|
153
|
+
If no config file exists, the skill guides you through interactive setup:
|
|
154
|
+
1. Select PR target branch
|
|
155
|
+
2. Choose issue tracker
|
|
156
|
+
3. Set PR description language
|
|
157
|
+
4. (Optional) Configure issue URL template
|
|
158
|
+
|
|
159
|
+
### Skill Files
|
|
160
|
+
|
|
161
|
+
- `SKILL.md` - Main workflow documentation
|
|
162
|
+
- `configuration-guide.md` - Detailed config options
|
|
163
|
+
- `issue-patterns.md` - Supported issue tracker patterns
|
|
164
|
+
- `pr-templates.md` - PR description templates
|
|
165
|
+
|
|
166
|
+
### Platform-Specific Note
|
|
167
|
+
|
|
168
|
+
Reference skill in Q chat by mentioning `.ai-rules/skills/pr-all-in-one/SKILL.md` file.
|
|
169
|
+
|
|
122
170
|
## AUTO Mode
|
|
123
171
|
|
|
124
172
|
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
@@ -1,10 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "Accessibility Specialist",
|
|
3
3
|
"description": "Accessibility expert for Planning, Implementation, and Evaluation modes - unified specialist for WCAG 2.1 AA compliance, ARIA attributes, and keyboard navigation",
|
|
4
|
-
"model": {
|
|
5
|
-
"preferred": "claude-sonnet-4-20250514",
|
|
6
|
-
"reason": "Suitable model for accessibility analysis"
|
|
7
|
-
},
|
|
8
4
|
"role": {
|
|
9
5
|
"title": "Accessibility Engineer",
|
|
10
6
|
"expertise": [
|
|
@@ -1,12 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "Act Mode Agent",
|
|
3
3
|
"description": "ACT mode agent - specialized for actual implementation execution",
|
|
4
|
-
|
|
5
|
-
"model": {
|
|
6
|
-
"preferred": "claude-sonnet-4-20250514",
|
|
7
|
-
"reason": "Suitable model for code implementation"
|
|
8
|
-
},
|
|
9
|
-
|
|
10
4
|
"role": {
|
|
11
5
|
"title": "Act Mode Agent",
|
|
12
6
|
"mode": "ACT",
|
|
@@ -31,13 +25,11 @@
|
|
|
31
25
|
"Apply accessibility and performance optimizations"
|
|
32
26
|
]
|
|
33
27
|
},
|
|
34
|
-
|
|
35
28
|
"context_files": [
|
|
36
29
|
".ai-rules/rules/core.md",
|
|
37
30
|
".ai-rules/rules/project.md",
|
|
38
31
|
".ai-rules/rules/augmented-coding.md"
|
|
39
32
|
],
|
|
40
|
-
|
|
41
33
|
"activation": {
|
|
42
34
|
"trigger": "🔴 **STRICT**: When user types 'ACT' or equivalent (Korean: 실행, Japanese: 実行, Chinese: 执行, Spanish: ACTUAR)",
|
|
43
35
|
"rule": "🔴 **STRICT**: ACT MODE request must activate this Agent automatically",
|
|
@@ -68,7 +60,6 @@
|
|
|
68
60
|
}
|
|
69
61
|
}
|
|
70
62
|
},
|
|
71
|
-
|
|
72
63
|
"workflow": {
|
|
73
64
|
"tdd_execution": {
|
|
74
65
|
"core_logic": "Red (failing test) → Green (minimal code) → Refactor (only after tests pass)",
|
|
@@ -82,7 +73,6 @@
|
|
|
82
73
|
"specialist_verification": "Reference Implementation Specialist Agents when needed (Architecture, Test Strategy, Performance, Security, Accessibility, SEO, Design System, Documentation, Code Quality)"
|
|
83
74
|
}
|
|
84
75
|
},
|
|
85
|
-
|
|
86
76
|
"mode_specific": {
|
|
87
77
|
"implementation_output": {
|
|
88
78
|
"step_by_step": "Show implementation progress with specific files created/modified",
|
|
@@ -91,13 +81,11 @@
|
|
|
91
81
|
"auto_return": "Automatically return to PLAN mode after implementation completes"
|
|
92
82
|
}
|
|
93
83
|
},
|
|
94
|
-
|
|
95
84
|
"delegate_agent": {
|
|
96
85
|
"primary": "frontend-developer",
|
|
97
86
|
"description": "This Mode Agent utilizes the Frontend Developer Agent's implementation workflow",
|
|
98
87
|
"integration": "Applies Frontend Developer Agent's TDD cycle and code quality checklist"
|
|
99
88
|
},
|
|
100
|
-
|
|
101
89
|
"tdd_cycle": {
|
|
102
90
|
"red_phase": {
|
|
103
91
|
"purpose": "Write failing test that defines expected behavior",
|
|
@@ -124,7 +112,6 @@
|
|
|
124
112
|
]
|
|
125
113
|
}
|
|
126
114
|
},
|
|
127
|
-
|
|
128
115
|
"quality_standards": {
|
|
129
116
|
"type_safety": "No any, unknown, or unsafe type bypasses",
|
|
130
117
|
"test_coverage": "90%+ for core logic, comprehensive for UI components",
|
|
@@ -133,12 +120,10 @@
|
|
|
133
120
|
"accessibility": "WCAG 2.1 AA compliance",
|
|
134
121
|
"performance": "Core Web Vitals optimization"
|
|
135
122
|
},
|
|
136
|
-
|
|
137
123
|
"communication": {
|
|
138
124
|
"style": "Execution-focused step-by-step progress reporting",
|
|
139
125
|
"format": "Clearly display implementation progress and quality verification results"
|
|
140
126
|
},
|
|
141
|
-
|
|
142
127
|
"verification_guide": {
|
|
143
128
|
"mode_compliance": [
|
|
144
129
|
"✅ Verify '# Mode: ACT' is displayed",
|
|
@@ -1,12 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "Agent Architect",
|
|
3
3
|
"description": "Primary Agent for creating, validating, and managing AI agent configurations",
|
|
4
|
-
|
|
5
|
-
"model": {
|
|
6
|
-
"preferred": "claude-sonnet-4-20250514",
|
|
7
|
-
"reason": "Balanced for schema design, meta-programming, and configuration tasks"
|
|
8
|
-
},
|
|
9
|
-
|
|
10
4
|
"role": {
|
|
11
5
|
"title": "AI Agent Framework Architect",
|
|
12
6
|
"type": "primary",
|
|
@@ -27,13 +21,11 @@
|
|
|
27
21
|
"Design specialized agents for specific domains"
|
|
28
22
|
]
|
|
29
23
|
},
|
|
30
|
-
|
|
31
24
|
"context_files": [
|
|
32
25
|
".ai-rules/rules/core.md",
|
|
33
26
|
".ai-rules/rules/augmented-coding.md",
|
|
34
27
|
".ai-rules/agents/README.md"
|
|
35
28
|
],
|
|
36
|
-
|
|
37
29
|
"activation": {
|
|
38
30
|
"trigger": "When user requests agent-related tasks: create agent, validate agent, audit checklist, manage agents",
|
|
39
31
|
"explicit_patterns": [
|
|
@@ -81,7 +73,6 @@
|
|
|
81
73
|
"documentation": "Agent added to README.md Quick Reference and Agent Details sections"
|
|
82
74
|
}
|
|
83
75
|
},
|
|
84
|
-
|
|
85
76
|
"workflow": {
|
|
86
77
|
"agent_creation": {
|
|
87
78
|
"approach": "TDD (Test-First)",
|
|
@@ -119,7 +110,6 @@
|
|
|
119
110
|
]
|
|
120
111
|
}
|
|
121
112
|
},
|
|
122
|
-
|
|
123
113
|
"modes": {
|
|
124
114
|
"planning": {
|
|
125
115
|
"description": "Planning new agent creation or modification",
|
|
@@ -149,7 +139,6 @@
|
|
|
149
139
|
]
|
|
150
140
|
}
|
|
151
141
|
},
|
|
152
|
-
|
|
153
142
|
"agent_schema_reference": {
|
|
154
143
|
"required_fields": [
|
|
155
144
|
"name: string - Agent display name",
|
|
@@ -170,7 +159,6 @@
|
|
|
170
159
|
"activation.explicit_patterns: string[] - Phrases that trigger this agent"
|
|
171
160
|
]
|
|
172
161
|
},
|
|
173
|
-
|
|
174
162
|
"code_quality_checklist": [
|
|
175
163
|
"✅ JSON Syntax: Valid JSON format",
|
|
176
164
|
"✅ Schema Compliance: All required fields present",
|
|
@@ -180,7 +168,6 @@
|
|
|
180
168
|
"✅ Naming Convention: kebab-case file name",
|
|
181
169
|
"✅ Consistency: Follows patterns from existing agents"
|
|
182
170
|
],
|
|
183
|
-
|
|
184
171
|
"communication": {
|
|
185
172
|
"style": "Systematic and clear approach, schema-driven design",
|
|
186
173
|
"approach": [
|
|
@@ -190,7 +177,6 @@
|
|
|
190
177
|
"Document all decisions and rationale"
|
|
191
178
|
]
|
|
192
179
|
},
|
|
193
|
-
|
|
194
180
|
"reference": {
|
|
195
181
|
"schema_location": "apps/mcp-server/src/rules/agent.schema.ts",
|
|
196
182
|
"existing_agents": ".ai-rules/agents/*.json",
|
|
@@ -1,12 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "AI/ML Engineer",
|
|
3
3
|
"description": "AI/ML expert for Planning, Implementation, and Evaluation modes - unified specialist for LLM integration, prompt engineering, RAG architecture, AI safety, and testing non-deterministic systems",
|
|
4
|
-
|
|
5
|
-
"model": {
|
|
6
|
-
"preferred": "claude-sonnet-4-20250514",
|
|
7
|
-
"reason": "Model optimized for AI/ML development guidance and code generation"
|
|
8
|
-
},
|
|
9
|
-
|
|
10
4
|
"role": {
|
|
11
5
|
"title": "Senior AI/ML Engineer",
|
|
12
6
|
"type": "primary",
|
|
@@ -63,13 +57,11 @@
|
|
|
63
57
|
"Follow augmented coding principles (Kent Beck)"
|
|
64
58
|
]
|
|
65
59
|
},
|
|
66
|
-
|
|
67
60
|
"context_files": [
|
|
68
61
|
".ai-rules/rules/core.md",
|
|
69
62
|
".ai-rules/rules/project.md",
|
|
70
63
|
".ai-rules/rules/augmented-coding.md"
|
|
71
64
|
],
|
|
72
|
-
|
|
73
65
|
"activation": {
|
|
74
66
|
"trigger": "🔴 **STRICT**: When AI/ML development is involved (LLM integration, RAG, prompt engineering), this Agent **MUST** be automatically activated",
|
|
75
67
|
"rule": "🔴 **STRICT**: When PLAN/ACT MODE involves AI/ML features, this Agent's workflow framework MUST be used",
|
|
@@ -181,7 +173,6 @@
|
|
|
181
173
|
]
|
|
182
174
|
}
|
|
183
175
|
},
|
|
184
|
-
|
|
185
176
|
"modes": {
|
|
186
177
|
"planning": {
|
|
187
178
|
"activation": {
|
|
@@ -529,7 +520,6 @@
|
|
|
529
520
|
}
|
|
530
521
|
}
|
|
531
522
|
},
|
|
532
|
-
|
|
533
523
|
"shared_framework": {
|
|
534
524
|
"llm_integration_patterns": {
|
|
535
525
|
"provider_abstraction": {
|
|
@@ -676,7 +666,6 @@
|
|
|
676
666
|
}
|
|
677
667
|
}
|
|
678
668
|
},
|
|
679
|
-
|
|
680
669
|
"code_quality_checklist": [
|
|
681
670
|
"LLM Integration: Provider abstraction with proper error handling",
|
|
682
671
|
"Prompt Safety: Injection prevention, input sanitization implemented",
|
|
@@ -689,7 +678,6 @@
|
|
|
689
678
|
"Streaming: Proper handling of streaming responses",
|
|
690
679
|
"Logging: Safe logging without PII exposure"
|
|
691
680
|
],
|
|
692
|
-
|
|
693
681
|
"tdd_cycle": {
|
|
694
682
|
"reference": "See augmented-coding.md 'TDD Cycle (Strict Adherence)' section",
|
|
695
683
|
"summary": "Follow Red -> Green -> Refactor cycle, adapted for AI",
|
|
@@ -701,7 +689,6 @@
|
|
|
701
689
|
"Mock LLM responses in CI/CD for determinism"
|
|
702
690
|
]
|
|
703
691
|
},
|
|
704
|
-
|
|
705
692
|
"ai_monitoring": {
|
|
706
693
|
"reference": "See augmented-coding.md 'AI Monitoring Checkpoints' section",
|
|
707
694
|
"ai_specific_warnings": [
|
|
@@ -714,7 +701,6 @@
|
|
|
714
701
|
"Over-complicated prompt chains"
|
|
715
702
|
]
|
|
716
703
|
},
|
|
717
|
-
|
|
718
704
|
"commit_rules": {
|
|
719
705
|
"reference": "See augmented-coding.md 'Commit Discipline' section",
|
|
720
706
|
"ai_specific": [
|
|
@@ -723,7 +709,6 @@
|
|
|
723
709
|
"Safety changes: Document security implications"
|
|
724
710
|
]
|
|
725
711
|
},
|
|
726
|
-
|
|
727
712
|
"communication": {
|
|
728
713
|
"approach": [
|
|
729
714
|
"Start by understanding AI/ML requirements context",
|
|
@@ -733,7 +718,6 @@
|
|
|
733
718
|
"Reference security best practices"
|
|
734
719
|
]
|
|
735
720
|
},
|
|
736
|
-
|
|
737
721
|
"file_naming": {
|
|
738
722
|
"patterns": {
|
|
739
723
|
"llm_client": "{provider}.client.{ext}",
|
|
@@ -768,7 +752,6 @@
|
|
|
768
752
|
}
|
|
769
753
|
}
|
|
770
754
|
},
|
|
771
|
-
|
|
772
755
|
"reference": {
|
|
773
756
|
"augmented_coding": {
|
|
774
757
|
"source": "augmented-coding.md",
|
|
@@ -1,10 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "Architecture Specialist",
|
|
3
3
|
"description": "Architecture expert for Planning, Implementation, and Evaluation modes - unified specialist for layer placement, dependency direction, and type safety",
|
|
4
|
-
"model": {
|
|
5
|
-
"preferred": "claude-sonnet-4-20250514",
|
|
6
|
-
"reason": "Suitable model for architecture analysis"
|
|
7
|
-
},
|
|
8
4
|
"role": {
|
|
9
5
|
"title": "Architecture Engineer",
|
|
10
6
|
"expertise": [
|