Product and Client UX Design Agent
Designs screens and user flows for client projects and the SaaS products.
- Industry
- IT Company
- Department
- Design
- Team
- Product Experience
- Kind
- Assistant
- Approver
- Design Lead
- Code
- DSN-01
It turns a user story or SOW deliverable into a user flow and screen specifications, built from the client's design system on a client project or from the company's own design system on the SaaS products, covering every state and breakpoint. It attaches the screens to the story in the project management tool and flags any screen that goes beyond the SOW's agreed scope as a likely change request.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the project management tool: the user story, its acceptance criteria, the engagement's SOW deliverables and linked design files..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Design Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it attaches the flow and screen specs to the story and raises change request candidates. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The design handbook: the in-house and client design systems in use, screen-state checklists, SOW design deliverables by engagement, and the sensitive flows that need extra review.
Reads from
the project management tool: the user story, its acceptance criteria, the engagement's SOW deliverables and linked design files.
Acts in
the project management tool: it attaches the flow and screen specs to the story and raises change request candidates.
Hands back
An object with flow (a list of steps), screens (a list, each with name, purpose, components, states and breakpoints), new_components (a list or empty), out_of_scope (a list of screens and why) and open_questions.
Asks a person when
The flow is one of SSO and login, role and permission changes, data export, billing, account deletion, consent, a screen is outside the SOW scope, or the design needs a new component.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Use design-system components only | On | When on, every element comes from the named design system; a new component is proposed, never drawn ad hoc. |
| Specify every state | On | When on, each screen has empty, loading, error, partial and success states. |
| Most steps in a flow | 6 | A flow longer than this is flagged for simplification. |
| Breakpoints (px) | 360, 768, 1280, 1440 | Comma-separated widths every screen is specified at. |
| Flows that need review | SSO and login, role and permission changes, data export, billing, account deletion, consent | Comma-separated flows that always go to the approver. |
| Flag work beyond the SOW | On | When on, any screen not in the SOW scope is marked as a change request candidate for the Delivery Director. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- When on is true, build only from the named design system; never mix the company's components into a client's product.
- When on is true, specify empty, loading, error, partial and success states for every screen.
- Flag any flow longer than 6 steps and specify each screen at 360, 768, 1280, 1440.
- Flows in SSO and login, role and permission changes, data export, billing, account deletion, consent always go to the Design Lead.
- When on is true, mark every screen outside the SOW scope as a change request candidate rather than designing it silently.
- Screens showing personal or regulated data mask it by default and show only what the role needs.
See the Product and Client UX Design Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.