# Get More From Claude

The prompts from the guide, ready to paste. Fill in anything in [square brackets] first.

From Kristen Parise BSc MSc BHScPT · kristen@blueberrytherapy.ca

## Prompt 1 · Write the prompt for me

```
I want [what you want, for example a weekly update email to my team] for [who it is for, for example my five-person clinic team]. Help me write the prompt. Ask me what you need to know first.

1. Ask me, all at once: what a great result looks like, whether I have an example I love, and anything else you need to know. Wait for my answers.
2. Write the prompt I should use, addressed to you, with my answers built in and any fill-ins left in [square brackets].
3. Tell me in one line to paste it into a fresh chat, and anything I need open first (a file, a folder, a connector).
Then stop. Next: run the prompt in a fresh chat, and bring the result to Prompt 2.
```

## Prompt 2 · Diagnose, don't fix

```
List every problem you see with this. Number them. Do not fix anything yet. I will tell you which ones to fix.

[paste the draft here, or name the file if I am working in a folder]

1. One line per problem, numbered, most serious first. Say what is wrong, not how you would fix it.
2. Wait for my list of numbers.
3. Fix only the ones I name, with the smallest change that solves each. Leave everything else exactly as it was, including anything you flagged that I did not pick.
Report what you changed, by number. Then stop.
```

## Prompt 3 · Parallel work (Claude Code)

```
Do these in parallel as mutually exclusive scoped tasks, then merge:
1. [task, naming the file or piece it may touch]
2. [task, naming a different file or piece]
3. [task, naming a different file or piece]
Merge means: [what you want at the end, for example one page called merged.md that puts the three together in that order, or "check the three agree and fix any seam"].

Rules: no two tasks touch the same file. If a task finds something outside its own file that now contradicts it, leave that file alone and put it in the report. When all three are done, do the merge as one pass.
Report the three results and what the merge changed, in five lines or fewer. Then stop.
```

## Prompt 4 · Handoff

```
Summarize where we are: what is done, what decisions I still need to make, what is next, and what problems are open. Write it so a fresh chat can pick up without reading this one.

1. Go back to the start of this chat (or the start of the summary I pasted), not the last few turns. Use these five headings: Done (with file names or links), Decisions (two lists, Made and Open), Next (the first step concrete enough to start on with no question), Open problems (say "I assumed" wherever you guessed), Rules I stated in this chat (my corrections, and anything I said to leave alone). Where I changed my mind, keep only the final version.
2. Leave out every client or patient name and any health detail about a person.
3. Show me the five sections and ask me to correct anything wrong or missing. Wait.
4. After my corrections, save it as handoff-[today's date, written YYYY-MM-DD].md if you can write files, and print a short opener I can paste into a new chat, under 400 words, that begins "Picking up from a handoff". If you cannot write files, say so, and make the opener carry all five sections instead, under 600 words.
Then stop. This chat is done.
```

## Prompt 5 · Fan out, fan in (Claude Code)

```
Use a fan-out and fan-in strategy. Delegate to cheap subagents to find as much as possible about [the question, for example ways a small clinic can cut no-shows], including approaches most people don't use. Then combine it all into one brief and make the recommendation.

1. Split the field into at least four angles and send one helper per angle. Each helper reports a list of approaches, one line each, with a source or example where it can find one. Mark any source it could not check as unverified.
2. Combine everything into one brief: every approach found, grouped, with the three least common marked.
3. Make the call: one recommendation, why, and what it would take to try it within a week.
Save the brief as [filename] and give me the recommendation in three lines. Then stop.
```

## Prompt 6 · Retro

```
How could you have done that faster with fewer tokens? Give me one lesson, written as what to do next time, and add it to my preferences file.

1. Look back over [the whole build in this chat, or name the build] with evidence: a file read twice, a wrong path tried, a check skipped, rework after I corrected you. List up to five, one line each. The lesson may be for you, or for how I asked.
2. Pick the one most likely to come up again. Write it as a single instruction in the positive, under 30 words. "Batch the file reads", never "Don't retry".
3. Add that one line under a heading called Lessons in my preferences file ([CLAUDE.md, or the file where I keep how I like to work]). Change nothing else in that file. If you cannot write files, print the line and tell me to paste it into my Project instructions.
Report the lesson and where you put it, in two lines. Then stop.
```
