Origem: D:/Documents/Github/transcript Arquivos omitidos (segredos, bancos de dados, logs, >50 MB): 2
36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
# Multi-agent development pipeline
|
|
|
|
Goal: ship UI changes with high design quality, code quality, and the least code that works.
|
|
|
|
## Phases
|
|
|
|
1. **Scope framer — `product-framer`**
|
|
- Convert the request into a short fix ledger: issue, acceptance criteria, files, out-of-scope.
|
|
- Output: checklist only; no code.
|
|
|
|
2. **Design quality — `ui-art-director` + `ux-critic`**
|
|
- Validate hierarchy, density, typography, motion, and user flow.
|
|
- Cut changes that do not improve the user's experience.
|
|
|
|
3. **Minimal code preflight — `code-reviewer`**
|
|
- Find existing patterns and the shortest safe implementation path.
|
|
- Reject new dependencies and speculative abstractions.
|
|
|
|
4. **Implementation — `frontend-craftsperson`**
|
|
- Implement one focused batch at a time.
|
|
- Add the smallest tests that prove behavior.
|
|
- Reuse tokens and existing DOM helpers.
|
|
|
|
5. **Final 3-agent review**
|
|
- `visual-qa`: visual regressions and missed UX criteria.
|
|
- `accessibility-reviewer`: keyboard, focus, labels, motion, semantics.
|
|
- `code-reviewer`: correctness, maintainability, unnecessary code.
|
|
|
|
6. **Fix loop**
|
|
- Send only blocking review findings back to `frontend-craftsperson`.
|
|
- Rerun the same 3-agent final review once.
|
|
|
|
## Default rule
|
|
|
|
If two solutions work, choose the one with fewer files, fewer branches, and no dependency changes.
|