The best Claude Code prompts for beginners are not clever. They are specific about the result, clear about limits, and they ask for a plan before anything changes. Here are fifteen to copy, grouped by the kind of job, and the simple pattern behind all of them.

Each one assumes you have started Claude Code in a folder that contains the files involved — ideally a practice copy while you are learning. If you have not got that far, the Claude Code getting started guide takes about twenty minutes.

The pattern behind every good Claude Code prompt

Most weak prompts are missing one of four things:

  1. The job — what should be different when it is finished.
  2. The scope — which files or folder, and which to leave alone.
  3. The rules — naming, format, tone, anything you would tell a new assistant.
  4. The checkpoint — "show me your plan first" or "do one, then stop".

Compare "tidy up my photos" with "Rename every .jpg in this folder to its date taken, as YYYY-MM-DD_001.jpg. Do not touch other file types. Show me the first five new names before renaming anything." The second one cannot be misunderstood.

This is the same principle as prompting a chat assistant, with one addition — the checkpoint — because Claude Code acts on files. Our article on prompts that work and why the popular ones don't explains why tricks such as "act as an expert" add so little.

Safe first prompts

1. Look around

What is in this folder? Give me a one-line summary of each file, and tell me anything that looks duplicated or out of place. Do not change anything.

2. Explain what you would do

I want to [job]. Before doing anything, explain your plan step by step, list every file you would create or change, and wait for me to say go.

Use this in front of any request larger than a single file. It is the most valuable habit in this list.

3. Write a project note

Create a CLAUDE.md file for this folder that describes what the files are for, the naming conventions you can see, and anything I should always be asked about before it is changed.

The built-in /init command does a version of this for you. Either way, Claude Code reads the file at the start of every session in this folder, so you stop repeating yourself.

Files and folders

4. Sort by type

Sort the files in this folder into subfolders by type: Documents, Spreadsheets, Images, Other. Write a list of every move to moves.txt. Show me the plan first.

5. Rename consistently

Rename the PDFs in this folder to client_YYYY-MM_description.pdf, using the client name and date from the first page of each. If you are unsure about any file, list it instead of renaming it.

6. Find duplicates

Find files in this folder and its subfolders that are exact duplicates of each other. List them in groups. Do not delete anything.

Documents and writing

7. Summarise a pile of documents

Read every document in the Reports folder and create summary.md with one paragraph per document and a final section listing themes that appear in more than one.

8. Edit to a style

Edit draft.md for clarity and a friendly, plain tone. Keep my structure and all the facts. Save the result as draft-edited.md, then list the five biggest changes you made and why.

9. The same letter, many times

Using letter-template.md and contacts.csv, create one personalised letter per row in a Letters folder, named after the person. Do the first one, show it to me, and wait before doing the rest.

Data and spreadsheets

10. Answer a question from a spreadsheet

Using sales.csv, tell me the total per month and the three best-selling products. Show the numbers as a table, and tell me how you calculated them.

11. Clean up the data

Create a cleaned copy of contacts.csv: remove duplicate email addresses, put names in Title Case, and format dates as YYYY-MM-DD. Do not change the original file. Tell me how many rows changed.

12. Make a chart

Create a simple chart of monthly totals from sales.csv, saved as sales-chart.png, with a clear title and labelled axes.

A first small website

13. One page, from a description

Build a single-page website in this folder for my bakery: a heading, a short "about us" paragraph, opening hours, and a contact section. Use plain HTML and CSS, no frameworks. Tell me how to open it in my browser.

14. Change it in plain English

Make the heading larger, change the colour scheme to warm browns, and make the page look good on a phone.

When something goes wrong

15. Explain and undo

Explain exactly what you changed in the last step and why. Then undo it.

You can also use the /rewind command, or press Esc twice with an empty prompt, to roll back the conversation and Claude's file edits to an earlier point.

Prompts to avoid

  • "Clean up my computer." Too broad, too much reading, and far too much it could touch. Start Claude Code in one folder instead.
  • "Delete anything you think I don't need." Ask for a list, then decide yourself.
  • "Do whatever you think is best." It will — and "best" may not be what you meant.
  • Very long prompts covering five unrelated jobs. Do them one at a time, with /clear in between.

Save the prompts you reuse

When a prompt works and you will need it again next month, do not keep it in a text file — turn it into a Skill, and it becomes a slash command such as /monthly-invoices. Our Claude Code Skills explainer shows how. For bigger ideas, 10 things you can automate with Claude Code goes beyond one-off prompts to scripts that run on a schedule.

These fifteen are drawn from the same material as the free Prompt Toolkit that comes with Claude Code for Beginners: fifty prompts across writing, research and data, websites and files, automation, and a first-hour starter pack, plus a session cheat sheet. You can get the toolkit on the book's page without buying anything.

Frequently asked questions

Do Claude Code prompts need special syntax?

No. Plain English works. Slash commands such as /clear are separate from prompts, and @ followed by a file name points Claude Code at a specific file.

Why ask for a plan first?

Because correcting a plan takes seconds and correcting forty changed files does not. Plan mode, one of Claude Code's permission modes, makes this the default.

Are prompts for Claude Code different from ChatGPT prompts?

The writing principles are the same. The difference is that Claude Code acts on your files, so good prompts also define scope and include a checkpoint.