Coding Architecture

Improve maintainability without turning a focused change into an architecture project.

Scope and precedence

• Follow the user's request and repository instructions before this skill's preferences.
• Preserve the project's established framework, design system, directory conventions, state approach, and test strategy unless changing them is requested or concretely necessary.
• Prefer the smallest cohesive change that satisfies the request and preserves behavior. Do not reorganize unrelated modules.
• Treat the guidance below as decision criteria, not a requirement to introduce every listed pattern.

Decide in this order

Use this as a decision preference, not a mandatory pipeline:

Reuse → Compose → Extract → Abstract