creating-cursor-commands

Cursor slash commands must be plain Markdown files without frontmatter, stored in .cursor/commands with kebab-case filenames. Include a single content field, required examples, and explicit instructions aligned with Cursor's schema to ensure reliable parsing and consistent behavior.

Use descriptive kebab-case filenames in the .cursor/commands directory. Commands contain only Markdown content with no metadata, a single content field, and mandatory examples. This structure ensures schema compliance and prevents parsing errors across your team's AI-assisted workflows.

Yes. Take your prompt, remove any frontmatter, restructure it into a single content field with explicit instructions and examples, then save it as a kebab-case Markdown file in .cursor/commands. Validation against Cursor's schema ensures the converted command works reliably.

Common causes include frontmatter in the file, multiple content fields, missing examples, or non-compliant schema structure. Cursor commands require plain Markdown only, a single content section, descriptive instructions, and required examples—no metadata or formatting deviations.

Apply consistent naming conventions, structure, and schema validation across all commands in .cursor/commands. Define command templates for common tasks like code review and testing, enforce the no-frontmatter rule, and include detailed examples so all team members produce reliable, predictable AI-assisted outputs.