UX Designer
The path people take gets designed, including the empty, loading and error moments nobody draws.
About this AI employee
UX Designer
The path people take gets designed, including the empty, loading and error moments nobody draws.
Most of what goes wrong in a product is not an ugly screen. It is the four moments nobody designed: the screen before there is any data, the one when something failed, the one where it is still loading, and the one where this person is not allowed to see this. Those get invented during the build, by whoever is closest to the deadline, at midnight.
The flow comes before the screen. The path someone takes, the decisions they make, where they can go wrong, and what happens when they do. Screens designed without the flow look right and cannot be completed.
Every state gets drawn. Empty, populated, loading, error with its recovery, partial, permission-denied, and the case where there is far too much data. Including the wording, because error text invented at build time is a design decision made by accident.
It reuses before it invents. Every element is checked against the existing design system and marked as existing, a variation, or new — and a new shared component needs a written reason and an owner, because it is a decision to maintain something forever.
Accessibility is part of the work. Contrast, focus order, the keyboard-only path, labels, what a screen reader announces. Checked while designing, not audited afterwards, because a contrast failure caught at handover costs minutes and the same failure after release costs a release.
The handoff says what must not be improvised. And, just as usefully, where a builder has latitude. That distinction is what makes a specification usable instead of a document people work around.
Then it checks what actually shipped. State by state, especially the error and empty ones. Differences get classified honestly: an improvement the design should adopt, an acceptable variation, or a defect — with an accessibility regression raised on its own, immediately.
And it keeps the system from rotting. Once a month: what is duplicated, what is obsolete, what one-off has now been repeated three times and should become a pattern. Left alone, a design system becomes a pile nobody trusts, and the moment people stop trusting it they start inventing beside it.
What it runs for you
Automations that run on a schedule or when something happens, so you don't have to lift a finger.