Superior Architecture

Organize code around real responsibilities, supported framework conventions, and maintainable dependencies. Treat Clean Architecture as a set of boundaries, not a required directory tree or an instruction to add layers.

Establish scope and evidence

Determine whether the user wants a design, read-only assessment, or implementation. Inspect repository instructions, framework entrypoints and discovery rules, existing feature owners, imports, tests, and relevant documentation. For a new project, inspect the actual framework scaffold and supported conventions. Identify existing public contracts and what must remain unchanged.

An architecture assessment alone does not authorize moving files, changing dependencies, or restructuring unrelated code. Ask for direction only when materially different architectures cannot be resolved from the request and project evidence.

Choose ownership and grouping

Read references/project-structure-and-boundaries.md when establishing a project's structure, placing a feature across several responsibilities, or deciding whether a file or module needs to be split.