Teaching Claude your setup: memory and skills
⏱ 20 min5 steps
Every time you explain the same thing to Claude twice, that's something to teach it once. There are three ways, from simplest to most powerful: files, and skills. You'll set up one of each.
Your first probably won't come out right. Nobody's does. You fix it the way you'd fix a recipe, one line at a time.
CLAUDE.md A note to Claude about how to work in this project. Claude Code reads it at the start of every session in that folder. All wordsauto memory Notes Claude Code saves for itself about you and your project, so it remembers them next time. All wordsskill A saved set of instructions for one kind of job. Claude uses it when the job comes up, or when you type its name. All wordsBefore this, you'll want:
Steps
Start Claude Code in your my-idea folder
-
Open (Cmd+SpaceWindows key, type Terminal, press Enter).
-
Go to your my-idea . Type this and press Enter:
cd ~/Backyard/my-ideacd ~\Backyard\my-idea -
Check the says my-idea.
-
Start . Type this and press Enter:
claude
You should see:
Claude Code's name and version at the top, a line starting with ❯ where you type, and ⏵⏵ on in the bar at the bottom.
auto mode Claude works without asking, and a separate safety checker blocks anything risky. All wordsThat's not what I see
- It says "cd: no such file or directoryCannot find path … because it does not exist".
- The my-idea folder isn't there. It comes from Check the idea first and The three files, so do those first, then come back.
- It says "zsh: command not found: claudeThe term 'claude' is not recognized".
- This Terminal window doesn't know about Claude Code. Close the window with Cmd+WCtrl+Shift+W, open a new one and try again. If it still says that, go back to Claude Code and .install Put a new program on your computer so you can use it. All wordssign in Tell Claude Code which Claude account is yours, so it knows you've paid for it. All words
-
Write the rules you want in every project
CLAUDE.md files are notes Claude reads at the start of every . You already have one in your project. There's also a personal one, at ~/.claude/CLAUDE.md~.claude\CLAUDE.md, that Claude reads in every project.
This asks Claude to interview you about how you like to work, then write your personal CLAUDE.md with a few safe rules already in it.
- Copy the prompt below.
Create or update my personal CLAUDE.md at ~/.claude/CLAUDE.md, which you read in every project. Interview me, one question at a time, about how I like to work: how I want answers (short or detailed), what I'm still learning, and the rules I want everywhere. Include these: show me the plan before changing more than one file; say plainly what you did not check; never buy, subscribe or sign up for anything. Show me the file before you save it.
- Paste it into Claude Code with Cmd+VCtrl+V and press Enter.
- Answer the questions one at a time.
- Read the before Claude saves it.
You should see:
Claude asks you one question about how you like to work, and waits for your answer.
That's not what I see
- I'm not sure what goes here versus the project's CLAUDE.md.
- Rules about you go in the personal one, like how you want answers. Rules about one project go in that project's CLAUDE.md, like "don't change the colors."
See what Claude remembers, and change it
Auto memory is notes Claude saves for itself as you work: your preferences, your corrections. Say "remember that…" and it writes it down.
-
Type this and press Enter:
/memory -
Press the down arrow to Open auto-memory folder and press Enter.
-
Open a note and read it. If your Mac asks which app, choose TextEdit.If Windows asks which app, choose Notepad. It's plain text, and you can change or delete any of it.
-
Back in Terminal, press Esc if the list is still open.
You should see:
A Memory list with Auto-memory at the top, then User instructions, Project instructions and Open auto-memory folder.
That's not what I see
- The auto memory folder is empty.
- Claude only saves notes when there's something worth keeping. Tell it something, like: Remember that I always want prices checked on the company's own website. Then open /memory again.
- Claude remembered something wrong.
- Tell it what to forget, like: Forget that I use Outlook. That's not true. Or open the auto memory folder from /memory and delete or edit the note yourself. They're plain text files.
-
Turn a job you repeat into a skill
Skills are saved instructions for one kind of job. Like a recipe card in the kitchen drawer: you write it once, and every time that dish comes up, Claude follows the same steps.
A prompt is something you paste in. A skill is something Claude finds and uses on its own when the job matches its description, or when you type its name. Good first skills are jobs you've already done with Claude three or more times, the same way each time.
This prompt asks Claude to interview you about the job and write the skill. The job goes at the end.
- Copy the prompt below.
Help me write a personal skill for a job I do over and over. I describe the job at the end. Save it at ~/.claude/skills/ in a folder with a short name you suggest, in a file called SKILL.md. Start with a description that says exactly when to use it, because that's how you'll decide. Then the steps you'd give a smart helper doing it for the first time, how to check the result, and a Never list. Interview me one question at a time for anything you'd be guessing. Show me the skill before you save it. The job:
- Paste it into Claude Code with Cmd+VCtrl+V.
- Type a space, then the job, like turn my notes from a call into a short list of what I promised to do.
- Press Enter, and answer the questions.
The description matters most. Claude reads only the descriptions of your skills until a job matches one, so say exactly when to use it.
You should see:
Claude asks you one question about the job, and waits. At the end, it shows you the skill before it saves it.
That's not what I see
- I don't have a job I've done three times yet.
- Then skip this step and come back. A skill written from a job you've only done once is a guess.
Run your skill by name
-
Leave Claude Code. Type this and press Enter:
/exit -
Start it again. Type this and press Enter:
claude -
Type / and the skill's short name, and press Enter. Claude follows your recipe card.
Rules I follow for skills: write them only for jobs you've done by hand, keep them few, and add a line to the Never list every time a run goes wrong. A skill makes Claude consistent, not correct. You still check.
You should see:
As you type the / and the first letters, a list opens under the line where you type, with your skill's name and the start of its description.
That's not what I see
- The slash command doesn't show up.
- Type , then start claude again. Check the skill's folder is inside ~/.claude/skills~\.claude\skills, and that the file is called SKILL.md exactly, in capitals./exit Typed in Claude Code, it ends the conversation and takes you back to Terminal. All words
-
Your challenge
Pick one job you've done with Claude three times the same way. Turn it into a skill, then run it with its slash command next time instead of explaining it again.
Last checked 2026-10-20
Connect and automate › 2. Teach it and schedule it
Teaching Claude your setup: memory and skills
One-page card · print it or keep it open
What you'll do
Every time you explain the same thing to Claude twice, that's something to teach it once. There are three ways, from simplest to most powerful: CLAUDE.md files, auto memory and skills.
The steps
- Start Claude Code in your my-idea folder
- Write the rules you want in every project
Create or update my personal CLAUDE.md at ~/.claude/CLAUDE.md, which you read in every project. Interview me, one question at a time, about how I like to work: how I want answers (short or detailed), what I'm still learning, and the rules I want everywhere. Include these: show me the plan before changing more than one file; say plainly what you did not check; never buy, subscribe or sign up for anything. Show me the file before you save it.
- See what Claude remembers, and change it
- Turn a job you repeat into a skill
Help me write a personal skill for a job I do over and over. I describe the job at the end. Save it at ~/.claude/skills/ in a folder with a short name you suggest, in a file called SKILL.md. Start with a description that says exactly when to use it, because that's how you'll decide. Then the steps you'd give a smart helper doing it for the first time, how to check the result, and a Never list. Interview me one question at a time for anything you'd be guessing. Show me the skill before you save it. The job:
- Run your skill by name
If it goes wrong
- It says "cd: no such file or directoryCannot find path … because it does not exist". The my-idea folder isn't there. It comes from Check the idea first and The three files, so do those first, then come back.
- I'm not sure what goes here versus the project's CLAUDE.md. Rules about you go in the personal one, like how you want answers. Rules about one project go in that project's CLAUDE.md, like "don't change the colors."
- The auto memory folder is empty. Claude only saves notes when there's something worth keeping. Tell it something, like: Remember that I always want prices checked on the company's own website. Then open /memory again.
- I don't have a job I've done three times yet. Then skip this step and come back. A skill written from a job you've only done once is a guess.
Words
- auto memory: Notes Claude Code saves for itself about you and your project, so it remembers them next time.
- skill: A saved set of instructions for one kind of job. Claude uses it when the job comes up, or when you type its name.
- slash command: Something you type in Claude Code starting with a slash, like /memory or /exit.