Build an AI Startup in 10 Days

Study Overview

Day 1 is the first step in converting your service idea into an actual product screen structure. Participants will learn the basic usage of Figma and design the structure of key screens such as Landing / Dashboard / Auth.

At the same time, starting from the original unstructured meeting minutes, functional specification (FR) through Codex Client, definition of normal and exception flows, and Gmail-linked sending are performed to automate requirements management and planning. Practicum is carried out in parallel.

Main session structure

Core Learning Elements

Study Overview

Day 2 is the stage of expanding the screen structure designed the previous day into the actual system operation flow and learning automated review of design document consistency through Codex AI. Participants use sequence diagrams and DFDs to visualize interactions and exception flows between system components, while using Codex AI to detect contradictions between meeting minutes, requirements, and screen design, and plan Analyze screen/API impact due to changes and automatically extract meeting decision logs.

Main session structure

Core Learning Elements

Study Overview

Day 3 is the step of connecting the previous screen design and data flow design to the actual database structure. Participants will extract the necessary data from screens and user flows and organize it into entities and properties.

Afterwards, relationships between entities are defined, and a normalization process from 1NF to 3NF is applied to design a data structure that reduces duplication and increases integrity. Ultimately, an ERD that can be used for service implementation Complete.

In this process, Codex AI is used as a project architect and auditor to sort data between planning and development (Task 01), build a dictionary of terminology standards across the project (Task 02), Automate analysis of chain impacts from schema modifications (Task 03), create DDL to record technical architecture decisions (Mission 01), and exception cases such as concurrency/integrity errors Carry out excavation (Mission 02).

Main session structure

Core Learning Elements

Study Overview

Day 4 is the stage of connecting previously designed screens, flows, and data structures to actual development documents and linking Codex Client Workspace. Participants decompose service functions into API units, define request and response structures in a form that can be used by both front-end and back-end, and have consistency verified through AI.

Additionally, by documenting the API using the Swagger/OpenAPI format and analyzing the scope of impact that may occur in case of change with Codex AI, Go beyond simple coding and learn practical product development and system stability analysis processes.

Main session composition (Codex AI linkage)

Core Learning Elements

Study Overview

Day 5 is the stage of linking Codex Client Workspace by auditing a service experience with high actual usability based on the previously configured screen structure and user flow. Participants analyze the screen plan based on the user's perspective and the principle of maintaining consistency, and find design flaws through collaboration with AI.

In addition, by streamlining the screen transition depth and verifying realistic barriers that reflect the personas of digitally underprivileged groups such as the elderly and the weak, Secure quantitative/qualitative usability evaluation capabilities that are highly useful in practical planning tasks.

Main session composition (Codex AI linkage)

Core Learning Elements

Study Overview

Day 6 is the step of connecting the screens and API specifications designed so far to the actual front-end screen. Participants create an efficient code structure by separating the roles of HTML, CSS, and JavaScript, and implement Figma designs into actual web screens.

Additionally, server data is bound to the screen through fetch/AJAX-based asynchronous communication, Handles various conditions such as loading, failure, and no data to create a real-world service-level user experience.

Especially in this session Codex Client WorkspaceClosely linked to construct a draft of the boilerplate screen skeleton that starts from a blank screen (Task 01), stack trace-based debugging advice and optional chaining defense code appearing in console logs such as TypeError: Cannot read properties of undefined (reading 'map') crashes (Task 02), correction of ambiguous variable names and improvement of common template renderer function extraction code (Task 03), server call 404 and JSON parsing Perform code quality review and encapsulation (Mission 02), including creating SyntaxError background analysis reports (Mission 01) and blocking global contamination.

Main session structure

Core Learning Elements

Study Overview

Day 7 is the step to promote the published prototype screen into an actual, operational feature. Participants establish a session control structure utilizing click event mapping, form data loading, and storage.

In addition, we diagnose points that cause deviation and information loss within the user's E2E journey path and restore them with sessionStorage. The completeness of the software is raised to the limit by blocking data redundant loading bugs caused by repeated input and past date exceptions with a guard.

Especially in this session Codex Client WorkspaceClosely linked to bind the subscription form submission event and synchronize localStorage (Task 01), restore search filter information when moving to multiple screens, sessionStorage caching (Task 02), set `isSubmitting` duplicate blocking lock variable and past date guard (Task 03), detect absence of loading spinner, create quality rating inspection report (Mission 01), create E2E user simulation driving verification report (Mission 01) 02).

Main session structure

Core Learning Elements

Study Overview

Day 8 is the day to plan and audit the user journey of membership registration and onboarding, which is the first impression of the service, from non-development planners to junior developers. Participants will learn how to maximize sign-up success rates by breaking down excessive form fields, such as unnecessary zip codes and street addresses, into a progressive sign-up structure.

In addition, we safely block payment/reservation data distortions caused by duplicate email subscriptions through JavaScript duplicate guard verification and assemble an email address format violation filter.

Especially in this session Codex Client Workspaceare closely linked to plan a sign-up/log-in priority checklist (Task 01), create a report to derive user flow by simplifying input form fields (Task 02), install a duplicate sign-up blocking guard and regular expression verification (Task 03), a silver customer persona mock experience real-time guide proofreading book (Mission 01), and build an integrated security patch for failure error messages (Mission 02) that prevents exposure of random account scanning hints.

Main session structure

Core Learning Elements

Study Overview

Day 9 is a session where the payment process that completes business monetization is planned from the user's perspective and a quality evaluation is conducted to completely block the risk of churn. Participants dramatically reduce friction by consolidating the multi-step confirmation window and two-factor authentication process into a summary overlay sheet.

In addition, we replace the external PG company's difficult English error codes with user-friendly and safe Korean, implement a spinner and order idempotent key that blocks repeated charging, and implant security badges and VAT segmentation elements to the payment window to eliminate phishing anxiety.

Especially in this session Codex Client WorkspaceBy closely linking, we build a simple order payment flow planning (Task 01), design of a safe error phrasebook and duplicate blocking lock (Task 02), revised safe payment UI CSS/HTML structure supplement (Task 03), window force closing and inspection response failure statement (Mission 01), and coupon search form initialization blocking customer journey diagnosis report (Mission 02).

Main session structure

Core Learning Elements

Study Overview

Day 10 You won't write a single line of code. All preparations necessary to release the service completed over 9 days of development to the world. Codex Client WorkspacePerform with . “Becoming the best explainer of the service” is my goal today.

We create service introductions that can be understood within 5 seconds and opening notices for each channel (email, homepage, SNS), prepare FAQs and customer service guides by predicting difficulties that users will experience, and complete result reports that can be delivered to investors and a roadmap for the next version.

Especially in this session Codex Client Workspaceare closely linked to complete the service launching material package (Task 01), configure 20 user perspective FAQs and response scenarios (Task 02), establish the MoSCoW priority Version 2.0 roadmap (Task 03), create an integrated launching package (Mission 01), and prepare the final presentation and Q&A (Mission 02).

Main session composition (Codex AI linkage)

Core Learning Elements