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

10 min / beginner / 5 steps

Create Your First Skill in 10 Minutes

Turn a task you do every week into a single command. Copy, paste, done.

Skills are markdown files that teach Claude how to do specific tasks. Instead of typing the same instructions over and over, you write them once and Claude follows them every time. Think of it like creating a custom command. Let's make a code review skill.

follow along in

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

  1. step 01 / 05

    Create the skills directory

    Skills live inside the .claude/skills folder in your project. Each skill gets its own folder, named after the skill, with a SKILL.md file inside. Create the folder for your first one.

    Prompt
    I want to create a reusable code review skill for Claude. How do I set this up in the app?

    what you should see

  2. step 02 / 05

    Create a code review skill

    Create a markdown file that tells Claude exactly how to review code. This is where the magic happens. You define the rules, the format, the tone, everything.

    Prompt
    Here are the instructions I want you to follow every time I ask for a code review: Check for: security vulnerabilities, performance issues, missing error handling, unclear naming. Rate each issue: CRITICAL, HIGH, MEDIUM, or LOW. Format: file path, line number, severity, issue, fix suggestion. Be direct. If the code is good, say so briefly.

    what you should see

  3. step 03 / 05

    Test it with a real review

    Now use the skill. Ask Claude to review your recent changes and watch it follow your exact format.

    Prompt
    Review this code: const API_KEY = "sk-live-abc123"; async function getUsers() { const users = await db.query("SELECT * FROM users"); return users.map(u => db.query(`SELECT * FROM orders WHERE user_id = ${u.id}`)); }

    what you should see

  4. step 04 / 05

    See the skill activate

    Notice how Claude followed your exact format, with severity ratings, file paths, and specific fixes. That's not coincidence. That's your skill definition driving the output.

    Prompt
    Why is the output so much better when I give you those instructions upfront?

    what you should see

  5. step 05 / 05

    Customize it for your team

    Now make it yours. Add your team's specific rules, coding standards, or things that always get missed in reviews. The skill grows with you.

    Prompt
    Add these rules to my code review instructions: - All API routes must have rate limiting - Database queries must use the repository pattern - React components must have error boundaries - No inline styles, Tailwind classes only - All public functions need JSDoc
    markdown
    # Add these to your code-review.md:

## Team-Specific Rules
- All API routes must have rate limiting
- Database queries must use the repository pattern
- React components must have error boundaries
- No inline styles, use Tailwind classes only
- All public functions need JSDoc comments

    what you should see

go deeperDeep dive into skills and custom commands

Tell someone what you built

Just finished "Create Your First Skill in 10 Minutes" on Claude Code Guide. Took about 10 min, and it's free: https://claudecodeguide.dev/tutorials/your-first-skill

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