CompCode Academy

Lesson 10 of 65 · Free to read

Day 10 ΓÇö Mini-project

Month 1 · Week 2 — GitHub Copilot Core 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: GitHub Copilot, Node/Python, Git

Overview

Mini-project day: ship a CLI tool mostly with Copilot. End-to-end means README, usage, and a clean GitHub repo — not a folder of scraps.

Learning objectives

By the end of this session, you can:

  • Explain the core ideas behind: Mini-project: a Copilot-built command-line tool.
  • Apply the ideas using GitHub Copilot, Node/Python, Git 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

Vertical slice for CLIs

Args → validation → core logic → persistence (file/JSON) → help text → README.

AI pair protocol

Outline commands first; implement one command at a time; test manually after each.

Tooling for today

Primary tools: GitHub Copilot, Node/Python, Git. 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
AI-driven Development for Programmers (Fireship) — Fast tour of AI coding workflows developers actually use.

Course video

Open on YouTube
Git and GitHub for Beginners (freeCodeCamp) — Commit, branch, push — the baseline every AI workflow needs.

Worked example / case study

Scenario

Task or expense tracker CLI with add/list/done; push with README.

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): GitHub Copilot, Node/Python, Git.
  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: Mini-project: a Copilot-built command-line tool.
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. Build a CLI task or expense tracker end-to-end, mostly via Copilot. Commit it to GitHub with a clean README.

Coaching notes

Include a sample session transcript in the README.

Steps

  1. Set up or open the workspace required by: GitHub Copilot, Node/Python, Git.
  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
Mini-project: a Copilot-built command-line tool.

## Context files
- (list paths)

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

## Definition of done
- Build a CLI task or expense tracker end-to-end, mostly via Copilot. Commit it to GitHub with a clean README.

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

  • Building flags nobody needs
  • No README / no example invocation
  • Giant single commit at the end

Key takeaways

  • Shipping teaches more than exercises
  • README is part of the product
  • Copilot is fastest inside a clear outline
  • Tools (GitHub Copilot, Node/Python, Git) change; the judgment skills transfer.

Resources

  • Official docs for: GitHub Copilot, Node/Python, Git
  • 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 10 of 65.

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