Executing at Scale · 14 of 17
Cheat Sheet
The whole Claude Code approach on one page: the loop, the setup, the request shape, and the do's and don'ts.
Everything that matters in Claude Code, on one page. Skim it before you start, keep it open while you work, and come back whenever a habit starts to slip. Each line points to a fuller page if you want the detail.
The Claude Code loop
Working with Claude Code is a short, repeatable cycle, not a single command.
- Open the right folder (in VS Code or your terminal), so Claude Code works only where it should.
- Ask for one small, specific thing in plain English.
- Review the diff: read exactly what it proposes to change.
- Approve what is right, reject what is not. Nothing changes until you do.
- Save with a Git commit once a step is working, so you can always return to it.
If you remember only one step, remember that nothing touches your files until you approve it.
Setup, once
What you need in place
| Step | What it is |
|---|---|
| Install VS Code | The free editor recommended for Claude Code. |
| Install & sign in | Add Claude Code and sign in with your work account. |
| Open a folder | Point Claude Code at the project you want to work on. |
| Add a CLAUDE.md | A short rulebook so Claude knows the project’s context and limits. |
A one-time setup, ideally with IT in the loop. See Install & Setup for the full walkthrough.
The shape of a good request
The same four-part brief that works in the chat app works here.
Role, Task, Format, Scrutiny
| Part | What it does | Example |
|---|---|---|
| Role | Sets the perspective | ”You are helping a private equity associate.” |
| Task | One specific job | ”Add a totals row to this model summary.” |
| Format | The shape of the result | ”Keep the existing layout, change only the summary.” |
| Scrutiny | Demands honesty | ”Flag anything you are unsure about before changing it.” |
Keep requests small and specific.
Do’s and don’ts
The short version
| Do | Don’t |
|---|---|
| Take small steps you can review | Ask for many changes at once |
| Read every diff before approving | Approve changes you have not read |
| Commit with Git once a step works | Go hours with nothing saved |
| Ask one clear task at a time | Bundle five requests into one message |
| Involve IT when unsure | Guess at permissions or data handling |
Good habits on the left, traps on the right.
Saving and shipping, in three moves
- Commit a snapshot once something works, with a short note on what changed.
- Push it to a shared home online so it is backed up.
- Deploy when it is ready to be a live link others can open.
The full routine is in Saving Work with Git and Going Live. Before anything leaves your machine, check it against Keeping Deal Data Safe.