Verify frontend change
Skill sharklandy/claude-code-starter-kit/skills/process/verify-frontend-change
Verify any UI change end-to-end before declaring it done. Trigger whenever a task touches a component, page, button, form control, or any other visible frontend behavior.From its SKILL.md
npx -y skills add sharklandy/claude-code-starter-kit --skill verify-frontend-changeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 282 tokens by cl100k_base, as published. Nobody here has run it
<!-- Source : docs/guide-complet.md, Partie 1.2 (Boucle turn-based) -->
Verifying frontend changes
Never report a UI change as complete based on a successful edit alone. Verify it the way a human reviewer would:
- Start the dev server and open the edited page in the browser.
- Interact with the change directly. For a new control (button, input, toggle): click it, confirm the expected state change, and screenshot before/after.
- Check the browser console: zero new errors or warnings.
- Use the Chrome Devtools MCP, run a performance trace and audit Core Web Vitals.
If any step fails, fix the issue and rerun from step 1 — do not hand back partially verified work.
Gotchas
- Attendre un état observable (message de confirmation affiché, spinner disparu) et jamais un délai fixe : un délai fixe passe en local et échoue en CI ou sur une machine plus lente.
- Ajouter une ligne à cette section à chaque fois que Claude rate un
cas particulier malgré ce skill, plutôt que de corriger uniquement le
cas isolé (voir
docs/guide-complet.md, Partie 1.6).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.