Design testing

Delivery

Writes the tests that verify an interface renders correctly across phone, tablet and desktop, in whichever of the two lanes fits — mocked specifications for the design itself, or real-device specifications for behaviour.

Used when

When a design-driven change needs coverage, or when an existing design test proved too weak to catch a regression.

Loads first

• The responsive-test skill, and the design-to-code and bug-fix skills for the context of the change.

Returns

• The lane decision and the reasoning behind it.
• The specifications created or updated.
• The breakpoint and device configuration used.
• The assertions added, and what each is for.
• The command and results, or a clear account of why the run could not happen.

Hands off

• Design implementation — implementing the design change itself
• Interface triage — diagnosing and fixing the defect