| name | review-architecture |
| description | Architecture-focused monorepo review. USE WHEN: user runs /review-architecture or explicitly asks for this review. DO NOT USE WHEN: implementing features or fixing bugs unless the user asked for a review.
|
| disable-model-invocation | true |
Review architecture
Run an architecture-focused review of the monorepo: layout, workspace dependencies, Turborepo task graph, app vs package boundaries, dependency direction, and module coupling/cohesion. Your reply must be a plan of suggested changes: concise, actionable, and structured-not only prose.
Invocation
Text after the slash command is additional scope/focus - narrow the review accordingly. If none given, use the default scope described below.
Best practices alignment
- Dependency direction - Apps depend on packages; packages must not depend on apps. No circular dependencies between workspaces.
- Single responsibility - Each package has one clear purpose (e.g.
@repo/dtos-common, @repo/enums-common, @repo/typescript-config).
- Public API surface - Packages expose a minimal, stable API via barrel exports; internal modules are not re-exported unless intentional.
- Turborepo - Task graph is acyclic; cache boundaries and
dependsOn are correct; no redundant or missing tasks.
- Root scripts - Single pnpm entry point for common operations; package scripts + turbo filters for scoped work; port allocation is documented and consistent.
Align with root AGENTS.md and app-level AGENTS.md for stated architecture and naming.
