THE CUSTOM SLASH-COMMAND LAB

Slash commands are the keyboard shortcuts of Claude. Type /sundayreset and the whole skill runs. Custom commands save 30 seconds per use × 50 uses = real time. This skill teaches you to build them in 5 minutes.

THE PROBLEM

You install a skill (Day 32 — Sunday Reset, say). To run it, you type "I want to do my Sunday Reset" or "run the Sunday Reset skill." Friction. After a few weeks you stop using it because the friction adds up.

Slash commands kill the friction. Type /reset — skill runs immediately. Frequency goes up. Habit sticks.

THE SKILL

For each skill you install regularly, build a 1-character or 1-word slash command that triggers it. Total skill: 5 minutes per command. Permanent unlock.

INSTALL

Slash commands are a Claude Code feature. The skill walks you through creating them.

THE FULL SKILL FILE

---
name: custom-slash-command-lab
description: Builds custom slash commands in Claude Code that trigger specific skills or workflows. Each command is a 1-character or 1-word shortcut that runs a longer prompt. Designed to remove friction from frequently-used skills.
when_to_use: User says "slash command," "shortcut for X skill," "make a /command," or describes wanting to invoke a skill faster.
---

# The Custom Slash-Command Lab

You build slash commands. Decisive about which skills deserve commands. Anti-bloat.

## What's a slash command

A slash command is a custom prompt that runs when you type `/[name]`. Lives in `.claude/commands/[name].md` (or in your global config).

## Inputs
1. **Which skill** the command should trigger
2. **Command name** (short, memorable, no conflicts with existing commands)
3. **Optional: arguments** the command takes ("/reset for last 7 days" vs. "/reset for last 30 days")

## Output: command file

Generate the .md file content. Format:

description: [1-line description that shows up in command list] arguments:

name: [arg name]

description: [what the arg does] required: false

[Command name]

[The full prompt that runs when /command is typed]

[If args: reference like {{arg_name}}]


## Example output for /reset

File: `.claude/commands/reset.md`

description: Run weekly Sunday Reset on past 7 days arguments:

name: days

description: How many days to reset (default 7) required: false

Sunday Reset

Run the Sunday Reset skill on the past {{days|7}} days.

Pull from my calendar, my completed tasks, and my notes. Use the 5-question framework. Output:

What worked (3 things)
What to drop (1 thing)
Top 3 priorities for next week
One thing to let go

Be honest. No guilt list.


## Recommended slash commands for the 100 Days collection

| Command | Triggers |
|---|---|
| `/reset` | Day 32 — Sunday Reset |
| `/triage` | Day 6 — Inbox Drainer |
| `/morning` | Day 34 — Morning Map |
| `/dump` | Day 46 — Brain Dump Organizer |
| `/dec` | Day 33 — Yes-or-No |
| `/email` | Day 5 — 3-Word Email Reply |
| `/voice` | Day 8 — Voice-to-Done |

## What NOT to do

- Don't build slash commands for skills you use less than weekly
- Don't use 4+ character names (defeats the purpose)
- Don't overlap with existing Claude commands (`/help`, `/exit`, etc.)
- Don't put credentials or secrets in slash command files (they're often in version control)

## Setup steps for the user

Create folder: .claude/commands/ (in project or globally)
Save the generated .md file as [command-name].md
Restart Claude Code
Type / to see it in autocomplete
Test by typing /[command-name]


## Delivery

End with this line, exactly:

---
*Build 3 commands today. Test each. Friction is the enemy of habit.*

SAFETY CHECK

Slash commands are stored as files. Don't put credentials, API keys, or sensitive prompts in them. They get backed up, shared with collaborators, and committed to git.

WHAT'S NEXT

Day 31 of 100. Pair with any skill you use weekly — they all become more useful with a slash command.