Django ORM Architecture Review
When To Use
- The main decision is about Django model design, queryset optimization, migration safety, or transaction boundaries.
- Reviewing N+1 query behavior, model fatness, or data migration strategy.
Workflow
- Identify the model structure — field types, relationships, indexes, and constraints.
- Review queryset patterns — select_related, prefetch_related, and annotate usage.
- Check for N+1 query patterns in serializers, templates, or DRF views.
- Review manager and queryset design — custom managers, chaining, and reuse.
- Check transaction boundaries —
atomic()blocks and transaction per request. - Review migration safety — data migrations, lock risks, and long-running migrations.
- Recommend the smallest structural change that improves performance or maintainability.
Output Format
Django ORM review:
- Model structure:
- Queryset patterns:
- N+1 analysis:
- Manager design:
- Transaction boundaries:
- Migration safety:
- Recommended change:
- Verification:
Source: WangYao-GoGoGo/architecture-agent-skills — distributed by TomeVault.