Build a local verified frontend skill

This is the shape of a skill, not Chip Huyen's original skill and not a universal set of commands. Work with the human to build the version that fits their project. Do not pretend the example decisions below are already true in their environment.

Start with the project

Inspect the repository before asking questions. Find the frontend framework, start command, local URL, existing browser or end-to-end test tools, CI setup, contribution guidance, and any visual or accessibility standards already recorded.

Bring the human concrete findings and ask only for the decisions the repository cannot answer:

• Which interfaces, routes, and states need visual verification?
• Which environments do they use, such as a desktop agent, terminal, remote runner, or CI?
• Which browser tool should the agent use in each environment?
• Which viewport sizes or breakpoints matter?
• What should the agent look for beyond obvious breakage?
• Which screenshots should be returned, and where should they go?

Do not turn this into a generic questionnaire. Build the first version around one real frontend change and refine it with the human.