create-rule

Persistent AI rules for Cursor projects are set up by creating .mdc files inside the .cursor/rules/ directory. These files use YAML frontmatter to define globs and descriptions, ensuring the AI agent consistently follows your project conventions and coding standards.

.cursor/rules files are Markdown configuration files that provide persistent context to guide AI agent behavior. You need them when outlining project conventions, file-specific patterns, or coding standards to ensure consistent AI behavior across Cursor workflows.

Yes, you can define file-specific patterns by creating rule files in .cursor/rules/. The YAML frontmatter in each file uses globs to target specific file types or directories, applying distinct coding standards and project conventions only where needed.

The best way to structure a baseline ruleset is to generate .mdc files within .cursor/rules/ containing your coding standards. You can optionally include scripts/, references/, and assets/ directories to support and organize your project's specific AI guidance policies.

No external dependencies are required to create Cursor rules. The process relies entirely on generating standard .mdc files with YAML frontmatter in your local .cursor/rules/ directory, though optional scripts and references can be included for advanced automation.

Your AI agent may not be following conventions because the rules are not properly defined in .cursor/rules/. By storing your coding standards as .mdc files with correct YAML frontmatter and file globs, you provide the persistent context needed for consistent behavior.