desktop-improvelisted
Install: claude install-skill SVN11X/skills
# desktop-improve
Improve what a person meets in the window, proven in the executable on Windows. A browser test proves nothing about a native window, and a passing unit test proves nothing about how the window feels.
`<standard>` is the copy of the standard the plugin ships in `skills/repo-setup/standard`, or a checkout of SVN11X/standards.
## Ground rules
- Talk to the owner in their language. Write code, comments and docs in English. Text people see stays in the app's language.
- Work on a test profile, never on the owner's data: point the app's data folder (for example `LOCALAPPDATA`) at a scratch folder, or use the app's own test profile.
- Keep the app's toolkit, theme and words. Fix the cause with the smallest change. No new UI framework for a UX fix.
- Never claim "verified on Windows" without a run on Windows. Say what ran and what did not.
## 1. Name the task
Write the task in the person's words, with what done looks like, before touching code: "while I type in another window, the review notice lets me finish the sentence; when I choose to start, the keyboard goes to the first question". A task the owner can recognize when it is done.
## 2. See what the window exposes
- tkinter exposes little to UI Automation. Measure it from inside: `python <standard>/scripts/desktop_ux.py tk <module>:<factory> --shots <scratch> --save <scratch>/before.json` builds the interface on a Tk root, opens every tab at 1024x700 and 800x600, saves screenshots and keeps the run. For