deslop-uilisted

# Deslop UI Slop is predictable, uncommitted design—not merely ugly design. Audit observable surface, structure, and voice against a brief; repair with a specific, verifiable choice. ## Repair order and evidence contract 1. Establish brief, preserved signals, and artifact; record surface, structural, and verbal findings separately. 2. Cite a selector, section, phrase, screenshot, or browser observation; assign P0–P3. 3. Choose a brief-bound named direction, prescribe repairs, and reinspect the same views. `n/a` requires an absent subject. Stop before changing a coherent brief-supported brand choice; ask for direction when the brief or acceptance criteria are absent. ## Diagnose cause, then tell Make two passes: **intent** (job, audience, hierarchy, retained signals, claimed signature) and **behavior** (rendered first view, section transitions, narrow view; trace code to selector/token or name screenshot geometry). Then ask whether replacing the suspect with a neutral version changes meaning or task performance. Preserve a documented functional pill, gradient, table, or system font; repair its implementation, not its role. Rank P0 meaning/interaction/accessibility/fact, P1 direction/hierarchy, P2 repeated default, then P3 polish. Every P0–P2 packet names: subject; observation plus brief; failure mechanism; preserved signal; concrete composition/color/type/shape/voice replacement and owner; after-state observation (including narrow view). Make at least one repair at the