Opening different folders in Codex and Antigravity prevents the tools from sharing files and breaks the feedback loop.

Create a new project directory `my-project` and initialize README.md with the following:
# Founder Intro & Problem Definition
- Founder Profile: Name, background, target market
- Core Problem: The key friction your target users face today
- Solution Concept: How your proposed web app solves this problem

Read README.md and draft a structured PAGE_REQUIREMENTS.md containing:
1. Target Audience & Core Value Proposition
2. UI Layout Specifications (Hero Header, Problem/Solution Grid, Interactive Contact CTA)
3. Design System (Dark theme, glassmorphism card styling, responsive grid)
4. Acceptance Criteria (Single file index.html, no broken styles, mobile-ready)

Read PAGE_REQUIREMENTS.md and build a complete index.html that satisfies all requirements:
1. Layout & Design:
   - Apply modern dark glassmorphism UI with Pretendard typography.
   - Consolidate CSS within <style> tags with responsive flex/grid layouts for mobile and desktop.
2. Required Components:
   - Header: Founder profile (avatar, name, tagline, 3 domain tags)
   - Body: Problem & Solution comparison cards (icons, titles, descriptions)
   - Footer: Interactive contact CTA button with smooth hover micro-animations
3. Delivery: Output a single, production-ready index.html file that opens cleanly in any modern browser.

Review index.html against PAGE_REQUIREMENTS.md:
1. Identify any missing requirements or rendering inconsistencies.
2. Create VALIDATION.md containing a structured QA checklist (Pass/Fail) with rationales.
3. If issues exist, document actionable remediation prompts for Antigravity.

I want to plan an AI Web App MVP. My initial concept is [Explain concept in 2-3 sentences].
Please help me structure Section 1 (Overview), Section 2 (Problem Definition), and Section 3 (Target Persona & Core Value) following the standard PROJECT.md specification format.

Based on the problem definition, design:
1. End-to-end user journey (Max 4 steps)
2. UI layout wireframes in Markdown for each screen
3. Complete Section 4 (User Flow) and Section 5 (Screen Specifications) for PROJECT.md.

Consolidate all sections and generate the authoritative `PROJECT.md` file:
- Ensure Tech Constraints specify: Single HTML, Vanilla JS, inline CSS, Pretendard font, mock AI logic.
- Include explicit Acceptance Criteria and an Out-of-Scope list to prevent feature creep.

Read PROJECT.md thoroughly and scaffold the initial `index.html` structure:
- Follow the design system and screen layout defined in Section 5.
- Implement responsive CSS for mobile and desktop screens.
- Build the Header, Hero section, and Input form controls.

Add core interactivity to `index.html`:
1. Form submission handler: Validate user input and display a loading spinner state.
2. Output generation: Produce rich structured result cards matching Section 6 data schemas.
3. Handle empty input validation with friendly error hints.

Implement local storage features:
1. Save generated outputs to `localStorage` under a dedicated key.
2. Render a "Recent Generations / History" list allowing users to reload previous results.
3. Add a "Copy to Clipboard" button with instant visual feedback.

Perform a full code review of `index.html` against `PROJECT.md`:
1. Verify each acceptance criterion defined in Section 7.
2. Check for JavaScript console errors, responsive layout bugs, and broken interactions.
3. Update `VALIDATION.md` with test logs and remediation recommendations.

• Functional Web App: `my-project/index.html` runs locally and executes the full user journey.
• Data Persistence: Results are stored in `localStorage` and persist across page refreshes.
• Validation Report: `my-project/VALIDATION.md` confirms all core acceptance criteria pass.

Review `PROJECT.md` and append Section 9: MVP v1.0 Feature Expansion:
- Selected Track: [Track A: Advanced UI / Track B: Data & Export]
- Specify exact new components, user actions, and acceptance criteria.
- Confirm that existing Day 3 core features remain untouched.

Read Section 9 of `PROJECT.md` and upgrade `index.html`:
1. Implement the requested Track A / Track B features cleanly.
2. Maintain full backward compatibility with existing form inputs and local storage keys.
3. Ensure no regressions occur in the core user flow.

Enhance error resilience in `index.html`:
1. Add input sanitization and length limits on all form fields.
2. Guard `localStorage` JSON parsing with try/catch and fallback defaults.
3. Provide a Toast Notification banner for success and error messages.

Conduct a complete regression audit of `index.html`:
1. Re-validate all Day 3 core features to ensure zero regressions.
2. Test new Day 4 track extensions across desktop and mobile viewports.
3. Update `VALIDATION.md` to certify MVP v1.0 release readiness.

• MVP v1.0 Codebase: Upgraded `index.html` featuring selective track extensions and defensive error handling.
• Updated Specs: `PROJECT.md` Section 9 updated to document all new functionality.
• Release QA Certification: `VALIDATION.md` updated with zero-regression test passes.

• Push `index.html` to your GitHub repo and enable GitHub Pages under Settings ➔ Pages.
• Copy your live HTTPS URL (e.g., `https://username.github.io/my-project/`).
• Test the live link on both your laptop and mobile device.

Read `PROJECT.md` and draft a concise 5-Minute Pitch Script (`PITCH.md`):
1. Hook & Problem Statement (1 min)
2. Solution & Live Demo Narrative (2 mins)
3. Competitive Edge & Tech Stack (1 min)
4. 2-Week Post-Bootcamp Milestone Roadmap (1 min)

• Time Limit: Exactly 5 minutes pitch + 2 minutes peer Q&A.
• Live Screen Share: Show your deployed URL in real-time.
• Peer Scorers: Fellow founders submit constructive feedback on the peer review sheet.

Draft `ROADMAP.md` incorporating feedback received during Demo Day:
1. Top 3 user friction points to resolve
2. Week 1 user interview schedule (Goal: 10 target users)
3. Week 2 technical improvements and deployment milestones

• 1. Live Web App: Deployed, public HTTPS URL running your MVP v1.0.
• 2. Complete Spec Repository: `PROJECT.md`, `VALIDATION.md`, `PITCH.md`, `ROADMAP.md`.
• 3. Pitch Presentation: Completed 5-minute live demo.

• Completion Certificate: Issued upon successful submission of all 4 key artifacts and survey completions.
• Alumni Network: Join the ACE Startup Slack community for ongoing peer collaboration and mentoring.
• Investor Office Hours: Top-rated demo day projects will receive 1-on-1 investor advisory sessions.