DRY Violation Detector FAQs

Question 1

Why is 'searching first' emphasized over refactoring later?

Accepted Answer

Searching first takes seconds and prevents technical debt from entering the codebase, whereas 'refactoring later' is often delayed indefinitely, leading to permanent maintenance overhead.

Question 2

What is a DRY violation in software development?

Accepted Answer

A DRY (Don't Repeat Yourself) violation occurs when knowledge or logic is duplicated within a system, making maintenance difficult and increasing the risk of inconsistent behavior when changes are made.

Question 3

What common patterns does the DRY Violation Detector look for?

Accepted Answer

It specifically looks for hardcoded arrays that duplicate enums, string literals that should be enum values, and validation logic duplicated across controllers and services.

Question 4

Can this skill distinguish between UI-specific and domain logic?

Accepted Answer

Yes, it provides a decision matrix to determine if a logic grouping is a domain concept that should be centralized or a one-off filter that is acceptable to inline.

Question 5

How does this skill help prevent code duplication?

Accepted Answer

It implements a search-first protocol that requires checking for existing enums, constants, and domain types before any new implementation, ensuring developers reuse existing structures.

DRY Violation Detector

Key Features

Use Cases

DRY Violation Detector

Key Features

Use Cases