brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
brooks-auditArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architect…
Independent GitHub snapshot · Automated classification · Original documentation governs
Read in order:
../_shared/common.md — Iron Law, Project Config, Report Template, Health Score../_shared/source-coverage.md — book coverage, exceptions, tradeoffs../_shared/decay-risks.md — symptom definitions and source attributionsarchitecture-guide.md (this directory) — the audit frameworkOnboarding mode: If the user asks for an onboarding report, codebase tour, or
"explain this codebase to a new developer", read onboarding-guide.md from this
directory and follow it instead of architecture-guide.md. This mode explains rather
than diagnoses — no Health Score, no Iron Law findings.
Scope: if the user did not specify files or a directory, apply Auto Scope Detection
(../_shared/common.md) first.
Mode line in report: Architecture Audit