The one-line version of each
- Prompt. What you type in the moment. A single message.
- Instruction. A standing rule for how AI should behave across every chat.
- Skill. A packaged workflow AI runs automatically when it sees a matching task.
- Command. A shortcut you type with "/" to manually trigger a workflow.
The side-by-side
| Prompt | Instruction | Skill | Command | |
|---|---|---|---|---|
| What it is | A message you type | A rule that always applies | A packaged workflow | A manual shortcut |
| When it runs | Every time you hit send | Every chat, in the background | Whenever AI sees a matching task | Only when you type "/" |
| How specific | To this exact request | To you, broadly | To one type of task | To one type of task |
| Setup effort | None | 5 to 10 minutes once | 30 minutes to a few hours | 5 to 30 minutes |
| Best for | One-off tasks | Voice, tone, defaults | Repeated workflows | Explicit, named actions |
Think of it like running a real business
Imagine you just hired an assistant.
- The prompt is you walking up and asking "hey, can you draft an email to ClientA about the contract delay?"
- The instruction is the one-page note you handed them on day one. "Always use plain English. Be direct. Don't include disclaimers. Ask before you send anything."
- The skill is the SOP you wrote together. "Here is exactly how we handle new client intakes, step by step."
- The command is the post-it on the desk. "When I tap on this, run the weekly status report."
The right order to build them
Most people get this wrong. They jump straight to commands or skills. Do it in this order:
- Get comfortable writing prompts first. Spend a week using AI. Notice what works and what doesn't.
- Set your instructions next. Write down the rules you keep repeating. Move them out of your prompts and into your custom instructions.
- Build skills for what you repeat. If a workflow happens more than once a week, package it as a skill.
- Add commands only when you want a named shortcut. Usually you don't even need them once skills are good.
Where most small businesses end up
Solid global instructions + 5 to 10 skills for their most repeated workflows + casual prompts for everything else. That setup beats 90% of what people build.
Common mix-ups
- "I keep retyping the same context in every prompt." That's a sign you need an instruction or a skill, not a longer prompt.
- "My skill never triggers." The skill's description is too vague. Rewrite it with specific trigger words people actually use.
- "My instructions are 1,000 words and AI ignores half of them." Too much, conflicting, or buried. Cut to 100-200 words of clear rules.
- "I built 20 commands and can't remember any of them." Convert them to skills so they auto-trigger. You're not supposed to memorize a command list.
The advanced take: layering all four
A real production setup uses all four together.
- System prompt (set by the platform). You don't touch this.
- Custom instructions (your standing rules). Tone, defaults, voice.
- Project-level instructions (per client or matter). Domain-specific background.
- Skills (packaged workflows). Auto-trigger for known tasks.
- Commands (manual shortcuts). For moments you want explicit control.
- Prompt (the message you type today). The actual request.
All six layers stack together. The AI reads them top to bottom before it answers. Good setups make every layer pull its weight so your day-to-day prompts can stay short.