create-rule

Create Cursor rules with YAML frontmatter and save them under .cursor/rules/.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates and maintains persistent Cursor rules to enforce coding standards and project conventions across sessions.

Core Features & Use Cases

  • Define rules in .cursor/rules/ to provide persistent context for AI agents.
  • Infer multiple rules from user conversations and apply them across sessions or projects.
  • Validate the rule format and file-pattern scopes before saving to ensure consistency.

Quick Start

Define a new rule by specifying its purpose, scope, and file patterns, then save it as a .mdc file under .cursor/rules/.

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 to guide AI agents across sessions?

To create persistent Cursor rules, define your project standards and conventions, specify their scope and file patterns, and save them as .mdc files under the .cursor/rules/ directory to guide AI agents across sessions. The system validates the format and inputs before saving.

What is the .mdc format used for defining file-specific Cursor rules?

The .mdc format for Cursor rules uses YAML frontmatter to define descriptions, scopes, and file patterns. It is stored under the .cursor/rules/ directory to provide persistent context and enforce coding standards for AI agents.

Can I infer multiple Cursor rules from a single conversation or project context?

Yes, you can infer multiple Cursor rules from user conversations or previous context. The system analyzes the provided context to automatically generate and apply multiple rules across sessions or projects.

How do I validate file-pattern scopes before saving Cursor rules?

Validating file-pattern scopes before saving Cursor rules is handled automatically by the system. It checks the .mdc rule format, YAML frontmatter, and input consistency to ensure the scope patterns are correct before writing to disk.

Do I need any external dependencies to set up project-wide coding standards in Cursor?

No external dependencies are required to set up project-wide coding standards in Cursor. You only need to create .mdc files with proper YAML frontmatter under the .cursor/rules/ directory to enforce your conventions.

When should I use project-wide rules versus file-specific rules for AI guidance?

Use project-wide Cursor rules for general coding standards and conventions, and file-specific rules when you need targeted AI guidance for particular file patterns. Both types are stored as .mdc files under .cursor/rules/ with appropriate scope definitions.