role-architect

To design technical architecture, define system layers, modules, boundaries, and directory structures to ensure clarity and maintainability. This involves specifying data models, API contracts, and internal module responsibilities for inter-module communication.

Establishing code conventions requires defining naming rules, patterns, and best practices for your code structure. You can enforce these standards by operating in a dedicated Convention mode to identify violations across the codebase.

Identifying technical risks and trade-offs involves evaluating architectural decisions against system requirements like scalability and maintainability. A Software Architect Agent assesses these factors to highlight potential issues before implementation.

Yes, you can define API contracts and data models specifically for inter-module communication. This specifies how modules interact and ensures consistent data exchange across system boundaries.

Yes, designing a new microservice architecture from scratch is a supported use case. You can define the service's API, data storage, internal module responsibilities, and directory structure to ensure a scalable design.

Reviewing code structure for violations involves operating in Code Review mode to identify deviations from established patterns. This checks the codebase against defined conventions, boundaries, and interface contracts.