AI Prompt Commands & Parameters
903 commands & parameters · 23 AI tools · official sources only
AI tools are increasingly driven by what you type, not what you click: slash commands steer coding agents, @ mentions attach context, and generation parameters shape images and video. This section is a structured reference for that typed layer - the commands, parameters, and prompt syntax of AI tools - built the same way as our keyboard shortcuts reference: every entry is a literal token taken from official documentation, with a description and a usage note, and every table links its source.
This is deliberately not a prompt gallery. There are no prompt templates or example prompts here; those age fast and are easy to find elsewhere. What is hard to find is a maintained, machine-readable list of what a tool actually accepts: which slash commands exist in Claude Code today, what every Midjourney parameter does, or how A1111 attention weighting is spelled. That is what these pages hold, and the same data is available as JSON through our public API.
Keyboard shortcuts for these tools remain in the Shortcuts section - the two references are linked both ways, so a platform page in one section points to its counterpart in the other.
Platforms
OpenAI-Compatible Endpoints
Tools in this reference that serve or accept the OpenAI API shape - point an OpenAI SDK at them by swapping the base URL. Details and every parameter are on each platform page.
| Platform | What is compatible | Documented tokens on our page |
|---|---|---|
| DeepSeek | Chat completions; beta base URL adds prefix and FIM completion | prefix, suffix, deepseek-reasoner, response_format |
| Qwen (Alibaba Model Studio) | OpenAI-compatible chat endpoint that also accepts DeepSeek, Kimi, GLM and MiniMax model names | enable_thinking, thinking_budget, search_options (extra_body) |
| LM Studio | Local server exposing /v1/chat/completions, /v1/completions, /v1/embeddings, /v1/responses, /v1/models | lms server start, temperature, maxTokens, structured |
| Nous Hermes | Hermes 4 served locally speaks the standard chat shape; tool calls use Hermes tag protocol | thinking=True, <tool_call>, <tools> |
One-page views: the AI prompt commands cheat sheet shows the first fifteen entries of every platform on a single static page, and the comparisons Claude Code vs Cursor and Claude Code vs Codex CLI pair the same task across tools.
Compact References
Smaller command sets live directly on this page.
Suno AI · Source: Suno Help Center
Prompt Metatags (6)
| Command / Syntax | What it does | Notes |
|---|---|---|
| [Verse] | Verse section | Specify a verse section in the song. |
| [Chorus] | Chorus section | Specify a chorus section. |
| [Bridge] | Bridge section | Specify a bridge section. |
| [Outro] | Outro | Specify the outro section. |
| Genre tags | Set genre | Tag genres like pop, rock, jazz, hip-hop. |
| BPM | Set tempo | Specify the song BPM (tempo). |
Agent Instruction Files · Source: AGENTS.md - Official spec
Cross-Tool Standard (2)
| Command / Syntax | What it does | Notes |
|---|---|---|
| AGENTS.md | Open cross-tool instruction file: a README for agents | Read by Codex, Cursor, Gemini CLI, Aider, Zed, Warp, Devin, Copilot coding agent, Factory, Jules, opencode, Windsurf and more. Plain Markdown, no required fields. |
| AGENTS.md (nested) | Per-package instruction files in a monorepo | Agents read the nearest AGENTS.md up the directory tree; the closest one takes precedence, so each subproject can ship its own. |
Tool-Specific Files (8)
| Command / Syntax | What it does | Notes |
|---|---|---|
| CLAUDE.md | Claude Code project memory file | Loaded at session start from the project root and parent directories; edit in-session with the /memory command documented on our Claude Code page. |
| ~/.claude/CLAUDE.md | User-level Claude Code memory | Applies across all your projects; project files add to it. |
| .cursor/rules/*.mdc | Cursor project rules (current format) | Rule files with metadata controlling when each rule applies. |
| .cursorrules | Cursor legacy single-file rules | Still read for backwards compatibility; new projects should use .cursor/rules/. |
| .github/copilot-instructions.md | GitHub Copilot repository-wide custom instructions | Applies to Copilot Chat and the coding agent for that repository. |
| *.instructions.md | Copilot scoped instruction files | Per-path instructions with applyTo front matter, alongside the repository-wide file. |
| GEMINI.md | Gemini CLI context file | Project instructions for Gemini CLI; it also reads AGENTS.md. |
| CONVENTIONS.md | Aider coding conventions file | Loaded with --read or listed in .aider.conf.yml so it is marked read-only for the LLM. |
Compatibility Patterns (1)
| Command / Syntax | What it does | Notes |
|---|---|---|
| ln -s AGENTS.md CLAUDE.md | Symlink pattern: keep one instruction source for tools with their own filename | A single AGENTS.md stays canonical while filename-specific tools follow the link. |
Frequently Asked Questions
What counts as a prompt command on this site?
A literal, typeable token from official documentation: slash commands, @ mentions, chat variables, generation parameters, and prompt syntax operators. We do not collect prompt templates or example prompts.
How is this different from the keyboard shortcuts pages?
The Shortcuts section covers keys you press and terminal CLI invocations. This section covers what you type inside an AI tool's prompt to control it - commands, parameters, and syntax.
Where does the data come from?
Each platform lists its source: official docs pages, vendor help centers, or the project's own wiki. Every table links its source, and nothing is invented.
Developers: this data is available as JSON at /api/v1/prompts/all.json and per platform at /api/v1/prompts/<key>.json.