command-creator

To create custom Opencode commands, add a Markdown file named <name>.md under the command/ directory. Define frontmatter fields like name, description, agent, and model, then write your prompt body to automate the task.

Configuring an Opencode command requires defining frontmatter fields including name, description, agent, and model. These fields tailor the command behavior alongside a Markdown body that serves as the prompt runtime.

Yes, you can define global Opencode commands by placing Markdown files in the ~/.config/opencode/command/ directory. Project-scoped commands go in .opencode/command/ to ensure consistent behavior across specific projects.

You invoke a custom command from the Opencode TUI by typing /<name>. The filename of your Markdown file in the command directory automatically becomes the command name used for invocation.

The best way to standardize prompt engineering workflows is creating reusable Opencode commands. By defining standardized prompts in Markdown files with specific frontmatter, teams ensure consistent behavior across multiple projects.

No dependencies are required to set up prompt automation. You only need to create Markdown files with appropriate frontmatter configuration in the designated command directories to start automating tasks.