YAGNI
Avoid implementing capabilities before a current requirement justifies them.
Use this when The proposed change adds extension points and configuration with no current consumer.
without the term
“You added a plugin system, three config options, and an abstract base class for a feature that only needs to do one thing. Can you take out the stuff we don't need yet?”
with the term · How do you ask a model for YAGNI?
Apply YAGNI to this change. Remove speculative capabilities while preserving today’s requirements, validation, and failure handling.
What is YAGNI?
YAGNI stands for You Aren't Gonna Need It. Build what the current requirement needs, including its validation and error handling, and leave hypothetical variations out.
Why does YAGNI matter when vibe coding?
Generated abstractions can make a small feature harder to understand.
How do you do YAGNI?
Separate required behavior from hypothetical future variation and implement the required part.
What goes wrong with YAGNI?
Calling necessary error handling or access checks speculative work.