micro-optimiz

name

micro-optimiz

description

Daily micro-refactoring. Each round is one small, behavior-preserving diff that raises code quality — deleting dead code, merging duplication into one generic helper, flattening control flow, purifying functions, fixing error paths, uniformizing names, separating concerns — never a big refactoring. Changes too large for one round are sliced into a ledger and done over several rounds. Use when the user asks to optimize, simplify, refactor, reduce complexity, clean up, or shrink code; asks to improve a function's design, make code more generic or reusable, or remove a flag/boolean parameter; mentions dead code, duplication, error handling, naming, SOLID, readability, maintainability, or a daily/recurring cleanup pass. Also triggers on a single pasted function or snippet the user asks to simplify, clean, or improve — small input still goes through the catalog, not ad-hoc advice. Not for adding features, performance tuning, or swapping libraries.

micro-optimiz — daily complexity reduction

Run this every day and the codebase gets simpler every day. Each round makes the targeted code measurably lighter: fewer lines, less nesting, fewer concepts to hold in mind. Deletion is the best refactoring; the second best is replacing imperative plumbing with a composed expression.

Goal per round

A round succeeds when at least one of these moved in the right direction, with behavior unchanged:

• Lines of code — dead code deleted, duplication merged, boilerplate collapsed into an expression.
• Complexity — nesting flattened, branches removed, state variables eliminated, control flow made linear.
• Design — a function or class reshaped so its structure matches its purpose (see "Design moves" below).

Two hard limits:

1. Behavior preservation — the result must be verifiably equivalent.
2. Round budget — one round is one small reviewable diff: ≤ ~50 changed lines, ≤ 2 files (the target plus its direct callers), . A change that cannot fit is not done bigger — it is (). Never let a round grow into a big refactoring "since we're at it".