Ch10 Daily Workflow

# Chapter 10 prompts — Your Repeatable Workflow

**Hour block: hours 47-48** of the book's 48-hour build.

> **Access requirement:** every prompt below is pasted into an interactive Claude
> Code terminal session, and Claude Code requires Pro or higher — the free plan
> does not include it (ch03:31). This repository never runs any of these prompts,
> and neither does its CI. They are documentation, not executable code.

**The full pack, with every prompt transcribed verbatim: [`prompts/ch10-daily-workflow.md`](../../prompts/ch10-daily-workflow.md)**
The pack is the source of truth for exact prompt text; this page is the guide to
navigating it.

## What this chapter's prompts do

The first project felt magical; a lot of people never manage a second one, because
what felt like magic was actually a system, and most people never write the system
down. This chapter extracts it: a morning-start prompt, the five-step build cycle
(set effort, give a scoped prompt, review the output, test, start fresh), an
end-of-day summary prompt, a one-page daily checklist, five reusable prompt
templates covering every kind of change the book makes, and a planning-conversation
prompt for projects bigger than the Task Tracker. It closes by turning everything
the book built — CLAUDE.md, design system, `.gitignore`, prompts, security
checklist, cleanup routine — into a starter kit you copy into every new project.

## When you use them

Hours 47-48, the book's last chapter — after the app is built, styled, secured,
tested, cleaned up, and monetized (Chapters 3-9). Nothing new needs to exist first;
this chapter is about the process you take *away* from the Task Tracker into your
next project, not a new feature on this one. `starter-kit/` in this repository is
the seven-file starter kit the chapter describes, filled in with the book's own
values so you can see the finished shape before you genericize it for your own
stack — see [`docs/starter-kit.md`](../starter-kit.md).

## Index of every prompt in the pack

| # | Prompt | Cite | What it does |
|---|---|---|---|
| 1 | Morning start | ch10:25-36 | Runs the test suite and shows the last 3 commits, at low cost, to orient before building |
| 2 | End of day | ch10:56-65 | Summarizes what changed today, as a list of files and one paragraph |
| 3 | New feature template | ch10:138-204 | `Add [feature] to [component]. Files: [...]. Follow the design system. Write tests.` |
| 4 | Bug fix template | ch10:138-204 | `Bug: [...]. Expected: [...]. File: [...]. Fix it and run tests.` |
| 5 | Code review template | ch10:138-204 | Reviews a file for unused code, security issues, TypeScript errors, and performance problems |
| 6 | Database change template | ch10:138-204 | Adds a field to a model, migrates, and updates the relevant form and list |
| 7 | Visual polish template | ch10:138-204 | Pastes a screenshot and names specific issues to fix, per the design system |
| 8 | Filled-in: new feature | ch10:185-200 | The new-feature template completed for a real due-date picker |
| 9 | Filled-in: bug fix | ch10:185-200 | The bug-fix template completed for a completed-tasks-still-showing bug |
| 10 | Filled-in: database change | ch10:185-200 | The database-change template completed for a `priority` field |
| 11 | The planning conversation | ch10:112-118 | For 5+ data models or 10+ pages: plans the data model, pages, and feature list before building anything |

11 prompts.

## The signature prompts

### ⭐ `prompts.md`'s five templates (ch10:138-204)

The copyable file is [`starter-kit/prompts.md`](../../starter-kit/prompts.md).

**New feature:**