Readers only.
Enter the password.
This page is for readers of the book. The password is in your copy.
That password doesn't match. Check your copy of the book.
58 prompts and skills.
Built to Repeat.
A working set for taking a design project from kickoff to handover with AI, organised by the five stages of Built to Repeat.
Start with the two set up prompts. Write your context block once, paste it into every prompt after that, and work through the stages in order. Replace anything in square brackets with your project details. Install the skills if you use Claude.
These prompts have been updated since the book. My process for using AI has improved, so I have rewritten, merged and removed some of the originals, and added new ones for each stage of Built to Repeat. If you are looking for a prompt from the printed edition and cannot find it, it was either folded into a stronger one here or dropped.
- 01Kickoff
- 02Research
- 03UX practice
- 04Visual design
- 05Testing and output
Accessibility at every stage. 53 prompts and 5 skills.
Nothing matches that. Try a shorter word, or clear the search.
Set up before you prompt
Write your project context once and make the AI ask questions before it answers. Every other prompt in this library points back to the context block, so do this first.
Kickoff: start with the right problem
Align on the real problem, ownership, success criteria and constraints before design begins. Accessibility starts here, not at the end.
Research: ground it in reality
Commission, participate or validate. It is a deliberate decision, and the design does not move on until the evidence is in.
UX practice: the thinking layer
Journeys, flows, IA and competitive analysis. The thinking happens here, before the visuals, and it ends with a senior review.
Visual design: make it real
Visuals and prototypes on the shared design system. Fidelity matched to the decision, no higher, and the words are part of the design.
Testing and output: the reasoning is the work
Targeted testing, handover, and the design reasoning written down next to every deliverable, so decisions outlast the people who made them.
Design systems: build it once
Audit what you have, set up tokens and components, and keep the system alive after launch. Run these in order the first time.
Skills: teach Claude your process
A skill is a folder with a SKILL.md file that tells Claude how to do one job your way. Each card below is a complete SKILL.md. The prompts above work in any AI tool. Skills are Claude only.
- Create a folder with the skill's name, for example design-kickoff-brief.
- Copy the card's text into a file called SKILL.md inside that folder.
- In Claude.ai: zip the folder, then upload it in Settings. Skills need a paid plan with code execution turned on.
- In Claude Code: put the folder in ~/.claude/skills/ for all projects, or .claude/skills/ inside one project.
- Skills do not sync between Claude.ai and Claude Code. Install in each place you use.
- Ask for the job in plain words, for example "run the kickoff brief on this ticket". Claude loads the skill when your request matches its description.
Career and job search
Not part of Built to Repeat, but the same habit applies: treat the search like a design problem. These are carried over from the book.