ui-parity
Installation
SKILL.md
UI parity
Compare a reference and an implementation, fix confirmed in-scope UI/UX differences, and deliver a verified report. Minimize human involvement by resolving routine findings from evidence and existing authority. A difference list or screenshot collection alone is not completion.
Scope and authority
- Start with the user's scope, accepted exceptions, reference, implementation, and permission to repair. A request to compare only remains read-only. This skill does not authorize publication, external messages, production mutations, new tracking systems, or unrelated work.
- The reference is the default UI standard, not an infallible business specification. Current explicit decisions and applicable requirements take precedence. Consult backend contracts/implementation when they clarify meaning; unfinished backend code is evidence, not automatic authority. Do not introduce API functional testing unless requested or necessary for an authorized change.
- The leader is the agent that holds the task. It owns the common quality standard, correctness judgments, ambiguous decisions and final acceptance, and repairs confirmed differences itself. Browser workers collect facts. A repair worker is used only for an independent repair with disjoint file ownership; "the repairer" below means whichever of the two made the change. Routine repetitions can follow a leader's recorded standing decision. Do not send every color mismatch to the user.
- The leader investigates conflicts and decides within delegated authority. Missing grounds first trigger a question-directed evidence request to an existing appropriate operator; ask the user only for a remaining product decision that evidence and authority cannot settle. Hold that dependency and continue independent work; never bury it as a pass.
- For an unavailable backend capability, implement the achievable UI with an isolated contract-shaped mock when authorized. Label the evidence as mocked; do not add mock labels, autofill buttons, or fake-success paths to the product merely for testing convenience. Preserve actual security and business constraints.