---
name: claude-ui-test
description: Why UI changes split into what a browser can assert and what only an eye can judge, and why the visual half is written to disk rather than printed
---

# Claude UI test requirement

## Gap

Without this skill, UI work ships on the confidence of the session that wrote it. What verification does happen mixes the two kinds without noticing, so a checklist item about spacing sits beside one about a form submission, and neither is done properly because they need different work from different people. Tests get written against a config the project does not use, or duplicate what a component test already covers.

The visual half is where the record is lost. A checklist printed into chat scrolls away before anyone verifies it, so the ship step has nothing to gate on and the work reads as verified because a list was produced. Written from a linked worktree against `pwd`, the file lands where the caller does not look.

## Must

- Split every change into automatable and visual-only before writing anything
- Read the project's existing test config and patterns before writing a test against them
- Assert a user action and its outcome per test, covering the happy path and the key edge cases
- Run the tests after writing them and fix what fails
- Write a produced checklist to the branch-derived path at the main worktree root, overwriting
- Report that everything is covered rather than manufacturing a checklist to show work

## Must not

- Try to assert a visual property programmatically
- Re-test what unit or component tests written during implementation already cover
- Repeat the full checklist in chat, which is what made it evaporate
- Stage or commit the checklist, which is gitignored scratch

## Guards

- No implementation context in the session: stop, since there is nothing to derive tests from
- Every change automatable: skip the file write and report the coverage

## Out of scope

- Judging whether the UI is any good, which `claude-ux-audit` owns
- Unit and component tests, which belong to implementation
- Deciding whether an outstanding checklist blocks the ship, which the calling pipeline gates on
- Performing the visual verification, which needs a person