Skip to content
Recaply.
Sign inSubmit a tool

LearnTutorials

Claude CodeTutorialsOpen Claude Code

Set up Claude Code as your daily coding partner

Set up Claude Code in 20 minutes with a short CLAUDE.md, private notes, a reusable skill, shared MCP servers and plan mode for bigger changes.

By Recaply EditorsIntermediate20 min5 stepsUpdated

A hand types on an open laptop next to a mug holding a small plant

What you need

  1. Step 1: Write a short CLAUDE.md

    5 min

    Claude reads this file at the start of every session, so it should hold only what the code can't tell it.

    1. In your project, run claude, then type /init to draft the file.
    2. For each line, ask whether Claude would get something wrong without it. If not, cut it.
    3. Keep exact commands, misleading spots in the code and team decisions.
    Your CLAUDE.md
    # Commands
- Test one file: [TEST COMMAND] [PATH TO FILE]
- Typecheck: [TYPECHECK COMMAND]

# Gotchas
- [OLD FOLDER] is still live, but don't copy its patterns.
- Integration tests need [VARIABLE NAME] set. See .env.example.

    You should see your file listed under Memory files when you run /context all.

    Claude keeps ignoring a line?

    Make the file shorter so the line stands out. Writing IMPORTANT won't help. A rule that can never bend belongs in a hook or a deny rule.

    The file can live at ./CLAUDE.md or ./.claude/CLAUDE.md. Anthropic suggests keeping it under 200 lines.

  2. Step 2: Keep personal notes in CLAUDE.local.md

    2 min

    Your own preferences load in every session here, but stay out of the shared repo.

    1. Create CLAUDE.local.md at the project root.
    2. Add your sandbox URLs, test data and personal habits.
    3. Run the command below to keep the file out of git.
    Run this
    echo "CLAUDE.local.md" >> .gitignore

    You should see no CLAUDE.local.md in git status, and the file under Memory files in /context all.

    Your notes are missing in another worktree?

    An ignored file exists only in the worktree where you made it. Import a file from your home folder instead, with a line like @~/.claude/my-project-notes.md.

    Never put API keys or passwords in either file. Claude reads both into its context.

  3. Step 3: Turn a repeated task into a skill

    5 min

    A skill holds a procedure Claude reads only when the task needs it, so it doesn't weigh on every session.

    1. Create the folder .claude/skills/pr-summary/ in your project.
    2. Save the text below in it as SKILL.md.
    3. Type /pr-summary in a session to run it. Claude can also pick it up when you ask for a PR description.
    Your SKILL.md
    ---
name: pr-summary
description: Write a pull request title and description for the current branch. Use when asked for a PR summary or description.
---
1. Run `git diff main...HEAD` and read the changes.
2. Write a title of 60 characters or fewer.
3. List what changed and why in 3 to 5 bullets.
4. Add a "How to test" section with exact commands.

    You should see /pr-summary in the menu when you type /, and a ready PR description after it runs.

    /pr-summary doesn't show up?

    Check that the file is named SKILL.md and that --- is its first line. Run claude plugin validate .claude/skills to find a broken header.

    For a skill with side effects, such as a deploy, add disable-model-invocation: true. Then it runs only when you type it.

  4. Step 4: Share MCP servers with your team

    3 min

    Servers listed in .mcp.json reach every teammate who clones the repo.

    1. Run claude mcp list to see the servers you have now.
    2. Add a team server with --scope project, as below. Claude Code writes it to .mcp.json at the project root.
    3. Commit .mcp.json. Each teammate approves it once, the first time they run claude there.
    Run this
    claude mcp add --transport http notion --scope project https://mcp.notion.com/mcp

    You should see the new server in claude mcp list, with a status next to its name.

    The server says it's pending approval?

    Project servers need your OK once. Run claude in the project and approve the server when asked.

    Keep tokens out of .mcp.json. Write ${API_KEY} in the file and set the real value as an environment variable.

  5. Step 5: Plan before bigger changes

    5 min

    In plan mode, Claude reads the code and writes a plan, but edits nothing until you approve.

    1. Start your prompt with /plan, as below. Or press Shift+Tab until the status bar shows plan mode.
    2. Read the plan. Press Ctrl+G to open it in your editor and change it.
    3. Pick an approve option, such as Yes, manually approve edits, to let Claude start.
    Your prompt
    /plan Add [FEATURE] to [PART OF THE APP]. Read the code it touches first. List the files you'd change and why, and name the tests that will prove it works.

    You should see a written plan of files and steps, and no changes to your code yet.

    Shift+Tab skipped past plan mode?

    New sessions start in auto mode. From there the order is manual, accept edits, then plan, so it takes 3 presses.

You get

Claude Code set up with your project's rules, your private notes, a reusable skill, shared tools and a plan-first habit

Try next

Install agent skills in Claude Code6 steps · 5 minInstall an agent skill in any AI coding agent6 steps · 5 minControl Claude Code with hooks and skill settings5 steps · 24 min

Did this guide work for you?

Sources

0 of 5Next: Write a short CLAUDE.md