maintain-project-rules

Audit .cursor/rules/*.mdc files for prefix, frontmatter, and content conformance.

1|Updated Jan 15, 2026

Search Tags:#audit #governance #conventions #rules #cursor #mdc #prefix

Ready to run

npx skills add https://github.com/janjaszczak/cursor --skill maintain-project-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maintain-project-rules
Source: https://github.com/janjaszczak/cursor/tree/main/skills/maintain-project-rules
Command: npx skills add https://github.com/janjaszczak/cursor --skill maintain-project-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and maintain project rules in .cursor/rules/. Use when auditing project rules, checking prefix convention, syncing doc/rules.md, or when the user asks about .cursor/rules or prefix convention.

Core Features & Use Cases

Audit and verify .mdc files in the rules directory for correct prefixes, frontmatter, and content alignment with the reference tables.
Propose actionable changes (rename, merge, or flag duplicates) to keep rules in sync with cursor-rules-principles and retro guidance.
Sync documentation (doc/rules.md) with current rules to ensure consistency across the repository.

Quick Start

Run the maintain-project-rules skill to audit .cursor/rules and prepare change proposals.

Frequently Asked Questions about maintain-project-rules

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

FAQPage Schema

How do I audit .cursor/rules files for prefix and frontmatter consistency?▼

Auditing .cursor/rules files involves scanning all *.mdc files to verify their prefixes, frontmatter, and content against project rules reference tables, identifying duplicates, missing prefixes, and suggesting renames or merges.

What is the best way to maintain .mdc rule files in a flat directory structure?▼

To maintain .mdc rule files in a flat directory structure, audit them against cursor-rules-principles and retro guidelines to flag duplicates, missing prefixes, and propose actionable changes like renames or deletions without applying modifications.

How do I sync doc/rules.md with my current .cursor/rules directory?▼

Syncing doc/rules.md with current rules ensures repository consistency by comparing existing *.mdc files against the documentation and generating actionable proposals to update either documentation or the rules themselves.

Does the cursor rules audit automatically apply changes to my files?▼

No, the cursor rules audit reports findings and recommended actions like renames, merges, or deletions per reference guidelines without applying changes, ensuring you maintain control over your project rules directory.

Why do I need to check prefixes in my .cursor/rules files?▼

Checking prefixes in .cursor/rules files ensures conformance to cursor-rules-principles and retro guidelines, preventing duplicate rules, missing naming conventions, and incorrect frontmatter alignment with the project rules reference.