kiss_skill

Overview

This skill enforces the KISS principle: prefer the simplest solution that works. It helps you avoid clever one-liners, over-abstraction, and premature optimization so code is readable, maintainable, and debuggable. Use it when complexity creeps in or when you feel tempted to show off.

How this skill works

The skill inspects code for "clever" smells: long chained operations, nested ternaries, dense regex, one-liners, and solutions that require explanation. It recommends replacing them with obvious steps: named intermediate variables, simple loops or if/else blocks, and clear constants. It also provides quick responses to common pressures that push complexity.

When to use it

• When a solution feels complex or hard to explain
• When you’re tempted to write a clever one-liner
• When multiple approaches are possible and you’re choosing for style
• When using advanced patterns for a simple problem
• During code reviews to enforce readability standards

Best practices

• Choose one clear implementation and avoid multiple alternatives in the same code path
• Name intermediate values so intent is explicit
• Prefer explicit control flow (for/if) over nested ternaries and dense chains
• Avoid complex regex; break checks into readable steps
• Optimize only after profiling shows a real need

Example use cases

• Refactoring a long chained array transformation into named steps for clarity
• Replacing a terse functional one-liner with a simple loop that a junior dev can follow
• Pushing back in a code review when a PR includes clever but unreadable code
• Deciding not to apply a design pattern that hides intent for a small feature
• Converting a regex-heavy validation into explicit checks when maintainability matters