code-simplifier

Apply behavior-preserving transformations such as early returns to flatten nesting, removing redundant wrapper functions, and clarifying variable names. Verify that outputs, interfaces, timing, and edge-case handling remain identical after each change.

Replace nested conditionals with early returns: check each failure condition at the top of the function and return immediately, leaving the main logic at the top indentation level. This flattens the code and makes the happy path easier to follow.

Avoid simplification when it reduces clarity, merges unrelated responsibilities into one function, removes valuable abstractions, or makes debugging harder. Also avoid touching Markdown, JSON, YAML, or prompt files, where wording itself is often functional.

Proper refactoring never changes public interfaces, business rules, or observable behavior. It only restructures the internal implementation, so all callers, outputs, and boundary conditions continue to work exactly as before.

Simplifying prioritizes readability and maintainability, while shortening only reduces line count. Overly compact code like nested ternaries or dense one-liners is often harder to debug, so clarity should always take precedence over brevity.