codingbuddy-rules 0.0.0-canary.20260106135414.7774b47 → 0.0.0-canary.20260107011320.2d16f78
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 +80 -0
- package/.ai-rules/adapters/claude-code.md +90 -0
- package/.ai-rules/adapters/codex.md +57 -0
- package/.ai-rules/adapters/cursor.md +56 -0
- package/.ai-rules/adapters/kiro.md +67 -1
- package/.ai-rules/adapters/opencode.md +91 -0
- package/.ai-rules/adapters/q.md +57 -0
- package/.ai-rules/agents/README.md +6 -0
- package/.ai-rules/agents/data-engineer.json +376 -0
- package/.ai-rules/agents/i18n-specialist.json +393 -0
- package/.ai-rules/agents/mobile-developer.json +355 -0
- package/.ai-rules/checklists/accessibility.json +132 -0
- package/.ai-rules/checklists/code-quality.json +97 -0
- package/.ai-rules/checklists/index.json +47 -0
- package/.ai-rules/checklists/performance.json +97 -0
- package/.ai-rules/checklists/security.json +119 -0
- package/.ai-rules/checklists/seo.json +97 -0
- package/.ai-rules/checklists/testing.json +97 -0
- package/.ai-rules/rules/core.md +186 -2
- package/.ai-rules/skills/api-design/SKILL.md +459 -0
- package/package.json +1 -1
|
@@ -187,6 +187,86 @@ AI: # Mode: EVAL
|
|
|
187
187
|
- ✅ Access to all specialist agent knowledge
|
|
188
188
|
- ✅ Easy to update: change `.ai-rules/` once, all tools benefit
|
|
189
189
|
|
|
190
|
+
## AUTO Mode
|
|
191
|
+
|
|
192
|
+
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
193
|
+
|
|
194
|
+
### Triggering AUTO Mode
|
|
195
|
+
|
|
196
|
+
Use the `AUTO` keyword (or localized versions) at the start of your message:
|
|
197
|
+
|
|
198
|
+
| Language | Keyword |
|
|
199
|
+
|----------|---------|
|
|
200
|
+
| English | `AUTO` |
|
|
201
|
+
| Korean | `자동` |
|
|
202
|
+
| Japanese | `自動` |
|
|
203
|
+
| Chinese | `自动` |
|
|
204
|
+
| Spanish | `AUTOMATICO` |
|
|
205
|
+
|
|
206
|
+
### Example Usage
|
|
207
|
+
|
|
208
|
+
```
|
|
209
|
+
User: AUTO 새로운 결제 시스템 기능 만들어줘
|
|
210
|
+
|
|
211
|
+
AI: # Mode: AUTO (Iteration 1/3)
|
|
212
|
+
## Phase: PLAN
|
|
213
|
+
[Following .ai-rules/rules/core.md workflow]
|
|
214
|
+
|
|
215
|
+
## Phase: ACT
|
|
216
|
+
[Execute with .ai-rules guidelines]
|
|
217
|
+
|
|
218
|
+
## Phase: EVAL
|
|
219
|
+
[Evaluate with quality criteria]
|
|
220
|
+
|
|
221
|
+
### Quality Status
|
|
222
|
+
- Critical: 0
|
|
223
|
+
- High: 0
|
|
224
|
+
|
|
225
|
+
✅ AUTO mode completed successfully!
|
|
226
|
+
```
|
|
227
|
+
|
|
228
|
+
### Workflow
|
|
229
|
+
|
|
230
|
+
1. **PLAN Phase**: Creates implementation plan with quality criteria
|
|
231
|
+
2. **ACT Phase**: Executes implementation following TDD workflow
|
|
232
|
+
3. **EVAL Phase**: Evaluates quality against exit criteria
|
|
233
|
+
4. **Loop/Exit**: Continues cycling until:
|
|
234
|
+
- Success: `Critical = 0 AND High = 0`
|
|
235
|
+
- Failure: Max iterations reached (default: 3)
|
|
236
|
+
|
|
237
|
+
### Antigravity-Specific Integration
|
|
238
|
+
|
|
239
|
+
AUTO mode works with Antigravity's task boundary tracking:
|
|
240
|
+
|
|
241
|
+
```python
|
|
242
|
+
task_boundary(
|
|
243
|
+
TaskName="AUTO: Feature Implementation",
|
|
244
|
+
Mode="AUTO_ITERATION",
|
|
245
|
+
TaskSummary="Iteration 1/3 - PLAN phase completed",
|
|
246
|
+
TaskStatus="Executing ACT phase",
|
|
247
|
+
PredictedTaskSize=30
|
|
248
|
+
)
|
|
249
|
+
```
|
|
250
|
+
|
|
251
|
+
### Configuration
|
|
252
|
+
|
|
253
|
+
Configure in `codingbuddy.config.js`:
|
|
254
|
+
|
|
255
|
+
```javascript
|
|
256
|
+
module.exports = {
|
|
257
|
+
auto: {
|
|
258
|
+
maxIterations: 3
|
|
259
|
+
}
|
|
260
|
+
};
|
|
261
|
+
```
|
|
262
|
+
|
|
263
|
+
### When to Use
|
|
264
|
+
|
|
265
|
+
- Large feature implementations requiring multiple refinement cycles
|
|
266
|
+
- Complex refactoring with quality verification
|
|
267
|
+
- Bug fixes needing comprehensive testing
|
|
268
|
+
- Code quality improvements with measurable criteria
|
|
269
|
+
|
|
190
270
|
## Maintenance
|
|
191
271
|
|
|
192
272
|
When updating rules:
|
|
@@ -450,3 +450,93 @@ Each workflow mode activates different specialist agents:
|
|
|
450
450
|
- **EVAL mode**: Security, accessibility, performance, and code quality specialists provide comprehensive review
|
|
451
451
|
|
|
452
452
|
**Important:** Specialists from one mode do NOT carry over to the next mode. Each mode has its own recommended specialist set.
|
|
453
|
+
|
|
454
|
+
## AUTO Mode
|
|
455
|
+
|
|
456
|
+
AUTO mode enables autonomous iteration through PLAN -> ACT -> EVAL cycles until quality criteria are met.
|
|
457
|
+
|
|
458
|
+
### Triggering AUTO Mode
|
|
459
|
+
|
|
460
|
+
Use the `AUTO` keyword (or localized versions) at the start of your message:
|
|
461
|
+
|
|
462
|
+
| Language | Keyword |
|
|
463
|
+
|----------|---------|
|
|
464
|
+
| English | `AUTO` |
|
|
465
|
+
| Korean | `자동` |
|
|
466
|
+
| Japanese | `自動` |
|
|
467
|
+
| Chinese | `自动` |
|
|
468
|
+
| Spanish | `AUTOMATICO` |
|
|
469
|
+
|
|
470
|
+
### Example Usage
|
|
471
|
+
|
|
472
|
+
```
|
|
473
|
+
AUTO implement user authentication with JWT tokens
|
|
474
|
+
```
|
|
475
|
+
|
|
476
|
+
```
|
|
477
|
+
자동 사용자 인증 기능을 JWT로 구현해줘
|
|
478
|
+
```
|
|
479
|
+
|
|
480
|
+
### Expected Behavior
|
|
481
|
+
|
|
482
|
+
1. **Initial PLAN**: Creates implementation plan with quality criteria
|
|
483
|
+
2. **ACT Iteration**: Executes implementation following TDD workflow
|
|
484
|
+
3. **EVAL Check**: Evaluates quality against exit criteria
|
|
485
|
+
4. **Loop or Exit**:
|
|
486
|
+
- If quality met (Critical=0, High=0): Exits with success summary
|
|
487
|
+
- If max iterations reached: Exits with failure summary and remaining issues
|
|
488
|
+
- Otherwise: Returns to PLAN with improvement focus
|
|
489
|
+
|
|
490
|
+
### Exit Criteria
|
|
491
|
+
|
|
492
|
+
- **Success**: `Critical = 0 AND High = 0` severity issues
|
|
493
|
+
- **Failure**: Max iterations reached (default: 3, configurable via `auto.maxIterations`)
|
|
494
|
+
|
|
495
|
+
### Configuration
|
|
496
|
+
|
|
497
|
+
Configure AUTO mode in `codingbuddy.config.js`:
|
|
498
|
+
|
|
499
|
+
```javascript
|
|
500
|
+
module.exports = {
|
|
501
|
+
auto: {
|
|
502
|
+
maxIterations: 3 // Default: 3
|
|
503
|
+
}
|
|
504
|
+
};
|
|
505
|
+
```
|
|
506
|
+
|
|
507
|
+
### AUTO Mode Output Format
|
|
508
|
+
|
|
509
|
+
```
|
|
510
|
+
# Mode: AUTO (Iteration 1/3)
|
|
511
|
+
|
|
512
|
+
## Phase: PLAN
|
|
513
|
+
[Planning content...]
|
|
514
|
+
|
|
515
|
+
## Phase: ACT
|
|
516
|
+
[Implementation content...]
|
|
517
|
+
|
|
518
|
+
## Phase: EVAL
|
|
519
|
+
[Evaluation content...]
|
|
520
|
+
|
|
521
|
+
### Quality Status
|
|
522
|
+
- Critical: 0
|
|
523
|
+
- High: 0
|
|
524
|
+
|
|
525
|
+
✅ AUTO mode completed successfully!
|
|
526
|
+
```
|
|
527
|
+
|
|
528
|
+
### When to Use AUTO Mode
|
|
529
|
+
|
|
530
|
+
- **Large feature implementations** that require multiple refinement cycles
|
|
531
|
+
- **Complex refactoring** where quality verification is critical
|
|
532
|
+
- **Bug fixes** that need comprehensive testing and validation
|
|
533
|
+
- **Code quality improvements** with measurable success criteria
|
|
534
|
+
|
|
535
|
+
### Differences from Manual Mode Flow
|
|
536
|
+
|
|
537
|
+
| Aspect | Manual Mode | AUTO Mode |
|
|
538
|
+
|--------|-------------|-----------|
|
|
539
|
+
| Transition | User triggers each mode | Automatic cycling |
|
|
540
|
+
| Iterations | Single pass per mode | Multiple cycles until quality met |
|
|
541
|
+
| Exit | User decides completion | Quality criteria or max iterations |
|
|
542
|
+
| Intervention | Required for each step | Only when requested or on failure |
|
|
@@ -147,3 +147,60 @@ Skills are located in `.ai-rules/skills/`. To use a skill:
|
|
|
147
147
|
- `subagent-driven-development` - In-session plan execution
|
|
148
148
|
- `dispatching-parallel-agents` - Handle parallel tasks
|
|
149
149
|
- `frontend-design` - Build production-grade UI
|
|
150
|
+
|
|
151
|
+
## AUTO Mode
|
|
152
|
+
|
|
153
|
+
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
154
|
+
|
|
155
|
+
### Triggering AUTO Mode
|
|
156
|
+
|
|
157
|
+
Use the `AUTO` keyword (or localized versions) at the start of your message:
|
|
158
|
+
|
|
159
|
+
| Language | Keyword |
|
|
160
|
+
|----------|---------|
|
|
161
|
+
| English | `AUTO` |
|
|
162
|
+
| Korean | `자동` |
|
|
163
|
+
| Japanese | `自動` |
|
|
164
|
+
| Chinese | `自动` |
|
|
165
|
+
| Spanish | `AUTOMATICO` |
|
|
166
|
+
|
|
167
|
+
### Example Usage
|
|
168
|
+
|
|
169
|
+
```
|
|
170
|
+
AUTO implement user authentication with JWT
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
### Workflow
|
|
174
|
+
|
|
175
|
+
1. **PLAN Phase**: Creates implementation plan with quality criteria
|
|
176
|
+
2. **ACT Phase**: Executes implementation following TDD workflow
|
|
177
|
+
3. **EVAL Phase**: Evaluates quality against exit criteria
|
|
178
|
+
4. **Loop/Exit**: Continues cycling until:
|
|
179
|
+
- Success: `Critical = 0 AND High = 0`
|
|
180
|
+
- Failure: Max iterations reached (default: 3)
|
|
181
|
+
|
|
182
|
+
### Copilot Integration
|
|
183
|
+
|
|
184
|
+
When using GitHub Copilot Chat with AUTO mode:
|
|
185
|
+
- Copilot references `.ai-rules/rules/core.md` for workflow
|
|
186
|
+
- Applies `.ai-rules/rules/augmented-coding.md` TDD principles
|
|
187
|
+
- Uses project structure from `.ai-rules/rules/project.md`
|
|
188
|
+
|
|
189
|
+
### Configuration
|
|
190
|
+
|
|
191
|
+
Configure in `codingbuddy.config.js`:
|
|
192
|
+
|
|
193
|
+
```javascript
|
|
194
|
+
module.exports = {
|
|
195
|
+
auto: {
|
|
196
|
+
maxIterations: 3
|
|
197
|
+
}
|
|
198
|
+
};
|
|
199
|
+
```
|
|
200
|
+
|
|
201
|
+
### When to Use
|
|
202
|
+
|
|
203
|
+
- Large feature implementations requiring multiple refinement cycles
|
|
204
|
+
- Complex refactoring with quality verification
|
|
205
|
+
- Bug fixes needing comprehensive testing
|
|
206
|
+
- Code quality improvements with measurable criteria
|
|
@@ -166,6 +166,62 @@ 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
|
+
## AUTO Mode
|
|
170
|
+
|
|
171
|
+
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
172
|
+
|
|
173
|
+
### Triggering AUTO Mode
|
|
174
|
+
|
|
175
|
+
Use the `AUTO` keyword (or localized versions) at the start of your message:
|
|
176
|
+
|
|
177
|
+
| Language | Keyword |
|
|
178
|
+
|----------|---------|
|
|
179
|
+
| English | `AUTO` |
|
|
180
|
+
| Korean | `자동` |
|
|
181
|
+
| Japanese | `自動` |
|
|
182
|
+
| Chinese | `自动` |
|
|
183
|
+
| Spanish | `AUTOMATICO` |
|
|
184
|
+
|
|
185
|
+
### Example Usage
|
|
186
|
+
|
|
187
|
+
```
|
|
188
|
+
AUTO implement user authentication feature
|
|
189
|
+
```
|
|
190
|
+
|
|
191
|
+
```
|
|
192
|
+
자동 사용자 인증 기능 구현해줘
|
|
193
|
+
```
|
|
194
|
+
|
|
195
|
+
When AUTO keyword is detected, Cursor calls `parse_mode` MCP tool which returns AUTO mode instructions.
|
|
196
|
+
|
|
197
|
+
### Workflow
|
|
198
|
+
|
|
199
|
+
1. **PLAN Phase**: Creates implementation plan with quality criteria
|
|
200
|
+
2. **ACT Phase**: Executes implementation following TDD workflow
|
|
201
|
+
3. **EVAL Phase**: Evaluates quality against exit criteria
|
|
202
|
+
4. **Loop/Exit**: Continues cycling until:
|
|
203
|
+
- Success: `Critical = 0 AND High = 0`
|
|
204
|
+
- Failure: Max iterations reached (default: 3)
|
|
205
|
+
|
|
206
|
+
### Configuration
|
|
207
|
+
|
|
208
|
+
Configure in `codingbuddy.config.js`:
|
|
209
|
+
|
|
210
|
+
```javascript
|
|
211
|
+
module.exports = {
|
|
212
|
+
auto: {
|
|
213
|
+
maxIterations: 3
|
|
214
|
+
}
|
|
215
|
+
};
|
|
216
|
+
```
|
|
217
|
+
|
|
218
|
+
### When to Use
|
|
219
|
+
|
|
220
|
+
- Large feature implementations requiring multiple refinement cycles
|
|
221
|
+
- Complex refactoring with quality verification
|
|
222
|
+
- Bug fixes needing comprehensive testing
|
|
223
|
+
- Code quality improvements with measurable criteria
|
|
224
|
+
|
|
169
225
|
## Reference
|
|
170
226
|
|
|
171
227
|
- [AGENTS.md Official Spec](https://agents.md)
|
|
@@ -122,9 +122,75 @@ 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
|
+
## AUTO Mode
|
|
126
|
+
|
|
127
|
+
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
128
|
+
|
|
129
|
+
### Triggering AUTO Mode
|
|
130
|
+
|
|
131
|
+
Use the `AUTO` keyword (or localized versions) at the start of your message:
|
|
132
|
+
|
|
133
|
+
| Language | Keyword |
|
|
134
|
+
|----------|---------|
|
|
135
|
+
| English | `AUTO` |
|
|
136
|
+
| Korean | `자동` |
|
|
137
|
+
| Japanese | `自動` |
|
|
138
|
+
| Chinese | `自动` |
|
|
139
|
+
| Spanish | `AUTOMATICO` |
|
|
140
|
+
|
|
141
|
+
### Example Usage
|
|
142
|
+
|
|
143
|
+
```
|
|
144
|
+
User: AUTO 새로운 컴포넌트 구현해줘
|
|
145
|
+
|
|
146
|
+
Kiro: # Mode: AUTO (Iteration 1/3)
|
|
147
|
+
## Phase: PLAN
|
|
148
|
+
[Follows .ai-rules/rules/core.md workflow]
|
|
149
|
+
|
|
150
|
+
## Phase: ACT
|
|
151
|
+
[Executes with quality standards from .ai-rules]
|
|
152
|
+
|
|
153
|
+
## Phase: EVAL
|
|
154
|
+
[Evaluates against quality criteria]
|
|
155
|
+
|
|
156
|
+
### Quality Status
|
|
157
|
+
- Critical: 0
|
|
158
|
+
- High: 0
|
|
159
|
+
|
|
160
|
+
✅ AUTO mode completed successfully!
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
### Workflow
|
|
164
|
+
|
|
165
|
+
1. **PLAN Phase**: Creates implementation plan with quality criteria
|
|
166
|
+
2. **ACT Phase**: Executes implementation following TDD workflow
|
|
167
|
+
3. **EVAL Phase**: Evaluates quality against exit criteria
|
|
168
|
+
4. **Loop/Exit**: Continues cycling until:
|
|
169
|
+
- Success: `Critical = 0 AND High = 0`
|
|
170
|
+
- Failure: Max iterations reached (default: 3)
|
|
171
|
+
|
|
172
|
+
### Configuration
|
|
173
|
+
|
|
174
|
+
Configure in `codingbuddy.config.js`:
|
|
175
|
+
|
|
176
|
+
```javascript
|
|
177
|
+
module.exports = {
|
|
178
|
+
auto: {
|
|
179
|
+
maxIterations: 3
|
|
180
|
+
}
|
|
181
|
+
};
|
|
182
|
+
```
|
|
183
|
+
|
|
184
|
+
### When to Use
|
|
185
|
+
|
|
186
|
+
- Large feature implementations requiring multiple refinement cycles
|
|
187
|
+
- Complex refactoring with quality verification
|
|
188
|
+
- Bug fixes needing comprehensive testing
|
|
189
|
+
- Code quality improvements with measurable criteria
|
|
190
|
+
|
|
125
191
|
## Getting Started
|
|
126
192
|
|
|
127
193
|
1. Ensure `.ai-rules/` directory exists with all common rules
|
|
128
194
|
2. Create `.kiro/rules/guidelines.md` with content above
|
|
129
195
|
3. Start a Kiro session - it will automatically reference common rules
|
|
130
|
-
4. Use PLAN/ACT/EVAL workflow as defined in `.ai-rules/rules/core.md`
|
|
196
|
+
4. Use PLAN/ACT/EVAL/AUTO workflow as defined in `.ai-rules/rules/core.md`
|
|
@@ -545,6 +545,97 @@ API 엔드포인트 구현
|
|
|
545
545
|
보안 취약점 검사
|
|
546
546
|
```
|
|
547
547
|
|
|
548
|
+
## AUTO Mode
|
|
549
|
+
|
|
550
|
+
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
551
|
+
|
|
552
|
+
### Triggering AUTO Mode
|
|
553
|
+
|
|
554
|
+
Use the `AUTO` keyword (or localized versions) at the start of your message:
|
|
555
|
+
|
|
556
|
+
| Language | Keyword |
|
|
557
|
+
|----------|---------|
|
|
558
|
+
| English | `AUTO` |
|
|
559
|
+
| Korean | `자동` |
|
|
560
|
+
| Japanese | `自動` |
|
|
561
|
+
| Chinese | `自动` |
|
|
562
|
+
| Spanish | `AUTOMATICO` |
|
|
563
|
+
|
|
564
|
+
### Example Usage
|
|
565
|
+
|
|
566
|
+
```bash
|
|
567
|
+
# Start AUTO mode
|
|
568
|
+
/agent plan-mode
|
|
569
|
+
AUTO 새로운 사용자 인증 기능을 만들어줘
|
|
570
|
+
```
|
|
571
|
+
|
|
572
|
+
### Workflow
|
|
573
|
+
|
|
574
|
+
1. **PLAN Phase**: Creates implementation plan with quality criteria (read-only)
|
|
575
|
+
2. **ACT Phase**: Executes implementation following TDD workflow (full permissions)
|
|
576
|
+
3. **EVAL Phase**: Evaluates quality against exit criteria (read-only)
|
|
577
|
+
4. **Loop/Exit**: Continues cycling until:
|
|
578
|
+
- Success: `Critical = 0 AND High = 0`
|
|
579
|
+
- Failure: Max iterations reached (default: 3)
|
|
580
|
+
|
|
581
|
+
### OpenCode Agent Integration
|
|
582
|
+
|
|
583
|
+
AUTO mode automatically switches between agents:
|
|
584
|
+
|
|
585
|
+
```
|
|
586
|
+
AUTO detected
|
|
587
|
+
↓
|
|
588
|
+
plan-mode agent (PLAN phase)
|
|
589
|
+
↓
|
|
590
|
+
act-mode agent (ACT phase)
|
|
591
|
+
↓
|
|
592
|
+
eval-mode agent (EVAL phase)
|
|
593
|
+
↓
|
|
594
|
+
[Check quality criteria]
|
|
595
|
+
↓
|
|
596
|
+
Loop or Exit
|
|
597
|
+
```
|
|
598
|
+
|
|
599
|
+
### Configuration
|
|
600
|
+
|
|
601
|
+
Configure in `codingbuddy.config.js`:
|
|
602
|
+
|
|
603
|
+
```javascript
|
|
604
|
+
module.exports = {
|
|
605
|
+
auto: {
|
|
606
|
+
maxIterations: 3
|
|
607
|
+
}
|
|
608
|
+
};
|
|
609
|
+
```
|
|
610
|
+
|
|
611
|
+
### AUTO Mode Output Format
|
|
612
|
+
|
|
613
|
+
```
|
|
614
|
+
# Mode: AUTO (Iteration 1/3)
|
|
615
|
+
|
|
616
|
+
## Phase: PLAN
|
|
617
|
+
[Planning with plan-mode agent...]
|
|
618
|
+
|
|
619
|
+
## Phase: ACT
|
|
620
|
+
[Implementation with act-mode agent...]
|
|
621
|
+
|
|
622
|
+
## Phase: EVAL
|
|
623
|
+
[Evaluation with eval-mode agent...]
|
|
624
|
+
|
|
625
|
+
### Quality Status
|
|
626
|
+
- Critical: 0
|
|
627
|
+
- High: 0
|
|
628
|
+
|
|
629
|
+
✅ AUTO mode completed successfully!
|
|
630
|
+
```
|
|
631
|
+
|
|
632
|
+
### When to Use
|
|
633
|
+
|
|
634
|
+
- Large feature implementations requiring multiple refinement cycles
|
|
635
|
+
- Complex refactoring with quality verification
|
|
636
|
+
- Bug fixes needing comprehensive testing
|
|
637
|
+
- Code quality improvements with measurable criteria
|
|
638
|
+
|
|
548
639
|
---
|
|
549
640
|
|
|
550
641
|
This guide ensures consistent, high-quality AI-assisted development using OpenCode/Crush with the `.ai-rules` system. All agents follow the same standards while leveraging OpenCode's powerful terminal-based interface.
|
package/.ai-rules/adapters/q.md
CHANGED
|
@@ -119,6 +119,63 @@ 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
|
+
## AUTO Mode
|
|
123
|
+
|
|
124
|
+
AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
|
|
125
|
+
|
|
126
|
+
### Triggering AUTO Mode
|
|
127
|
+
|
|
128
|
+
Use the `AUTO` keyword (or localized versions) at the start of your message:
|
|
129
|
+
|
|
130
|
+
| Language | Keyword |
|
|
131
|
+
|----------|---------|
|
|
132
|
+
| English | `AUTO` |
|
|
133
|
+
| Korean | `자동` |
|
|
134
|
+
| Japanese | `自動` |
|
|
135
|
+
| Chinese | `自动` |
|
|
136
|
+
| Spanish | `AUTOMATICO` |
|
|
137
|
+
|
|
138
|
+
### Example Usage
|
|
139
|
+
|
|
140
|
+
```
|
|
141
|
+
AUTO 새로운 Lambda 함수 만들어줘
|
|
142
|
+
```
|
|
143
|
+
|
|
144
|
+
### Workflow
|
|
145
|
+
|
|
146
|
+
1. **PLAN Phase**: Creates implementation plan with quality criteria
|
|
147
|
+
2. **ACT Phase**: Executes implementation following TDD workflow
|
|
148
|
+
3. **EVAL Phase**: Evaluates quality against exit criteria
|
|
149
|
+
4. **Loop/Exit**: Continues cycling until:
|
|
150
|
+
- Success: `Critical = 0 AND High = 0`
|
|
151
|
+
- Failure: Max iterations reached (default: 3)
|
|
152
|
+
|
|
153
|
+
### AWS Integration with AUTO Mode
|
|
154
|
+
|
|
155
|
+
Amazon Q's AWS expertise complements AUTO mode:
|
|
156
|
+
- Leverages Q's security scanning during EVAL phase
|
|
157
|
+
- Applies AWS best practices during ACT phase
|
|
158
|
+
- Uses Q's cost optimization suggestions in planning
|
|
159
|
+
|
|
160
|
+
### Configuration
|
|
161
|
+
|
|
162
|
+
Configure in `codingbuddy.config.js`:
|
|
163
|
+
|
|
164
|
+
```javascript
|
|
165
|
+
module.exports = {
|
|
166
|
+
auto: {
|
|
167
|
+
maxIterations: 3
|
|
168
|
+
}
|
|
169
|
+
};
|
|
170
|
+
```
|
|
171
|
+
|
|
172
|
+
### When to Use
|
|
173
|
+
|
|
174
|
+
- Large feature implementations requiring multiple refinement cycles
|
|
175
|
+
- Complex refactoring with quality verification
|
|
176
|
+
- AWS service integrations needing thorough testing
|
|
177
|
+
- Infrastructure as Code development with validation cycles
|
|
178
|
+
|
|
122
179
|
## Maintenance
|
|
123
180
|
|
|
124
181
|
1. Update `.ai-rules/rules/*.md` for universal changes
|
|
@@ -28,6 +28,8 @@ AI Agent definitions for specialized development roles.
|
|
|
28
28
|
| **Implementation Planning** | Technical Planner | `technical-planner.json` |
|
|
29
29
|
| **React/Next.js Development** | Frontend Developer | `frontend-developer.json` |
|
|
30
30
|
| **Backend API Development** | Backend Developer | `backend-developer.json` |
|
|
31
|
+
| **Database/Schema Design** | Data Engineer | `data-engineer.json` |
|
|
32
|
+
| **Mobile App Development** | Mobile Developer | `mobile-developer.json` |
|
|
31
33
|
| **Code Review (EVAL)** | Code Reviewer | `code-reviewer.json` |
|
|
32
34
|
| **Architecture Design** | Architecture Specialist | `architecture-specialist.json` |
|
|
33
35
|
| **Test Strategy** | Test Strategy Specialist | `test-strategy-specialist.json` |
|
|
@@ -36,6 +38,7 @@ AI Agent definitions for specialized development roles.
|
|
|
36
38
|
| **Accessibility Review** | Accessibility Specialist | `accessibility-specialist.json` |
|
|
37
39
|
| **SEO Optimization** | SEO Specialist | `seo-specialist.json` |
|
|
38
40
|
| **UI/UX Design** | UI/UX Designer | `ui-ux-designer.json` |
|
|
41
|
+
| **Internationalization** | i18n Specialist | `i18n-specialist.json` |
|
|
39
42
|
| **Documentation** | Documentation Specialist | `documentation-specialist.json` |
|
|
40
43
|
| **Code Quality** | Code Quality Specialist | `code-quality-specialist.json` |
|
|
41
44
|
| **Infrastructure/Deployment** | DevOps Engineer | `devops-engineer.json` |
|
|
@@ -50,6 +53,8 @@ AI Agent definitions for specialized development roles.
|
|
|
50
53
|
| Technical Planner | Low-level implementation planning with TDD and bite-sized tasks |
|
|
51
54
|
| Frontend Developer | TDD-based frontend development with React/Next.js |
|
|
52
55
|
| Backend Developer | Multi-stack backend API development (Node, Python, Go, Java, Rust) |
|
|
56
|
+
| Data Engineer | Database schema design, migrations, query optimization, analytics |
|
|
57
|
+
| Mobile Developer | Cross-platform (React Native, Flutter) and native (iOS, Android) development |
|
|
53
58
|
| Code Reviewer | Auto-activated in EVAL mode, multi-dimensional code quality assessment |
|
|
54
59
|
| Architecture Specialist | Layer boundaries, dependency direction, Clean Architecture |
|
|
55
60
|
| Test Strategy Specialist | TDD strategy, test coverage, test quality |
|
|
@@ -58,6 +63,7 @@ AI Agent definitions for specialized development roles.
|
|
|
58
63
|
| Accessibility Specialist | WCAG 2.1 AA, semantic HTML, screen reader support |
|
|
59
64
|
| SEO Specialist | Metadata, JSON-LD, Open Graph |
|
|
60
65
|
| UI/UX Designer | Visual hierarchy, UX laws, interaction patterns |
|
|
66
|
+
| i18n Specialist | Internationalization, translation key structure, RTL support |
|
|
61
67
|
| Documentation Specialist | Code comments, JSDoc, documentation quality assessment |
|
|
62
68
|
| Code Quality Specialist | SOLID, DRY, complexity analysis |
|
|
63
69
|
| DevOps Engineer | Docker, monitoring, deployment optimization |
|