gk-architect

To set up an architecture constitution for a new web application, define the tech stack, folder structure, and testing philosophy before development starts. This ensures the agent does not default to unconsidered or inconsistent patterns during the build.

You can prevent agentic drift by applying the O'Reilly principle of architecture-before-spec to define technical constraints and structural patterns upfront. This maintains high code quality standards and stops inconsistent coding patterns.

The best way to standardize folder structure and naming conventions is by generating a canonical ARCHITECTURE.md file. This document serves as the agent's constitution, enforcing adherence to established architectural patterns throughout the project.

Yes, you need an architecture specification before scaffolding a backend application to define state management and structural patterns. Forcing this definition before implementation prevents architectural drift and inconsistent coding.

To enforce architectural governance, integrate review processes that check every task against the established architectural patterns defined in your constitution. This ensures every task adheres to the defined structural patterns and technical constraints.