desloplisted

# Deslop Make code feel deliberate and easy to understand quickly. The default mode is review-first: show the user the current pipeline, the proposed style, and concrete before/after examples before changing files. Do not apply edits until the user approves the style, unless the user explicitly says to apply immediately. > **Companion skill:** `deslop` makes code *readable* (naming, ordering, splitting for clarity); `deslop-v2` makes it *lean* (removing over-engineering — pass-through wrappers, `??` confetti, nested ternaries, grab-bag returns, and over-nested folders/packages). If the real problem is too much abstraction or structure rather than unclear naming, use `deslop-v2`. When both apply, deslop-v2 removes the excess first, then deslop names what remains. ## Core Contract Optimize for a developer understanding the important path in about 5 seconds: ```txt entrypoint -> data/load step -> transformation -> side effect -> UI/output ``` Good deslop work may rename symbols, reorder imports, move files, split or inline functions, extract React hooks, remove pointless hooks, rename folders, flatten render branches, or simplify module boundaries. The measure is readability of the pipeline, not blindly adding abstractions. ## Style source (read first) Before proposing any style, read the repo's own style guide if it exists: `CODE-STYLE.md` (the SSOT) and the `## Conventions` digest in `AGENTS.md`. When present, they are the **authoritative target style** for this repo