Lesson 5 of 65 · Free to read
Day 5 — Building a reusable prompt-pattern library (function, class, refact…
Month 1 · Week 1 — Mental Models & Environment Setup 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, GitHub Copilot
Overview
A prompt-pattern library turns one-off wins into team assets. Patterns for function, class, refactor, explain, test, and fix should live in Markdown next to the code.
Learning objectives
By the end of this session, you can:
- Explain the core ideas behind: Building a reusable prompt-pattern library (function, class, refactor, explain, test, fix).
- Apply the ideas using Claude, GitHub Copilot 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
Pattern anatomy
Name, when to use, anti-goals, template, example fill-in, verification step. Version the file in git.
Library hygiene
Retire patterns that stop working after model/tool updates. Tag patterns by tool (Copilot vs Claude).
Tooling for today
Primary tools: Claude, GitHub Copilot. 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
Course video
Worked example / case study
Scenario
Draft 8 patterns; use one to generate a real function; refine the pattern based on what failed.
Step-by-step
- Clarify the outcome in one sentence tied to the exercise below.
- Gather grounding context (files, docs, schema, acceptance checks).
- Run the primary tool(s): Claude, GitHub Copilot.
- Produce the smallest vertical slice that proves the idea.
- Verify with a command, test, screenshot, or side-by-side comparison.
- 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: Building a reusable prompt-pattern library (function, class, refactor, explain, test, fix).
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. Create a personal Markdown “prompt cookbook” with at least 8 reusable patterns you can paste into any tool.
Coaching notes
Store as prompt-cookbook.md with a table of contents.
Steps
- Set up or open the workspace required by: Claude, GitHub Copilot.
- Skim today's core concepts and watch the video(s) before prompting.
- Execute the task in small commits (or saved artifacts if no-code).
- Fill the success checklist below.
- 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
| Asset | Purpose |
|---|---|
| Prompt stub | Reuse today's structure (role → task → constraints → format) |
| Verification checklist | Tests / manual QA / security skim |
| Decision log | What you delegated vs kept human |
Copy-paste prompt skeleton
## Goal
Building a reusable prompt-pattern library (function, class, refactor, explain, test, fix).
## Context files
- (list paths)
## Constraints
- Stack: (fill)
- Do not: (secrets, drive-by refactors)
## Definition of done
- Create a personal Markdown “prompt cookbook” with at least 8 reusable patterns you can paste into any tool.
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
- Hoarding 50 near-duplicate prompts
- Never testing a pattern on a second task
- Keeping secrets inside cookbook examples
Key takeaways
- Reuse compounds weekly
- Patterns should include verification
- Cookbook belongs in the repo
- Tools (Claude, GitHub Copilot) change; the judgment skills transfer.
Resources
- Official docs for: Claude, GitHub Copilot
- 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 5 of 65.