conceptual-integrity
Keeps a codebase converging instead of piling up: one kind of thing, one path. Traces the shared need behind scattered code, fixes disagreements at their source instead of compensating downstream, finishes migrations by deleting the old path, and makes the call instead of hedging with flags, fallbacks, wrappers, and parallel implementations. Use when planning or designing a feature, refactoring, adding an entry point, integration, provider, or capability, reviewing a plan, design doc, or diff, deciding which tests to add or delete, syncing with an upstream codebase, or when the user asks for conceptual integrity, a unified architecture, maintainability, less tech debt, fewer special cases, or no more patch pile-up. Not for one-line fixes or non-coding requests.
