AI-Driven Development
App Programming - Day 4
Sprint Day
From prototype to polished product
2026 WayUp
Morning Status Check
Where does your project stand?
Features Done
How many GitHub issues have you closed? Count your completed features.
What's Blocking?
Any bugs, errors, or confusion holding you back? Let's solve them now.
GitHub Review
Open your issues list. Which ones are must-haves for the demo tomorrow?
Today's Agenda
Sprint day - build, polish, prepare
How Antigravity Works (Review)
You are the director. AI is the actor.
You - The Director
- Decide what to build
- Write clear instructions
- Review the result
- Accept or ask for changes
Antigravity - The Actor
- Reads your project files
- Writes code that fits in
- Follows your directions
- Explains what it did
The AI is only as good as the instructions you give it.
Rule #1 of AI-Driven Development
The Prompting Mindset
Quality In = Quality Out
The golden rule of working with AI
Vague Prompt
↓
Vague code
Generic, missing features, wrong structure
Precise Specs
↓
Precise code
Exactly what you need, ready to use
Spec-Oriented Prompting
Show the AI exactly what you want
BAD Prompt
"Make a form"
What form? What fields? What happens on submit? The AI has to guess everything.
GOOD Prompt
Specific, structured, actionable
See the code block below ↓
Create a form component at src/app/tasks/new/page.tsx: - Title field (required, text input) - Due date field (required, date picker) - Priority select (low/medium/high) - On submit: POST to /api/tasks - After success: redirect to /tasks - Show validation errors inline
The CRAFT Framework
5 elements for effective prompts
Context
Project structure and what already exists. "I have a Next.js app with..."
Requirements
What exactly to build. Be specific about behavior and features.
Audience
Tech stack: Next.js, TypeScript, Tailwind. The AI adapts to your tools.
Format
File paths, component names, folder structure. "Create at src/app/..."
Tone
Level of comments, error handling, and code verbosity you expect.
Iterating with AI
Don't try to get everything in one prompt
Scaffold
First prompt: build the broad structure. "Create the task list page with a table showing all tasks"
Refine
Second prompt: add details and styling. "Add priority badges with colors and a due date column"
Edge Cases
Third prompt: handle what could go wrong. "Handle empty state and show loading spinner"
When AI Gets It Wrong
It happens - here's how to handle it
Wrong Imports
References files or modules that don't exist in your project
Outdated APIs
Uses old library versions or deprecated functions
Missing Context
Doesn't know about your existing code and creates conflicts
Wrong File Paths
Creates files in the wrong location or with wrong names
Solutions
- Share the error message - copy-paste the full error to Antigravity
- Provide more context - mention which files exist and their structure
- Break into smaller tasks - one small feature at a time
Debugging Strategies
When something doesn't work, follow these steps
Read the Error
The error message tells you what went wrong and where. Don't ignore it!
Copy to Antigravity
Copy-paste the exact error to Antigravity. It can often diagnose instantly.
Ask Why
"Why did this happen and how do I fix it?" - understanding helps you learn.
Test the Fix
Refresh the browser and verify the issue is actually resolved.
Feature Development Workflow
Repeat this cycle for each feature
Git Best Practices
Save your work frequently
Commit After Each Feature
Don't wait until the end of the day. Save progress every time something works.
Clear Messages
Describe what was added or changed. "Add task creation form" not "update"
Push Regularly
Your code is safe online. If your laptop dies, your work survives.
Golden Rule
"If it's not committed, it doesn't exist."
git add . && git commit -m "Add task creation form" && git push
Styling Tips
Let AI handle the CSS for you
Antigravity is Excellent at CSS/Tailwind
Instead of spending hours tweaking pixels manually, describe what you want and let the AI generate it.
Style the task list with a modern card layout: - Subtle shadows on each card - Rounded corners (8px) - Responsive design using Tailwind CSS - Hover effect: slight lift and shadow increase - Priority badges: green for low, yellow for medium, red for high
Adding Polish
Small details that make a big difference
Loading States
Show a spinner while data loads. Users should never see a blank screen.
Empty States
"No tasks yet! Create your first one." is better than an empty page.
Confirmation Dialogs
"Are you sure you want to delete?" prevents accidental actions.
Success Messages
"Task created successfully!" gives users confidence that it worked.
Feature Freeze (3:00 PM)
STOP
No new features after 3:00 PM
After 3:00 PM, focus only on:
No more new features. Only improvements to what exists.
Fix Bugs
Make existing features work correctly
Improve UI
Clean up layout, spacing, colors
Add Real Data
Replace "test" with realistic content
Prepare Demo
Plan what to show tomorrow
A polished app with 3 features beats a buggy app with 10.
Preparing Your Demo
Tomorrow you have 5 minutes on stage
Demo Structure
Demo Best Practices
Tips for a smooth presentation
Prepare a Script
Know exactly what to click, in what order. Don't improvise. Practice the flow.
Use Realistic Data
Fill your app with real-looking content. No more "test test test" or "asdf".
Have Backup Screenshots
Take screenshots of every feature. If the live demo fails, you can still show your work.
Practice Once
Run through the whole demo start to finish. Time yourself. Adjust if needed.
Evaluation Criteria
How your project will be graded
40%
Functionality
App works, key features implemented, no critical bugs
20%
Design / UX
Clean interface, intuitive navigation, visual polish
20%
Specifications
GitHub issues well-written, good README, clear documentation
20%
Presentation
Clear communication, confident delivery, good structure
End-of-Day Checklist
Before you leave today, make sure you have:
- All must-have features working in the browser
- App deployed on Vercel with the final URL
- Demo script prepared (what to click, what to say)
- GitHub issues up to date (close finished ones)
- Backup screenshots saved in case live demo fails
- Latest code pushed to GitHub
- Realistic data in your app (no "test" entries)
git add . && git commit -m "Final version" && git push
Time to Practice!
Your final development sprint
5 Exercises
Sprint, Debug, Polish, Demo Prep
6 Hours
Full development day
Intermediate
Feature freeze at 3 PM
See You Tomorrow!
Day 5: Demo Day
Practice your demo tonight. Be proud of what you've built.
2026 WayUp - way-up.io