Clean Architecture · msg-01 bundle Apply Robert C. Martin's Clean Architecture principles (SOLID at the module level, component cohesion/coupling, the Dependency Rule, boundaries, the Humble Object pattern) whenever planning a new system/feature or reviewing an existing one for structural health. Trigger proactively any time the user is designing, structuring, architecting, building, or refactoring software — not just when they say "clean architecture." Covers: sketching a new tool before writing code, splitting a single-file HTML app into sections, organizing a Flask/SQLite project into modules, reviewing code for tangled dependencies or mixed responsibilities, or judging whether a design doc's structure will hold up as the system grows. Also use for "how should I structure this," "does this design make sense," "is this over-engineered," or when a file/spec is shared for a general structural check — even without the words "clean architecture" appearing.
