Shorthand

Shorthand

**Teach Claude your shorthand.**

Shorthand scans your Claude Code commands and skills, mines your session history, and builds a natural language routing layer — so you stop typing slash commands and start talking.

Instead of remembering that `/create-invoice` is the command you need, just say "invoice Acme for $450 for March consulting." Shorthand figures out which command to run.

More examples:

• "check my email" routes to your work inbox, not your personal one
• "schedule a client call for Thursday" puts it on your business calendar, not your personal one
• "prep for my 2pm with Sarah" pulls context from the right CRM, project notes, and past conversations
• "remind me to follow up with John on Tuesday" creates the reminder in your preferred system
• "what's on my plate today" shows priorities from the tools you actually use

The routing isn't generic — it's *yours*. Your commands already know which inbox, which calendar, which tools. Shorthand just lets you reach them by talking naturally.

Why Not Just Talk to Claude?

Claude already does this natively — it can often figure out that "check my email" means you want `/email-overview`.

But it's not always consistent. Sometimes it catches the intent, sometimes it doesn't, and sometimes it routes to the wrong command.

Shorthand trades a small amount of token efficiency for reliable, repeatable routing. If consistency matters more to you than saving ~5,000 tokens per session, this is for you.

How It Works

Shorthand adds two things to your Claude Code project:

1. A routing snippet in your CLAUDE.md that tells Claude to check intent mappings before processing each message
2. A JSON file (intent-mappings.json) that maps natural language triggers to your existing commands and skills

When you type "check my email," Claude matches it against your mappings and invokes `/email-overview`. When you say "prep for my 2pm with Sarah," it runs `/prep-meeting` with the righ