CompCode Academy

Lesson 11 of 65 · Free to read

Day 11 ΓÇö Intent-first building with AI app builders

Month 1 · Week 3 — Visual AI builders & shipping MVPs fast 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: Claude (planning)

Overview

As a final-year or early-career engineer, visual AI builders help you validate product ideas and demos fast — before you invest a full codebase. Sharp product briefs and knowing the limits matter: auth, complex business rules, and long-term ownership still need real engineering.

Learning objectives

By the end of this session, you can:

  • Explain the core ideas behind: Intent-first building with AI app builders: describing product intent, iterating visually, and knowing when to drop into real code.
  • Apply the ideas using Claude (planning) 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

Intent → screens → success metrics

A brief with user, job-to-be-done, screens, and “done means…” outperforms “make an app like Uber.” Use this for capstones, hackathons, and interview demos.

Limits to respect

Builders struggle with subtle permissions, migrations, and compliance. Plan an escape hatch to exported code you can own in Git.

Tooling for today

Primary tools: Claude (planning). 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
Vibe Coding: The Complete Story (2015–2026) — Where the term came from and how practice evolved.

Course video

Open on YouTube
Stop Vibe Coding. Use This Instead. — Spec-driven recovery from “accept all” failure modes.

Worked example / case study

Scenario

Write a plain-English product brief for a simple app aimed at classmates or teammates — three screens and success criteria.

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): Claude (planning).
  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: Intent-first building with AI app builders: describing product intent, iterating visually, and knowing when to drop into real code.
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. Write a plain-English product brief for a simple app aimed at classmates or teammates — target user, core screens, and success criteria.

Coaching notes

Add a “non-goals” section and a “when we drop into code” trigger.

Steps

  1. Set up or open the workspace required by: Claude (planning).
  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
Intent-first building with AI app builders: describing product intent, iterating visually, and knowing when to drop into real code.

## Context files
- (list paths)

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

## Definition of done
- Write a plain-English product brief for a simple app aimed at classmates or teammates — target user, core screens, and success criteria.

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

  • Skipping user and success criteria
  • Assuming publish URL = maintainable product
  • No plan for data export/backup

Key takeaways

  • Clarity is the main skill
  • Limits are features of the plan
  • Briefs beat vibes alone
  • Tools (Claude (planning)) change; the judgment skills transfer.

Resources

  • Official docs for: Claude (planning)
  • 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 11 of 65.

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