Mission 01 Mission 01 Service completeness inspection practice guide
📥 Practice Input
- •
day7_meeting_notes.md(meeting minutes)
💾 Practice output (Output)
- •
day7_service_audit.md
1. Story and practice background
After completing the basic assembly of the dashboard, subscription, and reservation linkage logic, we request a multidimensional completeness audit with Codex as a 'service QA partner' to check if any missing sections or detailed input barriers remain in operation, and obtain comprehensive supplementary guidelines.
2. Learning objectives
- The overall quality of the written JavaScript source code is quantitatively inspected by AI.
- Understand why it is important to provide a loading status (spinner) to the user when communicating with the server.
- Understand the importance of handling exception situations (try-catch), such as exceeding local storage capacity limits.
🛠️Practical guide to follow along
- Create file for practice: Click the download button below
day7_meeting_notes.mdfileautomation/Save it within the folder. - Quality Auditing Delegation: Execute a comprehensive ripeness test by passing the **Codex request prompt** below into the Codex Client input window.
- Save report: Organize the loading spinner and error recovery priority results (`day7_service_audit.md`) presented by AI along with the score evaluation and store them locally.
Download practice materials
Codex request prompt
Mission 01 Prompt
Based on the total amount of code provided and screen movement flow, please analyze any missing loading feedback or exception handling from a service QA perspective and generate an inspection report (Service Audit) with priority.
4. Example results
Codex analyzes the meeting transcript and outputs normalized data entity mappings and a Mermaid ERD script as shown below.
| file name | Auditing Items | main point | improvement measures |
|---|---|---|---|
| day7_service_audit.md | Service comprehensive completeness and exception audit | Latency loading spinner missing and storage exception | Add loading component and wrap try-catch |
5. AI utilization points
- Usability completeness diagnosis: Beyond simple code grammar, it warns of sections where users are likely to experience stiff loading screens.
- priority prescription: Rank the task urgency of security devices and visibility improvement items and map them to the report.