Claude Code for non-developers

Claude Code sounds like a tool for programmers, but at its core it is Claude working directly in a folder on your computer. That makes it useful for marketers, founders, content editors and project managers too. This article shows what you can do with it, how to set it up without a terminal and how to work safely.

What it is good for

If the work lives in files, Claude Code can probably help. Some examples:

• Website text. Update copy, prices or team bios on a site built with a framework such as Astro, without hunting through folders yourself.
• Files and folders. Rename 200 photos by date, sort documents into folders, find duplicates.
• Spreadsheets and data. Clean a messy CSV export, merge two lists, compare this month’s numbers with last month’s.
• Documents. Turn a folder of meeting notes into one summary, or convert Markdown files to another format.
• Small tools. A script that resizes images or checks a list of links, built and explained by Claude.

The difference with a normal chat: you do not copy and paste. Claude opens the files, makes the changes and shows you exactly what it changed.

Set it up without a terminal

You need a paid Claude plan (Pro, Max, Team or Enterprise).

1. Install the Claude desktop app from claude.com/download and sign in.
2. Click the Code tab.
3. Choose Local.
4. Click Select folder and choose the folder you want to work in.
5. Pick a permission mode next to the send button (see below).

Tip: Only open the folder you need, not your whole Documents folder. Claude can only work in what you give it, and a smaller folder keeps things safe and fast.

Choose how much control you want

The permission mode decides when Claude asks before acting.

Mode	What happens	Use it when
Manual	Claude asks before every file change or command	You are starting out or the folder is important
Plan	Claude only reads and proposes a plan, no changes	You want to agree on the approach first
Accept edits	Claude changes files without asking each time; you review afterwards	You trust the task and want speed
Auto	A safety check reviews actions in the background and blocks risky ones	You are experienced and the task is routine

Start with Plan for anything bigger, switch to Manual to carry it out, and only move on to faster modes once you are comfortable.

A safe first workflow

1. Make a backup. Copy the folder, or ask Claude: “Set up Git version control for this folder so every change can be undone, and explain in two sentences what that means.”
2. Ask Claude to look first. “Look through this folder and tell me in plain language what is in it. Do not change anything.”
3. Describe the outcome you want. Be as specific as you would be with a colleague.
4. Review the plan. Ask questions until it makes sense.
5. Let Claude do it and review each change in the diff view (red is removed, green is added).
6. Check the result yourself: open the file, view the page, look at the spreadsheet.

Example requests

Website text:

On the About page, change the opening paragraph to the text below.
Keep the layout the same. Show me the change before you save it.

[new text]

Data clean-up:

The file leads-export.csv has duplicate rows and inconsistent country
names (NL, Netherlands, Nederland). Make a cleaned copy called
leads-clean.csv: one row per email address, country names in English.
Do not change the original file. Tell me how many duplicates you removed.

File tidying:

Rename all photos in the "event-2026" folder to the format
2026-05-14-001.jpg, based on the date each photo was taken.
First list ten examples of old and new names so I can check.

Tip: Type @ followed by a file name to point Claude at a specific file. You can also drag files into the prompt box.

When something goes wrong

• Claude is going the wrong way: click stop and type a correction. You do not have to start over.
• You do not like a change: reject it in Manual mode, or ask Claude to undo it. With Git set up, you can always go back to an earlier version.
• You do not understand what Claude did: ask “Explain what you just changed and why, without jargon.”

Warning: Be careful with anything that publishes, sends or deletes: pushing a website live, emailing a list, removing files. Ask Claude to stop before those steps so you can check first.

Make it remember your preferences

If you work in the same folder often, ask Claude to create a CLAUDE.md file with notes about the project and how you like to work. Claude reads it at the start of every session. See Write a CLAUDE.md.

Want a hands-on session where we set this up together for your own website or files? Book a strategic call: https://calendly.com/marrallisa/30min

Next steps

• Install Claude Code
• Write a CLAUDE.md
• Edit your site with Claude Code