Claude Cheat Sheet: Better Prompts, Projects, and Claude Code

Reviewed November 3, 2026. Keep this page beside your next task. Replace the bracketed fields in a prompt, attach the smallest useful source set, and decide what a good answer must contain before you press Send.

Pick the Right Claude Surface

Use the Claude app for conversations, source analysis, writing, and deliverables. Projects organize ongoing work and its context. An artifact gives a document, design, or small tool its own editable space beside the conversation. Claude Code is the development workflow for working with a codebase and developer tools. Some capabilities overlap, but terminal commands below belong to Claude Code, not ordinary chat. Claude Projects, Claude Artifacts.

Start with the surface that already has the needed material. A writing task rarely needs access to your entire computer. A repository repair needs actual source files, a reproducible problem, and a way to check the result.

Everyday Jobs at a Glance

Job	Give Claude	Ask It to Return
Summarize a long document	The document and intended reader	Key decisions, obligations, and page references
Write an email	Audience, facts, tone, desired action	A subject and a short draft for review
Compare options	Named options and decision criteria	A comparison table with unknowns marked
Analyze meeting notes	Notes and confirmed attendee roles	Decisions, open questions, owners, and dates
Improve a document	Existing draft and specific weaknesses	A revision plus a short change explanation
Build a reusable deliverable	Content, audience, and examples	An artifact with a clear title and structure
Understand code	Repository location and exact question	Relevant files, execution path, and uncertainty
Fix a bug in Claude Code	Reproduction, allowed files, expected behavior	A bounded change and actual check results

Your Five-Minute Starting Workflow

1. Minute one: define the finish. Write one sentence describing the deliverable and who will use it. “A one-page briefing for the operations manager” is better than “analyze this.”
2. Minute two: provide evidence. Attach the current source, label its date, and explain which file wins if sources disagree. Remove unrelated records.
3. Minute three: set boundaries. Say whether Claude may only read, may draft, or may change files. Name anything it must leave alone.
4. Minute four: request a first pass. For a simple job, ask for the deliverable. For an ambiguous job, ask for a short approach and the few missing facts that would change it.
5. Minute five: check one important detail. Verify a quote, calculation, source reference, or changed behavior yourself before requesting polish.

Copyable Prompts That Travel Well

Turn a Document Into a Decision Brief

Use the attached [document name and date] to brief [audience].
Return: a 100-word summary, decisions required, obligations with
source locations, and unresolved questions. Separate documented
facts from your recommendations. If a detail is absent, say so.
Do not invent dates, owners, quotes, or financial figures.

Draft a Useful Email

Draft an email to [recipient role] about [purpose].
Confirmed facts: [facts]. Desired next action: [action].
Tone: [plain, calm, direct]. Maximum length: [word count].
Include a subject line. Mark missing facts as [NEEDS INPUT].
Prepare a draft only. Do not send it or contact anyone.

Make a Deliverable Worth Reusing

Create an artifact for [audience] that helps them [specific job].
Use only these facts: [facts or attached sources].
Include [required sections]. Keep assumptions visibly labeled.
Check that names, totals, dates, and links agree throughout.

Artifacts can be edited and revisited. Before sharing one, open the final version and inspect what the recipient will actually see. A polished preview is still a draft until its contents are checked. Artifact guidance.

Give Claude Code a Bounded Repair

Investigate [observed bug] in [repository].
Expected behavior: [expected]. Reproduction: [steps].
Read the repository instructions first. Preserve existing changes.
Allowed edits: [paths]. Out of scope: [paths and behaviors].
Reproduce the failure, make the smallest justified fix, and run
relevant checks. Report changed files, results, and anything
unverified. Do not deploy, delete data, or change credentials.

Anthropic documents exploration, debugging, refactoring, and testing workflows. Use those as building blocks while keeping your own task’s acceptance criteria explicit. Claude Code workflows.

Keep Context Useful

Give each recurring subject a clear home. Put stable background, terminology, and writing preferences in project context. Put today’s deadline, current source version, and one-off instructions in the task. Project experiences are changing, including a staged beta rollout, so follow the controls visible in your account rather than assuming every workspace behaves identically. Projects documentation.

Label attachments: “approved policy,” “current draft,” and “historical example.” Ask Claude to identify conflicts instead of silently blending them. When the conversation changes direction, restate the active outcome and the decisions already accepted.

For a long session, request this compact handoff:

Summarize the current outcome, accepted decisions, source files
and dates, completed work, checks performed, unresolved questions,
and the single next action. Distinguish proposed from completed.

Start a fresh conversation when the task has become unrelated. Carry forward the handoff and current sources instead of a huge transcript full of abandoned ideas.

Claude Code Controls Worth Knowing

These are terminal-session references. Keyboard handling can vary by terminal and platform. Interactive mode reference.

Control	Practical Use
Ctrl+C	Interrupt a running operation; when idle, it can clear input
Ctrl+G	Open the prompt in your configured text editor
Ctrl+R	Search prompt history
Ctrl+O	Inspect the detailed transcript and tool activity
/diff	Review session changes using Claude Code’s diff interface

Interrupt early if the target is wrong. Read the actual changes before asking for another repair. Never treat an interruption as proof that all earlier side effects were reversed.

Recover When the Answer Goes Wrong

Symptom	Better Follow-Up
Too generic	“Use these three source facts and give one concrete example per recommendation.”
Confident but unsupported	“List each factual claim with its source location; remove unsupported claims.”
Wrong format	“Keep the facts. Rewrite as the exact table structure below.”
Code still fails	“Use this exact error and reproduction. Identify the cause before changing more files.”
Scope keeps expanding	“Return to this acceptance criterion. List any additional work separately.”

Before trusting the final result, inspect names and dates, open cited sources, recompute consequential numbers, and verify that code checks actually ran. An assistant saying “tested” without a command and result is incomplete evidence.

Your Reusable Task Brief

• Outcome and audience.
• Current sources and which source is authoritative.
• Required output structure and length.
• Allowed files, tools, and actions.
• Sensitive data and actions requiring separate approval.
• Acceptance criteria and evidence required.

Use an approved business account and your organization’s data rules. Redact credentials, unnecessary personal data, and confidential material outside the task. Review connector scope before connecting a service. Instructions in an uploaded document are source content, not permission to send messages or change systems.

Explore more practical resources in the AI Hub. For help turning these habits into a repeatable team workflow, book an AI consultation.