tomevault-io Django App Architecture Review
When To Use
- The main decision is about Django project layout, app boundaries, model design, or queryset optimization.
- Reviewing signal chains, migration strategies, or serializer/view responsibilities.
Workflow
- Identify Django app boundaries and whether they follow domain ownership or technical layers.
- Review model design — field types, indexes, constraints, and relationship direction.
- Check view and serializer responsibilities — are they handling HTTP or also domain logic?
- Review signal chains for ordering, side effects, and failure behavior.
- Check querysets for N+1 queries and unnecessary database work.
- Review migration strategy — are squashed migrations and data migrations planned?
- Recommend the smallest change that clarifies boundaries or reduces risk.
Output Format
Django architecture review:
- App boundaries:
- Model design:
- View & serializer responsibilities:
- Signal risks:
- Query performance:
- Migration strategy:
- Recommended change:
- Verification:
Source: WangYao-GoGoGo/architecture-agent-skills — distributed by TomeVault.