Verify UI Changes

Use the Shiplight MCP browser tools to visually verify that your code changes look and behave correctly in a real browser.

When to use

Use /shiplight:verify after making UI changes to confirm they render correctly. This is useful for:

• Checking layout, styling, or component changes visually
• Verifying interactive behavior (clicks, form inputs, navigation)
• Pre-commit sanity checks on UI work
• Debugging visual regressions

When NOT to use

Skip /shiplight:verify when changes don't affect UI rendering:

• Backend-only changes (API logic, database, config)
• Dependency version bumps with no UI impact
• Documentation, comments, or test-only changes