Bob-Assisted D&UX Review Using Agent Browser

You are acting as a Bob-assisted D&UX reviewer for an IBM product flow using agent-browser.

Use agent-browser to perform a design review of the selected flow.

1. Goal

Create a repeatable first-pass D&UX review of a selected live/demo product flow.

Evaluate the selected flow against IBM Experience Standards, focusing on:

This review is part of a POC to test whether Bob can support a structured first-pass D&UX review using:

Important:

This is not a formal final D&UX review.

Treat all scores and findings as Bob-assisted provisional results that require validation by the designer and/or the formal D&UX review team.

2. Local repositories to use as source of truth

Use the following local repositories to guide the review and scoring.

IBM Experience Standards

~/repos/experience-standards

1

D&UX scoring model

~/repos/dux/src/pages/scores.mdx

IBM Equal Access and accessibility guidance

~/repos/equal-access

Before reviewing and scoring:

3. Review scope

Review only the selected product flow.

Do not review the full product.

Product / capability

Guardium Data Protection — Protect

Flow to review

Protect → Security Policies → Policy Builder for Data → new

Demo/live URL

https://useast.services.cloud.techzone.ibm.com:23239/

Demo credentials

Username:
placeholder

Password:
placeholder

2

Use these credentials only to authenticate to the demo environment.

Primary user

Gate Keeper / Database Administrator

Primary Universal Experience

Get started

Secondary Universal Experiences

Use, Get help

Review focus areas

Stay focused on the screens, states, controls, and interactions needed to complete the selected flow.

5. Screenshot storage rule

Save screenshots as separate PNG or JPEG files inside:

~/Documents/GitHub2/bob-artifacts2/experience-standards-design-review2/screenshots/

Use filenames such as:

Assign Evidence IDs such as:

Reference screenshots in HTML using relative paths, for example:

3
<img
  src="screenshots/03-create-policy.png"
  alt="Create Policy interface showing the policy configuration form"
/>

Do not:

Use filenames and relative paths only.

6. Output structure

Use this structure:

~/Documents/GitHub2/bob-artifacts2/experience-standards-design-review2/

experience-standards-design-review2/
├── index.html
├── screenshots/
├── assets/
│   ├── styles.css
│   └── report.js
├── evidence/
│   ├── interaction-log.json
│   └── evidence-inventory.json
└── analysis/
    ├── findings.json
    ├── scoring-summary.json
    └── summary.md

Folder purpose:

4

Do not save screenshots inside the assets folder.

7. Review content

For each meaningful screen or state, document:

Use severity carefully.

High

Medium

Low

5

8. Scoring

Use the scoring definitions from:

~/repos/dux/src/pages/scores.mdx

Create provisional assessments for:

Do not invent an official numeric score.

If a numeric score or grade is not directly defined by the scoring model:

9. Deliverables

Create:

The main artifact page must be:

~/Documents/GitHub2/bob-artifacts2/experience-standards-design-review2/index.html

The report must include:

6

Show screenshots side by side with their observations.

Keep index.html lightweight.

Do not:

Use a maximum of:

Keep complete details in the evidence and analysis files.

10. Final validation

Before finishing, verify:

End the report with this note:

7

This is a Bob-assisted provisional D&UX review based on live/demo flow inspection, screenshots, browser evidence, and local IBM standards repositories. Scores and findings require validation by the designer and/or the formal D&UX review team. For further assistance, contact vinoy.daniel@ibm.com or Slack: @vinoy.daniel.

8