simplify

Understand the code's responsibility, callers, and edge cases first, then apply one simplification at a time. After each change, verify that outputs, error behavior, and side effects remain identical using tests or a proportionate final-state verification plan.

Common signals include deep nesting, long functions with mixed responsibilities, nested ternaries, boolean flag arguments, repeated conditionals, misleading names, duplicated logic, dead code, and wrappers that add no value.

Avoid simplifying code you do not yet understand, code that is already clean, performance-critical paths where the simpler version is measurably slower, and modules you are about to rewrite entirely.

Yes, the guidance explicitly favors straightforward TypeScript over clever compression, explicit names, and smaller focused helpers. It also requires matching existing project conventions for imports, naming, error handling, and type annotations.

Run the checks required by the repository and release instructions against the final diff, and confirm outputs, error handling, and side effects are unchanged. Add extra evidence only when the changed scope or a stated uncertainty warrants it.