keep-it-simple

What problem does it solve?

This skill helps teams avoid premature abstractions and over-engineering by guiding when to add abstractions and when to keep things simple, emphasizing YAGNI.

Core Features & Use Cases

• Enforces YAGNI principles before creating factories, abstract base classes, or config-driven features.
• Provides decision checks like the 3-case rule and explicit criteria to avoid unnecessary complexity.
• Use Case: When evaluating a new abstraction, verify whether there are 3 concrete usages before abstracting; otherwise implement a simple solution.

Quick Start

When planning new abstractions, ask if you have 3+ concrete use cases and implement the simplest working solution first.