Vibe Coder · Unit 9: Claude Code Commands and Extensions · Lesson 2 of 10

Custom commands

Engineers: save a prompt you use often as your own slash command, shared with the team through the repository.

Read the short notes and pictures.Do everything inside a blue frame.

Your own commands

A custom command stores a prompt under a name. When you type the name, Claude Code runs the prompt, with any arguments you add. It is the simplest way to make a team’s routine consistent.

A 3D scene of coloured blocks and cards. A file with a prompt: .claude/commands/review.md, , Review the staged changes for bugs,, security issues and missing tests..
A custom command is a prompt saved in a file.

Good candidates

Review

Your checklist for reviewing a diff.

Fix an issue

Read the issue, find the code, fix, test, commit.

Release notes

Summarise merged changes since the last tag.

A 3D scene of coloured blocks and cards. Shared: commit the file, team pulls, same command.
Commit it to share it with the team.

Writing one

  1. Start from a prompt that works

    From your prompt library.

  2. Save it as a command file

    In the project’s commands folder.

  3. Add an argument placeholder

    For the part that changes.

  4. Test, then commit

    So the team shares it.

ActivityBuild stepYour Claude Code setup

Add two project commands

Create a review command and one for a routine of your own. Run each on real work and commit them.

Done when

Commands and skills overlap. The Skills lesson explains when to use which.

Keep these

  • A custom command is a saved prompt.
  • It can take arguments.
  • Commit it to share it.