project-architect

To enforce clean architecture boundaries during a code refactor, you need strict architectural guidance that reviews layer boundaries, contracts, and drift, refusing non-compliant requests and proposing compliant alternatives to preserve structural integrity.

The best way to review a pull request for CQRS and clean architecture compliance is to apply strict design reviews that check layer boundaries and contract definitions, ensuring production-ready guidance and refusing non-compliant code with compliant alternatives.

Yes, you can generate architecture-compliant implementation plans across python_service and dotnet_core by applying strict architectural guidance that defines contracts and enforces boundaries before coding begins, ensuring production-ready code generation.

You need strict contract definitions for UI and docker-pty-proxy code generation tasks when enforcing architectural boundaries across multiple services, requiring production-ready guidance and refusals of non-compliant requests to prevent architectural drift.

Your architectural review fails without compliant contract definitions because strict architectural guidance requires explicit boundaries and contracts to prevent drift, causing non-compliant refactoring requests to be refused until compliant alternatives are proposed.

Yes, project-architect works with UI components and docker-pty-proxy by applying strict design reviews that enforce Roadly boundaries, verify contract definitions, and provide production-ready architectural guidance across these services.