claude-md-rules-creator

Generate and refactor CLAUDE.md and path-scoped rule files.

3|Updated May 11, 2026
One-click install
npx skills add https://github.com/anilcancakir/claude-code --skill claude-md-rules-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-md-rules-creator
Source: https://github.com/anilcancakir/claude-code/tree/main/plugins/ac/skills/claude-md-rules-creator
Command: npx skills add https://github.com/anilcancakir/claude-code --skill claude-md-rules-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It helps you author, refactor, and debug Claude Code’s CLAUDE.md and path-scoped rule files so the model consistently follows the standing instructions you intend.

Core Features & Use Cases

  • Choose the right CLAUDE.md layer and scope (managed vs user-global vs project-team vs project-personal), including when to use .claude/rules/<topic>.md and when to keep content inline in CLAUDE.md or CLAUDE.local.md.
  • Write effective rule content that actually changes behavior, including how to use paths: for path-scoped rules and how to import other sources of truth with @path (and how to avoid common loader footguns like globs:).
  • Debug “Claude is not following my CLAUDE.md” by checking what’s loaded, identifying conflicts and redundancies, and addressing issues like file shape, path scoping, compact/persistence behavior, and overgrown instruction files.

Quick Start

Ask the skill to create or rewrite the correct CLAUDE.md/rules file for your team or project, including any path-scoped rules you want to apply.

Frequently Asked Questions about claude-md-rules-creator

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

FAQPage Schema
Why is Claude Code not following my CLAUDE.md instructions?

Claude Code ignoring CLAUDE.md often stems from file shape issues, path scoping conflicts, or overgrown instruction files. Debug by checking what memory is loaded, identifying redundant rules, and refactoring bloated files into scoped .claude/rules/*.md files.

How do I write path-scoped rules for Claude Code?

Path-scoped rules in Claude Code use the paths: directive in .claude/rules/*.md files to apply instructions only to matching file locations. This ensures standing requirements trigger reliably based on the specific directory or file path being modified.

When should I use CLAUDE.md versus .claude/rules/*.md files?

Use CLAUDE.md for project-team conventions and CLAUDE.local.md for personal preferences, keeping content inline. Split into .claude/rules/*.md files when instructions become bloated or need path-scoped behavior to avoid loader conflicts.

What is the best way to structure CLAUDE.md files for a team?

The best structure for team CLAUDE.md files involves choosing the right scope layer, splitting bloated files into focused rules, using @path imports for shared sources of truth, and avoiding anti-patterns like globs: to ensure memory injection loads correctly.

Can I import external sources of truth into Claude Code instruction files?

Yes, Claude Code instruction files support @path imports to reference external sources of truth directly within CLAUDE.md or .claude/rules/*.md files. This avoids duplicating content while keeping memory loading and compact persistence behavior reliable.

What are common loader footguns when writing Claude Code memory rules?

Common Claude Code loader footguns include using globs: instead of paths: for scoping, creating overgrown instruction files that degrade model adherence, and failing to identify conflicts between inline CLAUDE.md content and path-scoped rule files.