Book 5 — Companion Materials

Templates & Resources

Ten downloadable starting points for the labs in The 30-Day Developer Pivot. Fill them in rather than staring at a blank page. Each file maps to a specific chapter and day so you know exactly when to reach for it.

// Plain markdown. Works in VS Code, Obsidian, iA Writer, or any text editor. No account required.

Boilerplate Manifest Template

Week 1 · Ch1/Day7

Pre-formatted manifest with all the tables from the Boilerplate Inventory lab. Categorise every task you currently do manually before handing any of it to the AI.

| Task | Frequency | Time cost | Automatable? | |------|-----------|-----------|-------------| | [your task here] | daily / weekly | ~N min | yes / partial / no |

Prompt Template Card

Week 2 · Ch2/Day2

The CONTEXT → TASK → CONSTRAINTS → FORMAT reference card with a worked example and language-specific inserts for Go, Python, TypeScript, and Rust. Pin it while you work.

## CONTEXT [Language] project. [Framework]. [Relevant background]. ## TASK [What you want the AI to produce, precisely.] ## CONSTRAINTS [What it must not do / what it must integrate with.] ## FORMAT [The exact shape of the output you want.]

Prompt Library — Starter Pack

Week 2–5 · Ch2/Day6

15 tested prompts across 7 categories: architecture, refactor, test, debug, explain, optimise, document. Use as-is or adapt for your stack. Naming convention included.

Categories: ARCHITECTURE · REFACTOR · TEST DEBUG · EXPLAIN · OPTIMISE · DOCUMENT 15 prompts, each with CONTEXT/TASK/CONSTRAINTS/FORMAT structure and notes on where to customise for your stack.

Proof of Concept README

Week 3 · Ch3/Day6

Professional README template for your Week 3 GitHub portfolio piece. Clone it into the repo before you write a single line of code. Fill it in as you build, not after.

# [Project Name] > One sentence: what this does and why it exists. ## What it demonstrates ## How it was built (the AI-augmented part) ## How to run it ## What you would do next

Rate Card Template

Week 4 · Ch4/Days 1–4

Hourly archaeology worksheet plus a three-tier rate card with actual arithmetic. Complete the worksheet on Day 1 before you make any rate decisions on Day 4.

TIER 1 — Execution (you build it) $[X]/hr TIER 2 — Direction (you direct the AI) $[Y]/hr TIER 3 — Strategy (you own the outcome) $[Z]/hr Worksheet: current rate → multiplier → justified new rate

Rate-Change Pitch Memo

Week 4 · Ch4/Day6

A ready-to-adapt memo for communicating a rate increase to existing clients, plus notes on the conversation itself. Fill in the numbers from your rate card worksheet.

Subject: Updated project rates — [Your Name] Hi [Name], I want to give you advance notice of a rate change effective [date]... [Framed around increased output, not increased cost.]

LinkedIn Bio Templates

Week 4 · Ch4/Day5

Five headline variants, three About section templates, an Upwork bio, and a portfolio project description format — all positioned around AI-augmented engineering.

HEADLINE VARIANTS (pick one, adapt): → Senior [Language] Engineer · AI-Augmented Development → Developer who ships at 10× · [Stack] + Claude/Copilot → I build the thing. The AI writes the boilerplate.

Escape-Hatch Delegation Playbook

Week 5 · Ch5/Day4

A template for delegating one complete category of work — to an AI, a junior, or a future version of yourself. Documents the trigger, the inputs, the process, and the acceptable output.

## Playbook: [Category of work] Trigger: When [condition], hand this off. Inputs required: [what the handoff needs to succeed] Process: [the steps, written for someone else] Definition of done: [what good looks like]

How We Build Code Now

Week 5 · Ch5/Day6

A team-facing document template for sharing your AI-augmented workflow with colleagues or clients. Works equally well as a one-person manifesto for future reference.

## How We Build Code Now ### What changed ### Our current toolchain ### What the AI handles / what we handle ### How we review AI-generated code ### Where to ask questions

Weekly Lab Checklists

All 5 weeks

All five weeks of daily deliverables as tickable checklists, plus a 30-day summary table. The single file you need open alongside the book for the full 30 days.

## Week 1 — The Boilerplate Inventory (Days 1–7) - [ ] Day 1: Install and configure your primary AI coding tool - [ ] Day 2: Complete the boilerplate manifest for one project - [ ] Day 3: Run your first CONTEXT/TASK/CONSTRAINTS/FORMAT prompt ...

When to use each resource

Week 1

Start with Weekly Checklists open throughout. Complete the Boilerplate Manifest on Day 7 — not before, once you have seven days of observation to draw on.

Week 2

Pin the Prompt Template Card on Day 2 and keep it visible. Seed your personal Prompt Library from Day 6 onwards — one prompt per task you repeat more than twice.

Week 3

Clone the POC README into your new repository on Day 1 of this week, before any code exists. Fill it in as you build. This discipline forces clarity on what you are actually demonstrating.

Week 4

Run the Rate Card worksheet arithmetic on Day 1. Do not look at the Pitch Memo until you have real numbers. Update your LinkedIn Bio on Day 5 — after the rate decision, not before.

Week 5

Use the Delegation Playbook template to document one complete category of work on Day 4. Write the How We Build Code Now document on Day 6 as if you are explaining this to a future colleague.