smithery.ai

maintain-project-rules

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.

First seen Mar 26, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents cursor

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,485 B
  • docs SUMMARY.md 228 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

maintain-project-rules

Activation gate

Use if:

  • User asks to audit or maintain project rules, check prefix convention, or sync doc/rules.md.
  • Context involves .cursor/rules/, rule files (.mdc), or conventions from cursor-rules-principles / retro.

Source of truth

  • cursor-rules-principles.md (in repo or ~/.cursor) – prefix table 000–500, general principles. See [reference.md](reference.md) for full prefix table.
  • commands/retro.md (PROJECT RULES section) – prefixes 000/050/100/200/900, flat .mdc, no subfolders in rules.

Procedure

  1. Resolve paths

- PROJECTROOT: git rev-parse --show-toplevel - PROJECTCURSORDIR: ${PROJECTROOT}/.cursor - PROJECTRULESDIR: ${PROJECTCURSORDIR}/rules - If PROJECTRULESDIR does not exist, report "No .cursor/rules in this repo" and stop.

  1. Audit

- List all *.mdc in PROJECTRULESDIR (flat; no subfolders per convention). - For each file: name, prefix vs principles/retro, frontmatter (description, alwaysApply, globs), line count (~<50 preferred), overlap with other rules (duplicate or near-duplicate content). - Flag: missing prefix, wrong prefix slot, missing/invalid frontmatter, oversized file, duplicate content.

  1. Proposals

- RENAME: file without numeric prefix → suggest prefix from reference.md / retro. - MERGE: two or more rules with overlapping scope → suggest target file and sections. - DELETE: only with clear justification (obsolete, fully merged); do not execute without user confirmation. - Do not delete, move, or rename until user confirms.

  1. Sync doc/rules.md

- If repo has doc/rules.md or docs/rules.md: update the "Context-Specific Rules" (or equivalent) list to match current .mdc files and their globs/scope. Keep doc and rules directory in sync.

Output

  • Report: table of files (path, prefix OK?, frontmatter OK?, lines, notes); list of proposals (RENAME/MERGE/DELETE with reason and target).
  • Closing line: "Do zastosowania: potwierdź zmiany lub wywołaj agenta rules-keeper."
  • No destructive changes without explicit user confirmation.

Reference

For full prefix table and conventions, see [reference.md](reference.md).