minimal-abstractions

Before adding a new abstraction (interface, abstract class, wrapper, layer), ask:

If any answer is "no" or "maybe" → Don't add it. Use the simplest solution that works.

Abstractions are not free - every interface, wrapper, layer, or pattern adds:

Evaluates and prevents unnecessary abstractions by analyzing interfaces, layers, and patterns against concrete requirements. Use when evaluating new abstractions, reviewing architecture proposals, detecting over-engineering, or simplifying existing code. Triggers on "is this abstraction necessary", "too many layers", "simplify architecture", "reduce complexity", "over-engineered", "do we need this interface", or when reviewing design patterns. Source: dawiddutoit/custom-claude.