create-rule

Create and manage Cursor rule files with YAML frontmatter in .cursor/rules/.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create and manage Cursor rule files to enforce coding standards, project conventions, and consistent patterns across a codebase and AI workflows, reducing ambiguity in agent guidance.

Core Features & Use Cases

  • Define rules in .cursor/rules/ as .mdc files to enforce coding standards and project conventions.
  • Use frontmatter in each rule to describe its purpose and the file patterns (globs) it should apply to.
  • Quick-start templates and guidelines to create rules for common patterns and workflows.

Quick Start

Create a new file under .cursor/rules/ named example.mdc with a frontmatter description and globs, then write your rule content below.

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 my project?

To create persistent Cursor rules, generate .mdc files inside the .cursor/rules/ directory with YAML frontmatter specifying the rule name, description, and file globs for project-wide AI guidance.

What are Cursor .mdc rule files and how do they work?

Cursor .mdc rule files are configuration documents in .cursor/rules/ that use YAML frontmatter to define name, description, and globs, ensuring consistent AI coding standards across matching file patterns.

Can I apply Cursor rules to specific file patterns in my codebase?

Yes, you can apply Cursor rules to specific file patterns by defining globs in the YAML frontmatter of your .mdc files, targeting only the relevant files for project conventions.

How do I enforce coding conventions across AI workflows in Cursor?

You enforce coding conventions across AI workflows by writing .mdc files in .cursor/rules/ with descriptive frontmatter, reducing ambiguity in agent guidance and maintaining consistent documentation.

Do I need a specific directory structure to manage Cursor rules?

Yes, you need a .cursor/rules/ directory containing .mdc files with YAML frontmatter that includes at minimum a name and description to govern AI guidance and globs properly.

What's the best way to set up project-wide AI guidance in Cursor?

The best way to set up project-wide AI guidance is creating .mdc files in .cursor/rules/ with frontmatter and rule content, using quick-start templates to enforce coding standards and workflows.