Namespace Your Skills with a Prefix to Stay Organised
Once you have more than a handful of skills, they start blending into the built-ins. A simple naming convention fixes that instantly.
Instead of creating skills called /review, /deploy, and /summarise alongside all your built-in commands, prefix them consistently:
# Flat chaos:
/review
/deploy
/summarise
# Namespaced and scannable:
/my-review
/my-deploy
/my-summarise
# Or group by domain:
/work-review
/work-deploy
/personal-journal
Claude Code's slash commands live in a flat list. When you're juggling project skills, personal shortcuts, and shared team commands, they all pile up together. A prefix like /my- means you can type those three characters and immediately see only your custom skills, without scrolling past built-ins or wondering which /review is which.
This pays off even more if you share a project with teammates who have their own skills loaded. Prefixing by owner or domain makes it obvious at a glance whose command you're invoking.
Pick one convention and stick to it. /my-, your initials, or a project short-code all work well.
Two characters at the front saves minutes of hunting through a crowded slash menu.
via @vinicavin
Log in to leave a comment.
Turn your most common prompts into reusable slash commands — drop a markdown file into .claude/commands/ and it becomes a /command you and your team can invoke anytime, with consistent instructions every time.
Create reusable slash commands in your project so common prompts like "run tests and fix failures" or "review this file for security issues" become a single /command instead of typing the same instructions every time.
The $ARGUMENTS placeholder in custom slash command files turns a static prompt into a reusable tool — pass different values each time you invoke it, just like a function that takes arguments.