abstraction-judgment

What problem does it solve?

This Skill helps developers make better decisions about when and how to introduce abstractions, preventing over-engineering and promoting maintainable code.

Core Features & Use Cases

• Guidance on Abstraction: Provides clear rules and signals for when to extract shared code, create base classes, or build framework layers.
• Avoids Premature Abstraction: Emphasizes writing concrete code first and abstracting only when patterns are stable and the benefit is clear.
• Use Case: When a developer is unsure whether to create a new utility function after seeing a piece of code repeated twice, this Skill can guide them to wait until a third instance validates the pattern before abstracting.

Quick Start

Use the abstraction-judgment skill to evaluate if a newly observed code pattern should be extracted into a shared utility.