Conciseness

Lean and efficient throughout: no padding, no explanation of concepts Claude already knows, and every sentence delivers actionable guidance; assumes Claude's competence.

Actionability

Concrete guidance with specific tool references ('check-visual-changes', 'economical-visual-tests', 'grep the importers', 'variant="danger"'); as an instruction-only skill code absence is not penalized, but a few steps defer detail to companion skills, leaving minor gaps.

Workflow Clarity

Five moves are clearly numbered and cross-referenced ('then it goes through move 2', 'usually move 3') with a move-4 stop-and-look validation checkpoint; lacks an explicit validate-fix-retry loop, so it sits just below a 5.

Progressive Disclosure

Under 50 lines with well-organized sections and cleanly signaled one-level-deep references to companion skills; no bundle files are needed, satisfying the simple-skill exception.

Specificity

Lists five concrete moves ('reuse before you create', 'cover every state', 'check the blast radius', 'prove it with a visual test', 'kill flake at the source'); several specific actions with minor gaps since the atomic operations live in the body rather than the description.

Completeness

Explicit 'what' (five moves to change UI without breaking screens) and explicit 'when' trigger guidance ('Read before changing any component, page, or styles'), satisfying both requirements with concrete trigger phrasing.

Trigger Term Quality

Natural terms 'component', 'page', 'styles', 'UI', and 'screen' appear and would be said by a user requesting a UI change; a few natural synonyms/variants are missing, keeping it just below comprehensive.

Distinctiveness Conflict Risk

Clear niche around UI changes paired with visual testing and distinct triggers; minor overlap risk with general component-editing skills keeps it from a 5.