Mission 01 Mission 01 Service Completeness Lab Guide
📥 Lab input
- •
day7_meeting_notes.md(meeting notes)
💾 Lab output
- •
day7_service_audit.md
1. Story and lab background
After basic assembly of the dashboard, sign-up and booking logic, ask Codex as your 'service QA partner' for a multi-angle completeness audit to see if any working gaps or detailed input barriers remain, and get an overall improvement guide.
2. Learning goals
- Get the overall quality of your JavaScript code checked quantitatively by AI.
- Understand why showing a loading state (Spinner) to users during server calls matters.
- Understand the importance of exception handling (try-catch) for cases like exceeding local storage limits.
🛠️ Follow-along lab guide
- Create the lab file: press the download button below and save
day7_meeting_notes.mdin theautomation/folder. - Hand off the quality audit: send the **Codex request prompt** below in Codex Client to run an overall completeness check.
- Save the report: organize the loading spinner and error recovery priority report (`day7_service_audit.md`) AI gave with scores, and keep it locally.
Download lab materials
Codex request prompt
Mission 01 Prompt
Based on all the provided code and screen flows, analyze missing loading feedback and exception handling from a service QA view, and generate a check report (Service Audit) with priorities.
4. Example output
Codex analyzes the meeting notes and outputs a normalized data entity mapping and Mermaid ERD script like below.
| File | Audit item | Main issue | Fix |
|---|---|---|---|
| day7_service_audit.md | Overall service completeness and exception audit | Missing loading spinner while waiting, and storage exceptions | Add a loading component and wrap with try-catch |
5. AI use points
- Usability completeness diagnosis: beyond code syntax, warns about sections where users are likely to feel the screen freeze while loading.
- Priority prescription: ranks the urgency of security and visibility improvements and maps them in the report.