Architecture Session Review

Use this skill to make architecture thinking useful during coding work. The goal is not to summarize architecture theory. The goal is to turn architectural concerns into better implementation choices, concrete verification, and clear decision notes.

Core Workflow

1. Inspect the live code, repo guidance, current behavior, and any user supplied issue or design context before judging the architecture.
2. Classify the scope of the change as local code, module, component, service, data boundary, deployment unit, or enterprise integration.
3. Identify the top quality attributes that matter for this task. Prefer three or fewer unless the user asks for a broad review.
4. Map the relevant boundaries: components, dependencies, public contracts, data ownership, runtime communication, and deployment constraints.
5. Choose the smallest useful architecture pass:
   1. Light pass for one file, one function, or a narrow refactor.
   2. Standard pass for cross module changes, shared abstractions, public APIs, data access, or important tests.
   3. Deep pass for service boundaries, storage ownership, architecture style choices, migration plans, operational behavior, or decisions that should be recorded.
6. Implement the change in the style of the repo, keeping edits scoped.
7. Convert each important concern into a verification step. Prefer executable checks over opinions.
8. Finish with changed files, checks run, decision summary, and remaining risk.

Architectural Significance Filter