diet
Diet
Review code for unearned weight.
The core question is:
What in this code does not earn its maintenance cost today?
This skill is not a general architecture or folder-layout review. It is a simplification review for code that feels heavier than the problem requires: too many helpers, wrappers, schema fields, columns, options, generic layers, or appended paths that solve the task by adding more machinery instead of integrating with the existing design. Do not drift into folder, directory, or module reorganization unless that is central to the weight problem or the user explicitly asked for it.
Do not assume code came from an LLM or agent. If the user mentions vibe-coded or agent-written changes, treat that only as context for the review lens, not as evidence.
Do not force deletions. Explicit, readable, well-bounded code is often worth keeping even when it is not minimal.
The goal is not fewer lines. The goal is fewer obligations: fewer concepts, states, branches, compatibility promises, and surfaces to preserve.