create-rule

Create persistent Cursor rules with YAML frontmatter in .cursor/rules/.

8|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kensaurus/cursor-kenji --skill create-rule-kensaurus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-rule
Source: https://github.com/kensaurus/cursor-kenji/tree/main/skills-cursor/create-rule
Command: npx skills add https://github.com/kensaurus/cursor-kenji --skill create-rule-kensaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to establish and enforce persistent Cursor AI guidance by creating centralized rule definitions that influence agent behavior across projects.

Core Features & Use Cases

  • Create and manage rules under .cursor/rules/ with YAML frontmatter describing purpose, scope, and applicability.
  • Prevent duplication by checking existing rules and provide pathways to extend or refine existing conventions.
  • Provide clear guidance on rule formats, validation, and naming to ensure consistency across projects.

Quick Start

Create a new .mdc rule file in .cursor/rules/ with a descriptive filename and a YAML frontmatter block describing the rule.

Frequently Asked Questions about create-rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create persistent Cursor rules for AI guidance?

To create persistent Cursor rules, generate a new .mdc file within the .cursor/rules/ directory, including a YAML frontmatter block to define the rule's purpose, scope, and applicability for AI agents.

What is the correct file structure for Cursor project conventions?

The correct file structure for Cursor project conventions places rule definitions as .mdc files inside the .cursor/rules/ directory, optionally utilizing separate components directories for scripts, references, and assets.

How do I prevent duplicate coding standards in Cursor rules?

To prevent duplicate coding standards, the rule creation process checks existing rules in the .cursor/rules/ directory and provides pathways to extend or refine current conventions rather than generating redundant files.

Can I use YAML frontmatter to define AI agent guidance scope?

Yes, YAML frontmatter is required in .cursor/rules/ files to describe the rule's purpose, scope, and applicability, ensuring the AI agent guidance is properly scoped and applied across projects.

What is the best way to manage team coding standards in Cursor?

The best way to manage team coding standards is by centralizing rule definitions in .cursor/rules/ with consistent naming and YAML frontmatter, providing clear validation and guidance on rule formats to enforce conventions.

Are there limitations to what I can define in Cursor rules?

Limitations include needing to adhere to specific .mdc file formats and YAML frontmatter conventions in .cursor/rules/, as improper validation or naming can disrupt how agent guidance and project conventions are applied.