# Slash Command (/academy/slash-command)



A slash command is a labeled button that pastes a whole paragraph.

You type `/review` or `/hackhaton-space-stack:new` and the host expands that into the instructions you were tired of retyping. It is not magic. It is a saved prompt with a short name — the same move as a [CLI](/academy/cli) flag, except the "flag" is a sentence.

The file *is* the command. `new.md` becomes `/new`. The body is the ritual. Optional frontmatter is just a label for the menu.

**You choose. The skill notices.**

A [skill](/academy/skill) is a document the model can pick when the job matches. A slash command is you picking. Use commands for rituals you run on purpose. Use skills for jobs the [agent](/academy/agent) should notice on its own.

This plugin ships two on purpose: `/hackhaton-space-stack:new` and `/hackhaton-space-stack:add`. They do not invent a [stack](/academy/stack). They point the agent at [MCP](/academy/mcp) — plan, then create — the same path as `npx create-hackhaton-space-stack@latest mcp`. Codex has no slash menu; the skills cover the same workflows there.

Anything you typed twice is a candidate. Handoff notes. "Commit this." "Add PWA." Name it. Slash it.

Do not confuse the button with the [system prompt](/academy/system-prompt). Standing orders are always on. A command is a doorbell you press.

**What this unlocks**

Once the ritual has a name, you stop losing the prompt in a snippets app. You fire the same paragraph every time, with `$ARGUMENTS` dropped in, and the agent shows up already mid-job.

A pasted blob is a habit. A slash is infrastructure.
