Record the baseline
Keep the accepted result, intended change, affected surfaces, and recent work in your task list or plan tool.
Use this skill when
- A cosmetic or shared component change affects more than one surface.
- You must preserve an accepted design baseline while changing presentation.
- Code, browser evidence, screenshots, and guidance must describe the same result.
Coverage workflow
Change the shared owner
Update the semantic token, component, or style rule once. Trace aliases, variants, generated output, and local overrides.
Keep one reviewer
Use one dedicated reviewer when supported. Check design rules, consumer coverage, relevant states, and documentation after each cosmetic change.
Reconcile evidence
Use static inspection for propagation and browser evidence for layout and interaction. Keep source, tests, deployment, persisted content, and public visibility separate.
Standards boundary
WCAG 2.2 success criteria are normative. Button hierarchy from USWDS, GOV.UK Design System, and Material Design 3 is design guidance. The standards reference keeps those roles separate.
Works in
Claude Code: Marketplace skill. Codex: candidate, not yet runtime-tested.
Install
npx skills add jamditis/claude-skills-journalism --skill surface-completeness