Commands: your entry points
Give a repeated request or app action a name you can invoke.
A prompt shortcut asks the agent for work
A command can hold instructions behind a slash name. A standup command, for example, asks the agent to read recent commits and write a status note. Its purpose is to save the user from retyping that request.
An action operates the app or runs code
Commands can also change the model, select a theme, or invoke code registered by a plugin. The slash syntax is an entry point, not a promise that every command runs through the model.
A command is not the same as a skill
“Review this demo” is a user request. Extracting timestamped screenshots is a reusable capability the agent may choose while fulfilling it. The command starts the work; the skill is part of the agent’s method. Markdown versus code does not determine which it is.
Share the shortcuts your team uses
Package a standup command with your team’s instructions for its format. Installing the content bundle makes that same command available without copying the prompt into each conversation. A Lua plugin can provide a command when the action needs code rather than model reasoning.