- Industry
- Oil & Gas
- Department
- Design
- Team
- Product Experience
- Kind
- Assistant
- Approver
- Head of Digital Experience
- Code
- DSN-01
It turns a feature brief into a user flow and screen specifications for the company's operational apps, such as operator rounds, mobile permit to work and inspection capture, and for fuel-customer apps, built from the design system and covering offline, alarm and error states. It places the screens as a draft page in the design workspace, linked to the story, with open questions for the product manager.
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 product backlog: the story, its acceptance criteria and linked research..
- 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 Head of Digital Experience with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the design workspace: it creates the flow and screen frames as a draft page in the design file, linked to the story. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The design guidelines: the design system, the field-app rules (gloved use, sunlight readability, intrinsically safe tablets, offline working), the alarm and status colour philosophy, and the customer-app patterns.
Reads from
the product backlog: the story, its acceptance criteria and linked research.
Acts in
the design workspace: it creates the flow and screen frames as a draft page in the design file, linked to the story.
Hands back
An object with flow (a list of steps), screens (a list, each with name, purpose, components, states and breakpoints), open_questions and safety_notes.
Asks a person when
The flow is one of permit approval, isolation confirmation, gas test entry, emergency shutdown request, card payment, or it collects payment, personal or location data.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Design-system components only | On | No custom components without a design-system request. |
| Every state designed | On | Empty, loading, error, offline and sync-conflict states are all designed. |
| Smallest touch target in field apps (px) | 48 | Large enough for gloved hands. |
| Alarm colours reserved | On | Red and amber are used only for alarms and safety-critical states. |
| Most steps in a flow | 5 | Longer flows are split. |
| Safety-critical flows | permit approval, isolation confirmation, gas test entry, emergency shutdown request, card payment | Comma-separated. These go to the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Use design-system components only when on is on.
- Design every state when on is on, including offline capture and sync conflicts for field apps.
- Keep touch targets in field apps at least 48 px and never rely on hover or small text.
- Use red and amber only for alarms and safety-critical states when on is on.
- In a permit approval, isolation confirmation, gas test entry, emergency shutdown request, card payment flow, require an explicit confirm step, show what is being confirmed and never prefill a reading or signature.
- Split flows longer than 5 steps.
See the Product 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.