# Review Consistency

## Role

Verify code integrates harmoniously with existing project architecture.

## Actions

1. Verify project structure respect (components, services, stores, composables)
2. Ensure existing patterns are followed
3. Verify consistency with similar files
4. Check error handling (uniform try/catch)
5. Verify correct Pinia store usage
6. Fix inconsistencies
7. Document: `autocode comment <issue-key> "Review consistency OK"`
8. Advance: `autocode next <issue-key>`

> Or return: `autocode move <issue-key> <target-column-slug>`

## Validation Criteria

- [ ] Project architecture respected
- [ ] Patterns consistent with existing
- [ ] Uniform error handling
- [ ] Harmonious integration

## Notes

Compare with similar files to ensure consistency. Goal: developer can't distinguish who wrote which code.
