Productive— faster every day
For your professionTeachersStudentsManagersMarketingDevelopersFreelancersParents

Prompt library · AI · 10 prompts

Prompts from the guide

Claude Code: a personal automation engine, not just for developers

10 prompts from this guide. Fill in whatever sits in [square brackets] — your own context, the document text or the name of your tool. That context is exactly what separates a generic answer from a usable one.

Read the full guide →

What you need

I want to install Claude Code on [macOS / Windows 11].
I've never worked in a terminal before and I don't have
Node.js or anything like that installed.

Write me a step-by-step guide:
1. how do I open the terminal on my system
2. exactly what to type, line by line
3. how do I know each step worked (what should print out)
4. what do I do if a permissions error shows up
5. how do I confirm at the end that the tool is running

For each command, write one sentence explaining what it does.
Don't assume any prior knowledge and don't use terms you
haven't explained.

First run: a safe playground

You're in a practice folder I'm using to try out what you
can do. Don't delete anything.

1. Go through this folder and all subfolders and give me an
   overview: how many files there are, what types, how big,
   how old.
2. Show me the 10 oldest and 10 largest files.
3. Find files that look like duplicates (same content or
   nearly the same name) and list them in pairs.
4. Suggest a reasonable way to sort this folder — but don't
   move anything yet, just write me a plan.

Answer briefly and put the results in a table.

Task 1: cleaning up a folder where nothing can be found

The folder [path] has [about 900] files from the last few
years. I want to clean it up, but carefully.

Steps:
1. First give me an overview: file types, counts, total size,
   oldest and newest.
2. Suggest a folder structure by type and year, for example
   documents/2024, invoices/2025, images/2023. Show me the
   proposed tree and how many files would go into each folder.
3. List separately the files you're not sure how to classify,
   and files that look like duplicates.
4. Don't move ANYTHING yet. Wait for me to approve the plan.

Rules: never delete anything, not even duplicates. Keep the
original creation dates. If a file has no extension in its
name, or is corrupted, put it in a review/ folder and give
me a list.

Task 2: bulk renaming based on content

The folder [path] has [420] scanned documents named things
like scan_0042.pdf. I want to rename them based on content.

Name pattern: YYYY-MM-DD_document-type_counterparty.pdf
For example: 2025-03-14_invoice_alpha-services.pdf

Rules:
- figure out the document type from the content: invoice,
  contract, statement, confirmation, other
- take the date from the document, not the file's timestamp;
  if there's no date in the document, use the file's date and
  add a _nodate flag at the end of the name
- write the counterparty name in lowercase without accents,
  replace spaces with hyphens, shorten to 3 words
- if you're less than 90% sure about the content, do NOT
  rename the file — write it to a review.txt file with a
  reason instead

Do it on 10 files first and show me a table: old name → new
name → what you read from the document.

Task 3: extracting data from a stack of PDFs

The folder [path] has [180] invoices in PDF. Build a single
CSV file, invoices.csv, from them.

Columns, in this order:
file, vendor, tax ID, invoice number, issue date, due date,
amount before VAT, VAT rate, amount with VAT, payment
reference, confidence

Rules:
- semicolon delimiter, UTF-8 encoding, decimal comma
- dates in YYYY-MM-DD format
- amounts as a plain number, no currency symbol and no
  thousands separators
- if a value isn't in the document, leave the cell empty;
  do NOT guess or calculate anything
- in the confidence column, write high / medium / low based
  on how legible the document is
- for handwritten scans, always mark confidence as low

Process 10 files first, show me the result, and wait.
At the end, tell me how many invoices don't add up — where
the amount before VAT plus VAT doesn't equal the amount with
VAT.

Task 4: a monthly report that generates itself

I have a file [data.csv] with [sales for the past year]. The
header and first three rows look like this:

[paste 4 rows here, including the column headers]

Write a Python script, report.py, that:
1. loads the file (semicolon delimiter, UTF-8, decimal comma)
2. cleans the data: drop rows missing [key column], unify
   the spelling of [column], and convert dates to real dates
3. calculates a monthly summary: count, sum, average, median
4. calculates the top 10 [category] by [metric] and their share
5. compares the last month to the previous month and to the
   same month last year, in percent
6. saves the numbers to results.csv and three charts to
   charts/ as PNG
7. at the end, prints a summary in plain English: what went
   up, what dropped, where the data looks suspicious

Comment each step in English, explaining WHY it's there. The
script has to hold up even with empty cells. Then run it and
show me the output.

Task 5: managing a website and other text-based projects

This folder holds a [website / documentation] made up of
[markdown] files in a [content/] folder.

Run a consistency check for me and return one summary:
1. files missing a required field in the header (required
   fields: [title, description, date, category])
2. links inside the project that point to a file that doesn't
   exist
3. duplicate or very similar titles
4. texts shorter than [1500] characters and longer than
   [30000]
5. places using straight quotes instead of proper typographic
   quotes
6. typos in recurring terms (list the variants of the same
   term that appear across the project)

Don't fix anything, just list the findings with the file path
and line number. Sort them by severity.

What to put in it

I want to set up a CLAUDE.md file with permanent instructions
in this folder, so you behave the same way every time you
start up again.

First look around the folder, then write a draft that
includes:
1. What this folder is for (I'll tell you: [description])
2. The folder structure and what goes where
3. Conventions: file names, date format, encoding, language
4. Procedures for three recurring tasks I do here:
   [task A], [task B], [task C] — for each one, the steps and
   the output
5. Hard rules: what to never delete, what to never send, when
   to ask instead of deciding
6. Where to save outputs and backups

Write it concisely, in bullet points. Phrase it as
instructions for yourself, not a description for a human.
Where you're not sure what applies to this folder, write a
question and leave it for me to fill in.

How to maintain it

We just finished [task]. Go through what we did today and
suggest what should be added to CLAUDE.md, so I don't have
to explain it again next time.

List only concrete sentences to add, and for each one note
which section it belongs in and why. Don't write anything
yet — I want to approve it first. Skip anything that only
applied today, and anything I wasn't sure I wanted permanent
myself.

When in doubt, ask for the plan

I want to [task description] in the folder [path].

Don't do anything yet. Write me:
1. an exact plan of the steps, in the order you'd carry
   them out
2. for each step, which files would change, move, or get
   created — and roughly how many
3. what about this is irreversible and what can be undone
4. what happens if you run into something unexpected in the
   data
5. how I would verify the result is correct once it's done
6. what you'd back up before running this, in my position

Then wait. Don't run anything until I approve the plan.

All prompts