UX/UI/IA

When to Use

Use whenever an agent designs, restructures, implements, or reviews an interface: information architecture, navigation, flows, forms, controls, content hierarchy, responsive behavior, accessibility, visual systems, interaction states, or usability.

Use it before aesthetic exploration to establish structure, and again after implementation as a rendered-interface quality gate. Do not use it for pure backend work or as a substitute for user research when the users, domain, or risks are unknown.

Contract

This skill produces interfaces that are understandable, operable, resilient, and visually coherent. It guarantees that:

• the user, job, product truth, constraints, and success outcome are explicit before styling;
• information architecture and task hierarchy precede component selection;
• the complete flow includes loading, empty, partial, success, error, permission, offline, interruption, and recovery states where relevant;
• UX laws are selected as diagnostic lenses, not treated as universal commandments;
• accessibility, responsive behavior, content stress, and input modes are part of the design, not a cleanup pass;
• recommendations are verified in the rendered interface when implementation access exists;
• the output makes decisions and trade-offs explicit instead of producing generic advice.