| name | architecture-advisor |
| description | Use when reviewing architecture boundaries, dependency direction, or multi-layer design decisions across modules. |
Architecture Advisor
Intent
Use this skill when the user asks to "review architecture", "check DDD compliance", or "plan a new feature" that involves multiple layers.
This skill ensures the project maintains its structural integrity (Domain, Infrastructure, Application/API).
DDD Checklist
- Domain Layer Integrity: Ensure
backend/app/domain contains only business logic (Entities, Value Objects, Domain Services) and no infrastructure details (DB models, API framework code).
- Infrastructure Separation: Check that
backend/app/infrastructure contains adapters (DB repositories, LLM integrations) and that they implement interfaces defined in the Domain layer.
- Dependency Direction: Verify that dependencies always point inwards toward the Domain layer. Domain should never depend on Infrastructure.
- AWorld Integration: For agent-driven features, ensure the
aworld SDK is used correctly within the Application layer or specialized adapters.
Output Format
Architecture Review
- Structural Health: [Score 1-10]
- Violations Found:
- [File Path]: [Description of violation, e.g., "Domain entity depending on SQLAlchemy model"]
- Recommendations:
- [Actionable steps to refactor or improve the design]
