CompCode Academy

Lesson 26 of 65 · Free to read

Day 26 — Claude Code: agentic coding in the terminal and the plan-act-observ…

Month 2 · Week 6 — Claude Code & Agentic CLI Coding 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 Code

Overview

Claude Code brings agentic coding to the terminal: plan → act → observe. Day one is orientation — explore an unfamiliar repo safely.

Learning objectives

By the end of this session, you can:

  • Explain the core ideas behind: Claude Code: agentic coding in the terminal and the plan-act-observe loop.
  • Apply the ideas using Claude Code 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

Mental model

You are the tech lead; the agent is a capable junior who must show its work. Destructive commands need explicit approval.

Exploration prompts

Ask for architecture summary, entrypoints, and risky areas (auth, migrations).

Tooling for today

Primary tools: Claude Code. 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
From Vibe Coding to Agentic Engineering (Karpathy × Sequoia) — Why vibe coding raises the floor — and engineering raises the ceiling.

Course video

Open on YouTube
AI-driven Development for Programmers (Fireship) — Fast tour of AI coding workflows developers actually use.

Worked example / case study

Scenario

Install Claude Code; generate an architecture summary of an unfamiliar repo; sanity-check it.

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 Code.
  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: Claude Code: agentic coding in the terminal and the plan-act-observe loop.
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. Install Claude Code and have it explore an unfamiliar repo and summarize its architecture.

Coaching notes

Save the summary as docs/ai-architecture-skim.md.

Steps

  1. Set up or open the workspace required by: Claude Code.
  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
Claude Code: agentic coding in the terminal and the plan-act-observe loop.

## Context files
- (list paths)

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

## Definition of done
- Install Claude Code and have it explore an unfamiliar repo and summarize its architecture.

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

  • Approving commands unread
  • Exploring production databases
  • Expecting perfection without a clear goal

Key takeaways

  • Plan-act-observe is the loop
  • Exploration before edits
  • Human approval is a feature
  • Tools (Claude Code) change; the judgment skills transfer.

Resources

  • Official docs for: Claude Code
  • 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 26 of 65.

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