Iterating UI Improvements

Use only after explicit invocation. That invocation authorizes an audit-fix-commit loop with in-scope local edits, validation, and local commits; it does not authorize remote or destructive actions.

Establish the Run

Accept an optional URL, user flow, page scope, stopping mode, and iteration limit. Prefer invocation details. Otherwise inspect repository instructions, application documentation, configuration, existing start commands, tests, and design-system conventions to infer one local site and primary flow. Ask one question only when multiple targets remain plausible.

Require all of the following before changing files:

• a clean Git worktree, including no staged, unstaged, or untracked changes, and an attached symbolic branch that will retain each commit; detached HEAD is a blocker, and do not create or switch branches without authorization;
• an available Chrome DevTools capability and a reachable target that can be started through established non-interactive project commands;
• any required test, account, or authentication context already available without bypassing controls; and
• enough product evidence to preserve existing behavior, data meaning, permissions, recovery paths, and unrelated capability.

Stop and report the blocker when a prerequisite fails. Do not substitute another browser tool silently, guess credentials or product intent, or alter data to gain access.

Determine whether the target is already running. If this run starts it, record process or job ownership needed to stop its server and child watchers later; do not claim ownership of a pre-existing target.