Task 02 Screen Consistency Review Lab Guide
📥 Lab input
- •
fragmented-terms.md(mixed terms spec)
💾 Lab output
- •
project-glossary.md(standard term dictionary)
1. Story and lab background
Late in the project, a strange conversation happens in a design review meeting. The planner says "The sign-up screen says 'Username'," the developer says "The login screen labels it 'Customer ID'," and the front-end developer says "The confirm button is a small green one on one screen and a full-width blue one on the other."
When screens for the same service use different labels, button styles and messages like this, users get confused, communication costs between developers grow, and it breeds code rework.
In this lab, you'll learn to use Codex to survey scattered terms across all project docs and build a standard term dictionary (Glossary) that runs from planning all the way to DB variable names.
2. Learning goals
- Identify how domain terms are scattered across docs and design specs.
- Define the consistency break areas and English abbreviations (domain standard names) for the project.
- Define a standard term dictionary that planners, developers and designers all follow.
- Use AI to map legacy words to variable names and data types.
🛠️ Follow-along lab guide
- Create the lab file: press the download button below and save
day5_signup_flow.mdin theautomation/folder. - Hand standardization to Codex: send the **Codex request prompt** below in the Codex Client prompt box and build.
- Review the report: check that inconsistent elements are correctly mapped to a break area, the current state and a recommended standard.
Download lab materials
Codex request prompt
Task 02 Prompt
Compare the screen designs in the provided day5_signup_flow.md with each other, analyze elements that lack consistency in button placement rules, terms used and feedback messages, and write a screen comparison report.
4. Example output
Codex analyzes the terms together and produces a normalized master dictionary like this.
| Break area | Sign-up screen (LOGIN-001) | Data type | Mixed words in use | Recommended alignment (TO-BE) |
|---|---|---|---|---|
| User label | Labeled 'Username' | VARCHAR(50) | Labeled 'Customer ID' and 'Username' | Standardize all input labels to a single name, 'Username (ID)' |
| Main button structure | Small green Done button at top right | VARCHAR(50) | Full-width blue Log in button at bottom, small green Done button at top right | Make action buttons full-width at the bottom in the primary color |
| Session booking | Reservation | VARCHAR(50) | booking, request, Book, Reservation | reservation_id |
| Booking status | ReservationStatus | VARCHAR(20) | status, type, Step, Status | res_status |