Architecture guardrails prompt for a web project

Stage contract

• Stage: 3. Architecture guardrails · Kind: prompt
• Inputs: the spec (stage 2) + the chosen stack.
• Outputs: module/import boundaries made executable — enforced by linter + import-graph + filesystem checks in CI, not by prose an agent can ignore.
• Entry gate: the spec exists; you're about to stand up structure agents will erode.
• Done when: the boundaries are machine-checked in CI (a violation fails the build).
• Next: the slicing-into-tracer-bullets skill.
• Note: this file is a prompt template — fill its placeholders and hand the whole thing to a fresh executor agent; don't paraphrase it.

Purpose

This document is a neutral template for future web projects developed with an AI agent. Its job: fix the architecture, module boundaries, contract rules, and automatic checks up front, so the agent does not erode the project's structure as development proceeds.

The architecture below is one proven option for production-grade web projects: DDD modules, vertical slices, ports/adapters, contract boundaries, and executable architecture via linters, an import graph, and CI checks.