Master an architectural UI/UX design approach: find usability weak points from the user's view based on screen specs and path design, review layout consistency between screens, and shorten the flow depth to reach the final goal.
In real projects, misunderstandings between planning, design and development lead directly to missing database items and broken consistency. Let's see why guaranteeing consistency at the design stage matters.
Stubborn feature-centered design means first-time beginners don't understand the UI and quit the app midway.
Button positions, sizes and labels (Username vs Customer ID) differ on each screen, making users tired of relearning.
Users go through an overly long 9-step screen journey to reach their goal (booking a session), lowering final payment conversion.
Compare ChatGPT, limited to a single chat context, with Codex Client, which understands the whole folder structure and dependencies between files.
| Compared | ChatGPT (general chat AI) | Codex Client (Workspace-based AI) |
|---|---|---|
| Context awareness | Compares and analyzes many screen plan files and the path depth of user entry together | Traces mismatched UI button designs, sizes and alignment, and status message formats across login, sign-up, My Page and more |
| Screen consistency review | Gives only convenience feedback on a single text screen | Recommends consistent standard names and DB column names based on the project term dictionary |
| Impact analysis | Suggests isolated schema errors or made-up table fixes | Works backward from small schema changes (e.g. adding a column) to list API specs and screen parts to fix |
The list of final outputs learners create during the Day 5 session, and the purpose of each.
A Mermaid ERD script and spec rendering entities and relationships pulled from a natural-language plan (output: erd-schema.md)
A project standard term dictionary defining scattered planning terms as standard English columns (output: project-glossary.md)
A change impact analysis listing API and screen fixes for adding booking approval (WAIT_APPROVE) (output: change-impact-report.md)
A Design Decision Log (DDL) archiving the reasons for normalization and data design decisions and rejected alternatives (output: design-decision-log.md)
An Edge Case analysis report with DB improvements for concurrent payment errors, data lost on account deletion (referential integrity) and transaction rollback (output: edge-case-analysis.md)
A mapping of the inputs used in the lab and the outputs produced through Codex Workspace reasoning.
Enter the meeting scenario prose and derive precise normalized relationships (1:N, 1:1) and Mermaid code.
Based on the screen spec of the provided booking request form, review whether the information structure is clear from the view of a beginner who's new to the service, point out what hurts usability, and write an improvement report (UX Review Report).
Compare the gap between Figma plan terms and DB dev specs and build a domain term master dictionary.
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.
Find the API and table impact when the release plan changes to add an 'approval' step to booking.
Analyze the detailed booking scenario path in the provided day5_signup_flow.md and write a User Journey Report that minimizes the click steps and screen changes a user needs to complete a session booking.
Log the rejection reasons and agreements for normalization decisions, splitting booking history physically, and so on.
You are a self-employed person in your 50s who is a bit clumsy with smartphone apps. Looking at the sign-up and first screen UI spec in the provided day5_signup_flow.md, write from your own point of view what is most confusing and hard when signing up, with your emotional reactions and requests for improvement.
Audit system weak points to prevent referential integrity violations (account deletion) and broken transactions.
Based on the provided day5_signup_flow.md spec, score each of 1) information readability, 2) control accessibility, 3) error recovery and 4) flow efficiency out of 5, and build a service quality evaluation (Usability Evaluation) with an overall score, strengths and painful areas to improve.
Going beyond simple text matching, it understands entity referential integrity (FK) and transaction lifecycles, and works backward from a natural-language plan to DDL (Data Definition Language) queries and state machine rules automatically.
It groups differently written terms (customer name vs Nickname) by meaning (Clustering) to produce a company-wide term master dictionary, and syncs the data dictionary's consistency based on it.
See how data and analysis from each step go around the technical design loop to maximize quality.
This usability diagnosis pipeline removes usability errors and design contradictions before a single line of code is written, making sure users can understand and use the product easily.
Topics that work well for class discussion or interview questions.
"When a sign-up error wipes out all entered data, how should we balance the security view (deleting data) and the user experience (UX) view?"
"If a project runs to the middle without a screen consistency guide, how does the resulting 'terminology debt' inside the dev team affect the real schedule?"
An overview of all the lab tasks and missions covered on Day 5.
| Task | Topic | How AI is used |
|---|---|---|
| Task 01 | Review screens from the user's view | Have AI review awkward screen layouts from a beginner's view and suggest fixes |
| Task 02 | Screen consistency review | Compare term use and button position symmetry across pages and set rules |
| Task 03 | User journey improvement | Design a flow that cuts unnecessary standalone screens to reduce user clicks |
| Mission 01 | Be a first-time user | Use an older persona unfamiliar with smart devices to recreate sign-up struggles |
| Mission 02 | Evaluate service quality with AI | Evaluate usability, understanding and convenience together and convert them to grades and scores |