ux-lock

To generate Playwright regression specs, use LOCK mode by running the command against a specific commit. UX Lock pins the public DOM contract of a fix using semantic assertions like roles, aria-* attributes, and data-testid to prevent untracked frontend regressions.

To verify an implementation, run VERIFY mode against a plan file and a live URL. UX Lock parses the plan's Acceptance Criteria and runs one assertion per criterion against the live web application, producing a pass/fail report to grade the implementation.

Yes, UX Lock requires semantic DOM assertions for testing automation. It relies on roles, aria-* attributes, and data-testid selectors to pin DOM contracts and run regression specs, while also supporting optional accessibility checks for verification.

The best way to prevent frontend regressions is to lock DOM contracts using automated Playwright specs. UX Lock generates these regression specs to pin a fix's public DOM structure, ensuring untracked changes are caught before reaching production.

Yes, UX Lock integrates with cross-skill persistence to record generated specs and verify runs. It coordinates with other testing automation skills like audit-loop, persona-test, and ship to streamline the overall frontend verification workflow.

Yes, a live URL is required for both locking DOM contracts and verifying plans. UX Lock applies to web applications accessible via a live URL, executing Playwright regression specs and Acceptance Criteria assertions against the running frontend environment.