Skip to main content

Una Commands

Una Commands are reusable prompts you can invoke inside an AI chat session with a single slash command. A command is a Markdown file that bundles a name, a description, and a detailed prompt template into one place. When you invoke a command, its prompt is automatically loaded into the conversation — complete with any arguments you passed in.

This guide covers how to use commands and how to write your own.


Invoking a Command

Type the command name as a slash command, followed by your request:

/command-name your request here

Examples:

/generate-one-file-html-page A dark-themed portfolio page with a hero, projects grid, and contact form
/summarize-meeting Paste your meeting transcript here
/write-release-notes Version 2.4.1 — fixed login bug, added export to Excel

Inside the command's prompt template, the text that follows the command name is available as $ARGUMENTS. The AI fills in $ARGUMENTS with exactly what you typed.


Command File Structure

Every command is a single Markdown file stored under /Local AI/Commands/:

/Local AI/Commands/
generate-one-file-html-page.md
summarize-meeting.md
write-release-notes.md
...

One file = one command. No subfolders required.


The Command File Format

A command file has two parts: a frontmatter block at the top, and the prompt body below it.

---
name: My Command
description: One or two sentences explaining what this command does and when to invoke it.
---

You are an expert in X. The user has asked you to...

$ARGUMENTS

(rest of instructions)

Frontmatter Fields

FieldRequiredDescription
nameYesDisplay name of the command.
descriptionYesOne or two sentences. Explains what the command does and when it should be triggered.

The $ARGUMENTS Placeholder

Place $ARGUMENTS anywhere inside the prompt body where you want the user's input to appear. When you invoke the command, the AI replaces $ARGUMENTS with the text you typed after the command name.

If you invoke the command with no arguments (just /command-name with nothing after it), $ARGUMENTS is an empty string. Well-written commands handle this gracefully — either by generating sensible defaults or by asking the user for the missing information.


How Commands Differ from Skills

CommandsSkills
PurposeReusable prompt templatesReusable AI behaviors with deep instructions
Stored in/Local AI/Commands//Local AI/Skills/
File structureSingle .md fileFolder with skill.md + optional extra files
Supports extra filesNoYes (loaded on demand)
Best forParameterized one-shot promptsComplex, multi-step tasks with supporting context

Use a command when the task is straightforward and can be fully described in a single prompt with one variable input.
Use a skill when the task is complex, requires multiple reference files, or the AI needs deep domain context beyond what fits in one prompt.


Best Practices

Writing the Prompt Body

Be explicit about the output format. Tell the AI exactly what to produce: a JSON object, a Markdown document, a code file, a numbered list. Don't leave the format ambiguous.

Handle the empty-arguments case. Decide what happens when the user provides no input. Either generate a sensible default, or include a clear instruction like: "If $ARGUMENTS is empty, ask the user what they would like to create."

State constraints up front. List hard rules the AI must follow (e.g. "Do not include any external dependencies", "Output only the file content with no surrounding explanation"). Put these before the instructions, not after.

Include at least one worked example. A full input → output example in the prompt dramatically improves consistency. For commands that generate code or structured data, a complete realistic example is far more useful than a skeleton.

Keep the prompt focused. A command does one thing. If you find yourself writing branching logic for very different use cases, split it into two commands.

Naming the Command

  • Use lowercase kebab-case: generate-one-file-html-page, summarize-meeting, write-release-notes
  • The filename (without .md) is the command name users type
  • Keep it short and descriptive — users type it frequently

Example: generate-one-file-html-page

This command generates a complete, self-contained HTML page from a short description.

How to invoke:

/generate-one-file-html-page A clean portfolio landing page for a product designer: dark theme, hero, projects grid, contact form

What it does: Produces a single valid HTML5 file with all CSS and JavaScript inline, semantic markup, responsive layout, and placeholder content — ready to open in a browser and edit.

Download the full command file and drop it into /Local AI/Commands/ to start using it immediately.


Checklist Before Publishing a Command

  • Frontmatter has name and description
  • Description is precise enough that the AI knows when to suggest it
  • $ARGUMENTS is placed where the user's input should go
  • The empty-arguments case is handled
  • Output format is explicitly stated
  • At least one worked example is included in the prompt
  • Filename uses lowercase kebab-case