// 8 tips tagged "skills"
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.
Drop a Markdown file into .claude/commands/ and it becomes a slash command — no config, no code, just a prompt in a file that your whole team can share.
Add a consistent prefix like /my- to all your custom skills so they stay grouped and scannable in the slash command list.
Pair a UserPromptSubmit hook with a skill-rules.json config to reliably trigger the right skill on every prompt instead of relying on Claude's 50/50 automatic detection.
CLAUDE.md loads into every message. Move workflow-specific instructions into skills that load on demand to reduce token costs across your session.
Turn repetitive instructions into reusable skills that persist across sessions and keep Claude consistent without manual reminders.