abstraction-judgment

Extract shared code only when patterns are stable and the benefit is clear, typically after a third instance validates the pattern. This approach prevents premature generalization and reduces cognitive overhead in software design.

Failure signals of over-abstraction include premature generalization and increased cognitive overhead. This skill identifies these signals to help developers avoid building unnecessary framework layers and maintain code quality.

The Rule of Three guides code refactoring by suggesting developers wait until a piece of code is repeated a third time before abstracting it. This validates the pattern and ensures the abstraction improves maintainability.

To avoid premature generalization, write concrete code first and abstract only when the pattern is stable. Evaluate whether creating base classes or framework layers provides a clear benefit before introducing new abstractions.

If a code pattern is repeated twice, you likely do not need an abstraction yet. This skill advises waiting until a third instance appears to validate the pattern before extracting shared code or creating base classes.

Yes, this skill evaluates newly observed code patterns to determine if they should be extracted into shared utilities. It provides rules and signals to prevent over-engineering and promote maintainable code.