> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kombai.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Commands
> Custom commands let you create reusable prompts and workflows as Markdown files. Use them to standardize common processes of your team into single commands and automate repetitive tasks.
export const Send = props => {
return ;
};
export const DeleteIcon = props => {
return ;
};
export const NewChat = props => {
return ;
};
export const Rules = props => {
return ;
};
You can create markdown files directly in the `./kombai/commands/` directory of your project or
add the existing commands directory path via the **Rules and Commands** tab on the [Settings](/account/settings) page.
## Run custom commands
1. [Launch Kombai extension](/get-started/set-up#launch-kombai-extension) in your IDE.
2. Type a slash `/` in the chat input box to check the available commands.
3. Select the custom command you want to run.
4. Add any other instructions you want to add to Kombai.
5. Press Enter or click the button to run the command.
Kombai will now run the workflow defined in the associated Markdown.
## Add directory path
Kombai supports project-level as well as global commands. Project-level commands are specific to a project, while global commands are supported across all projects where you use Kombai.
Here's how to add a directory path:
1. Copy the path of the directory that contains your custom commands' Markdown files.
2. Click the icon below the chat input box to open the **Rules and Commands** tab in the [Settings](/account/settings) page.
3. Scroll to the **Commands** section.
4. Paste the path of the folder into the **Project Commands Directory** (for project-level commands) or **User Commands Directory** (for global commands) input field.
5. Click the icon.
## Delete directory path
Here's how to delete a directory path:
1. [Launch Kombai extension](/get-started/set-up#launch-kombai-extension) in your IDE.
2. Click the icon below the chat input box to open the **Rules and Commands** tab in the [Settings](/account/settings) page.
3. Go to the **Commands** section.
4. Click the icon next to the directory path you want to delete. Alternatively, you can click the **Remove All** button to delete all saved directory paths.
## Team commands
Team commands let you share and discover commands across your team. Publish your local commands for team members to use, or use commands shared by others.
You need to be part of the Team plan to use team commands.
### Publish a command
You can publish any local command from your repo to your team. To publish a command:
1. [Launch Kombai extension](/get-started/set-up#launch-kombai-extension) in your IDE.
2. Click the icon below the chat input box.
3. Go to the **Team Commands** tab.
4. Under **Publish Your Commands**, select the local command you want to publish from the dropdown.
5. Click the **Publish** button.
The command will now be available to all members of your team.
You must have local commands added in the **Commands** tab before you can publish them.
### Discover and use team commands
The **Team Commands** section lists all commands published by members of your team. You can search for commands by name or author using the search bar at the top of the list.
To use a team command, type a slash `/` in the chat input box — team commands appear alongside your local commands in the command list.
## FAQs
[Spec Kit](https://github.com/github/spec-kit) and [OpenSpec](https://github.com/Fission-AI/OpenSpec) are tools that allow you to create custom commands. You can add the path to the generated commands folder via the **Rules and Commands** tab in the [Settings](/account/settings) page.
For example, if you have a `.cursor/commands` folder created by OpenSpec, simply add that path in the settings. See ["Add directory path"](#add-directory-path) for instructions on how to add a directory.
If you are using Spec Kit, you have to also add the path to the new *specify-rules* file, e.g., `.cursor/rules/specify-rules.mdc`. Refer to the ["Add rule path"](/features/rules#add-rule-path) guide for instructions on how to add a rule path.