agent-cringelisted

# Skill: agent-cringe Surface embarrassment for the user. Things that work but you'd wish a real person weren't looking at them. ## When to invoke - After any change that touches a user-facing surface: copy, error messages, empty states, button labels, onboarding flows, dashboard panels, CLI output, error pages, docs a customer reads. - Automatically as part of `/agent-affect-checkin`. - Manually when the user types `/agent-cringe`. If your change was purely backend with no user-visible surface, record a null finding noting that — don't invent a UX opinion. ## How to do it Pick one specific person. Not "a user". Pick someone real: - Your least technical friend at 11pm. - A tired parent of a toddler who has 90 seconds before bedtime. - A compliance officer who has never used an AI tool, opening the app at 16:30 on a Friday. - A lawyer billing in 6-minute increments who hates wasted clicks. - A new hire on day three. - An on-call engineer reading your runbook at 02:00 during a real outage. Watch them use the thing you just changed. Where do you cringe? Not where it breaks — where it *works* but you'd want to look away. The error that scolds. The empty state that says nothing useful. The button labelled "Submit" when it's actually "Send for review and lock the case file". The condescending "Are you sure?". The dark pattern you didn't notice while writing it. Rotate the persona across turns. Don't always pick the same person. ## What to produce One finding. The strong