Claude Code Guide
বাংলায় পড়ুন

5 min / beginner / 5 steps

Build Your First CLAUDE.md in 5 Minutes

The single most important thing you can do with Claude Code. Create the file that turns it from generic to personalized.

A CLAUDE.md file is like a briefing doc for Claude. It tells Claude who you are, what your project is, and how you like to work. Without it, Claude starts every conversation from scratch. With it, Claude already knows the deal. Let's build one.

follow along in

You need: A Claude account. Open claude.ai in a browser, or the Claude desktop app.

  1. step 01 / 05

    Get to your starting point

    Pick any project you're working on, a side project, a work repo, anything. We just need to get Claude looking at the right place.

    Prompt
    I want to set up a CLAUDE.md file for my project. It's a Next.js app with TypeScript. Where do I start?

    what you should see

  2. step 02 / 05

    Generate your CLAUDE.md

    In the terminal, one command does it all. In the app or IDE, you describe your project and Claude writes it for you.

    Prompt
    My project is a Next.js SaaS app with TypeScript and Tailwind. We use Prisma for the DB, vitest for tests, and prefer functional components. Never use `any` types.

    what you should see

  3. step 03 / 05

    Open the generated CLAUDE.md

    Take a look at what Claude created. It should have your project name, the tech stack it detected, build commands, and some basic context. This is your starting point.

    bash
    cat CLAUDE.md

    what you should see

  4. step 04 / 05

    Add your communication preferences

    This is what separates a good CLAUDE.md from a great one. Tell Claude how you like to work. Are you a senior dev who wants terse answers? A beginner who wants explanations? Add a section for it.

    Prompt
    Add this to the CLAUDE.md you just wrote: Be concise. Give code first, explanation second. Use TypeScript always. When fixing bugs, show root cause before fix. Don't ask. Just do it.
    markdown
    # Add this to the bottom of your CLAUDE.md

## Communication Preferences
- Be concise. Skip the preamble.
- When I ask for code, give me the code first, explanation second.
- Use TypeScript. Never suggest JavaScript alternatives.
- When fixing bugs, show me the root cause before the fix.
- Don't ask "would you like me to...". Just do it.

    what you should see

  5. step 05 / 05

    Test it and see the difference

    Now start Claude Code and give it a prompt. Notice how it already knows your stack, your build commands, and your preferences. No more explaining yourself.

    Prompt
    Add a dark mode toggle to the header. My stack is Next.js 16, Tailwind, TypeScript.

    what you should see

go deeperRead the full CLAUDE.md guide

Tell someone what you built

Just finished "Build Your First CLAUDE.md in 5 Minutes" on Claude Code Guide. Took about 5 min, and it's free: https://claudecodeguide.dev/tutorials/your-first-claude-md

Share on LinkedIn

New guides, when they ship

One email, roughly weekly. CLAUDE.md templates, workflows I actually use, and the cut-for-length stuff that does not make the public guides. One-click unsubscribe.

Or read Product Field Notes, the Substack