Boyjingweizhang/qt-widgets-agent-skills

Qt Widgets UI Review

Review the real QWidget output. Do not treat the HTML prototype as proof that the application is correct.

Inputs

• actual application screenshots;
• capture metadata: state, dimensions, DPI, theme, command;
• ui-spec.yaml and design-tokens.json;
• current .ui, QSS, resources, and presentation-layer C++;
• current UI inventory and contract validation output;
• before screenshots when available.

Required screenshot matrix

For substantial screens, request or capture:

State	Target size	Minimum size
idle/ready	required	required
active/acquiring	required	required
warning/fault	required	recommended
long text / localization	recommended	recommended
disabled/disconnected	recommended	optional

Use scripts/capture_window.ps1 when the application has a deterministic demo mode. GPU/OpenGL content may require visible on-screen capture and can still differ from off-screen techniques.

Review dimensions

1. Task hierarchy: primary action and primary data are obvious.
2. Operational state: connection, acquisition, storage, warning, and fault states remain visible where required.
3. Layout: alignment, spacing, stretch, splitter behavior, clipping, and minimum size.
4. Typography: hierarchy, truncation, rapidly changing metric stability, and readability.
5. Color and semantics: contrast and meaning; warnings do not depend on color alone.
6. Controls: hit area, focus, disabled/hover/pressed states, destructive action separation.
7. Plots: dominant area, labels, legend, cursors, alarm regions, and repaint stability.
8. Consistency: tokens, dynamic roles, icon family, borders, radii, and panel treatment.
9. Maintainability: local styles, selector specificity, repeated literals, and runtime global repolish.
10. Integration: protected contract, build, and runtime behavior.

Severity

• Critical: unsafe or unavailable operation, hidden abort, severe clipping, broken state communication, lost integration contract, or unusable minimum-size layout.
• Warning: material inefficiency, ambiguity, inconsistency, accessibility issue, or maintainability problem.
• Opportunity: polish or optimization with lower user impact.

Report format

Write design/reviews/<screen>-review-vN.md:

# Screen review

## Verdict
Pass / Pass with warnings / Fail

## Critical
- [C1] Evidence, impact, exact location, recommended fix.

## Warnings
- [W1] ...

## Opportunities
- [O1] ...

## Contract and build evidence
- ...

## Next iteration scope
- Maximum three highest-value changes.

Use precise evidence. Avoid vague statements such as “make it more modern.”

Read-only rule

This skill reports findings. Use qt-widgets-ui-implement for changes. A user may explicitly request review plus fixes, in which case finish and save the review before implementing.

References

• references/screenshot-protocol.md
• references/review-rubric.md
• references/industrial-measurement-profile.md