CompCode Academy

Lesson 38 of 65 · Free to read

Day 38 ΓÇö Build sprint I

Month 2 · Week 8 — Full-Stack Build Sprint Audience: Final-year students & early-career engineers (0–3 years) Format: Self-paced study + optional live clinic · Suggested time: 4–6 focused hours Key tools: Cursor / Claude Code, Supabase

Overview

Build sprint I: scaffold and data layer. Resist UI rabbit holes until the API and schema are real.

Learning objectives

By the end of this session, you can:

  • Explain the core ideas behind: Build sprint I: scaffold and data layer.
  • Apply the ideas using Cursor / Claude Code, Supabase on a realistic task (capstone, internship, or first-job style)
  • Produce the exercise deliverable with clear success criteria
  • Identify common failure modes and how to recover
  • Capture at least one reusable prompt, rule, or checklist for your personal library
  • Decide what must remain human-reviewed for this class of work

Core concepts

Scaffold order

Repo → env → schema/migrations → API stubs → seed data → smoke test.

Agent instructions

Forbid unrelated refactors; require migrations for schema changes.

Tooling for today

Primary tools: Cursor / Claude Code, Supabase. Prefer official docs when APIs change. When a model invents a symbol, verify against source or docs immediately.

Practice posture

You are a final-year or early-career engineer pairing with a very fast teammate (the model): clear intent, grounded context, inspect consequential changes, keep a paper trail (commits, prompts, decisions).

Process diagram

Watch & learn

Study these free videos before or during the exercise. Each embed is chosen to reinforce today's objectives.

Course video

Open on YouTube
How To Use Cursor AI (Full Tutorial 2025) — Install, chat, agent mode, and core Cursor loop.

Course video

Open on YouTube
SQL Tutorial — Full Database Course (freeCodeCamp) — Joins and queries you must validate, not just generate.

Worked example / case study

Scenario

Scaffold full-stack app; implement DB + API layer with an agent; prove with smoke calls.

Step-by-step

  1. Clarify the outcome in one sentence tied to the exercise below.
  2. Gather grounding context (files, docs, schema, acceptance checks).
  3. Run the primary tool(s): Cursor / Claude Code, Supabase.
  4. Produce the smallest vertical slice that proves the idea.
  5. Verify with a command, test, screenshot, or side-by-side comparison.
  6. Write down one steering note — what you told the AI when it went wrong.

Sample prompt you can adapt

Role: Senior engineer mentoring an early-career developer (pairing with me).
Task: Build sprint I: scaffold and data layer.
Context: Final-year / early-career project (capstone, internship, or junior role).
Constraints:
- Match existing project patterns
- No new dependencies unless justified
- Include tests or a verification checklist
- Call out assumptions explicitly
Output: step plan first, then code/files, then verification commands.

Hands-on exercise

Primary task. Scaffold the full-stack app and implement the database and API layer with an agent.

Coaching notes

Seed script with realistic sample rows.

Steps

  1. Set up or open the workspace required by: Cursor / Claude Code, Supabase.
  2. Skim today's core concepts and watch the video(s) before prompting.
  3. Execute the task in small commits (or saved artifacts if no-code).
  4. Fill the success checklist below.
  5. Note one surprise and one process improvement for tomorrow.

Success criteria

  • Deliverable matches the exercise description
  • You can explain every AI-generated change in plain language
  • Verification ran (tests, manual check, or published URL)
  • At least one pitfall from this lesson was consciously avoided
  • Artifact saved (repo commit, doc, or published link)

Timebox

Suggested: 90–150 minutes of focused build time after study.

Templates & checklists

AssetPurpose
Prompt stubReuse today's structure (role → task → constraints → format)
Verification checklistTests / manual QA / security skim
Decision logWhat you delegated vs kept human

Copy-paste prompt skeleton

## Goal
Build sprint I: scaffold and data layer.

## Context files
- (list paths)

## Constraints
- Stack: (fill)
- Do not: (secrets, drive-by refactors)

## Definition of done
- Scaffold the full-stack app and implement the database and API layer with an agent.

Daily reflection (3 minutes)

  • What did AI do well?
  • Where did it confidently fail?
  • What rule will you add to your cookbook/rules file?

Common pitfalls

  • UI first, empty API forever
  • Manual schema edits in hosted UI without migrations
  • Giant scaffold PR with secrets

Key takeaways

  • Data layer unlocks features
  • Smoke tests early
  • Agents need forbids as much as goals
  • Tools (Cursor / Claude Code, Supabase) change; the judgment skills transfer.

Resources

  • Official docs for: Cursor / Claude Code, Supabase
  • Course cookbook: keep prompts in a versioned Markdown file in your repo
  • Prior days this week — skim objectives if you skipped ahead

Self-paced lesson — Mastering AI-Assisted Development & Vibe Coding — Day 38 of 65.

New free lessons and course updates. Unsubscribe from any email.