Best Practices · Optional
Cheat Sheet
A dense one-page reference: the core loop, the prompt shape, and the do's and don'ts.
Everything that matters, on one page. Skim it before a task, keep it open while you work, and come back to it whenever a habit starts to slip. Each line points to a fuller page if you want the detail.
The core loop
Good use of Claude is a short, repeatable cycle, not a one-shot command.
- Set up the right workspace and context (your work account, the right Project, the relevant files).
- Brief Claude with a clear, four-part prompt.
- Read the answer for substance, not volume.
- Refine the parts that are off with a follow-up.
- Verify every figure, quote, and claim against the source before it leaves your desk.
If you remember only one step, remember the last one.
The four-part prompt shape
Every strong prompt says four things. Skip one and you feel the gap.
Role, Task, Format, Scrutiny
| Part | What it does | Example |
|---|---|---|
| Role | Sets the perspective | ”You are assisting a private equity associate.” |
| Task | States the job, with a specific verb | ”Summarize this teaser for an initial screen.” |
| Format | Names the shape of the answer | ”Four headings, bullets under each, one page.” |
| Scrutiny | Demands honesty about limits | ”Flag anything vague or unusual.” |
The backbone of almost every good prompt. See Anatomy of a Good Prompt for the full version.
Do’s and don’ts
The short version
| Do | Don’t |
|---|---|
| Verify every number against the source | Trust fluent output you have not checked |
| Make the confidentiality call before uploading (the checks) | Drag a document in and start working |
| Brief precisely with role, task, format, scrutiny | Send a vague one-line request |
| Keep each deal in its own Project | Mix several deals in one conversation |
| Refine a good draft with a follow-up | Restart from scratch every time |
| Keep the final judgment with you | Ask Claude to make the decision |
The positive habits on the left, the traps on the right.
When to use a Project
A quick rule: if you will return to the same material more than once, use a Project rather than a loose chat.
- Use a Project for a live deal (its own siloed space, its documents loaded once) and for a repeated function you do across deals (a standing setup with reusable instructions).
- Use a plain chat for a quick, throwaway question that needs no saved context.
- One engagement, one Project: it keeps context clean.
See What Projects Are and Setting Up a Deal Project for the detail.
Verification, in three checks
Before anything reaches a deliverable:
- Numbers: find every figure in the source, exactly, in context.
- Claims and quotes: confirm the source actually says it.
- Gaps: skim the source for anything material the answer left out.
The fuller routine is in Verify Everything.
Five prompt patterns worth knowing
- Refine, don’t restart: fix the wrong 20 percent with a follow-up.
- Show the working: ask for reasoning before the conclusion.
- Structured comparison: ask for a table with fixed rows and “not stated” for gaps.
- Devil’s advocate: tell Claude to argue against your thesis.
- Constrain the output: name the length, headings, and tone precisely.
Full versions in Anatomy of a Good Prompt.