pre-generation-arch-check

To prevent architectural drift before code generation, you can run a pre-generation architecture check to validate proposed file changes against project-wide separation of concerns and orchestration rules. This detects anti-patterns early in the planning phase.

Separation of concerns in code architecture compliance is a rule that prevents overlapping modifications, such as editing an agent's core logic and a skill's configuration simultaneously. Pre-generation linting flags these violations to ensure changes route through the correct workflow.

You can lint proposed file changes by running a pre-generation architecture check that validates task summaries and file modifications against established agent, skill, and guide directory structures to prevent unauthorized modifications.

Yes, pre-generation architecture linting works for multi-agent orchestration by validating that orchestrator delegation rules are followed. It checks proposed changes to ensure tasks are routed correctly and structural integrity is maintained across directories.

Unauthorized file modifications are flagged during the planning phase to enforce architectural integrity and compliance before any code is generated. This prevents structural violations across agent, skill, and guide directories by ensuring changes follow established workflows.