27 Sep 2026 · 7 min readSlash Commands

What Are Slash Commands, and Why Do They Work So Well?

A slash command is just a saved prompt with a name. That sounds trivial, and the reason it works is exactly that it is trivial — it removes the blank page, which is where most prompting effort is actually lost. This guide explains why naming and storing prompts beats retyping them, what makes a command worth saving, and how a personal library compounds over a few months.

The idea, stripped down

You write a prompt that works. A week later you need it again and you cannot remember how you phrased it, so you rebuild it from scratch and get a worse result. A slash command is that prompt, saved under a stable name you can recall. That is the whole mechanism — and it works because the expensive part of using AI is not typing, it is deciding what to type.

You stop rewriting the same structure. The scaffolding is already written.
Results become consistent, because the input is consistent.
You can improve a command once and every future use benefits.
You can share it, so a teammate gets your version rather than approximating it.

What is worth saving

Anything you have typed more than twice. That is the whole threshold.
Anything that took several attempts to get right — the working version is the valuable artefact, not the idea.
Anything with a fixed structure: a report format, a review checklist, a meeting template.
Anything you explain to other people repeatedly.

⚠️ Note: Do not save one-off questions. A library of thousands of near-identical entries is worse than a library of ten, because searching it costs more than it saves.

What makes a good command

Named after the job, not the tool. 'Weekly report' rather than 'prompt 14'.
Starts with the role and goal, so it works without extra framing.
Has explicit placeholders for the parts that change, so you fill rather than rewrite.
States length and format, because 'summarise' alone is where vague output comes from.
Includes what to avoid, which is often more effective than what to do.

command shape

/Weekly report

You are writing a status report for a manager who was not
in the meetings.

Input: <paste your rough notes>
Include: what shipped, what is blocked, what needs a decision
Constraints: under 200 words, no jargon, plain sentences
Avoid: padding, restating the org chart, vague future plans

Why a library compounds

The value of a command library is not linear. The first ten save a little time. The next fifty save the thinking as well as the typing, because you are choosing from a decision rather than inventing one. And because the commands get better as you refine them, the library quietly becomes a record of how you like work done — which is a genuinely valuable artefact.

A paste bin and a scratch notepad are enough to run a whole command workflow in the browser, with no account and nothing sent anywhere.

Smart Paste Bin freeDetect text type and extract insights Quick Notes freeDistraction-free notepad with autosave OneLiner Quotes free500+ aesthetic quotes. Copy or download as PNG.Quote Card Maker freeDesign quote cards with fonts, backgrounds & templates Markdown Editor freeSplit pane with live preview + toolbar

All of these run in your browser — no account, no upload, free forever.

Get started with real ones

These are the most-copied patterns in the SlashAI library — copy one, replace the placeholders, and save it as your own.

/Summarize

Summarize Anything

Compress any text into a faithful summary at the length and reading level you choose.