What is the difference between rules and hooks in Claude Code?

Rules (defined in CLAUDE.md or .claude/rules/) are natural language instructions that Claude interprets with judgment. Hooks are deterministic shell commands that execute automatically on specific events.

How do I scope a rule to only specific files or directories?

You can use YAML frontmatter in a rule file within .claude/rules/ to define a 'paths' list using glob patterns, such as 'src/api/**/*.ts' for API-specific rules.

Where should I store project-wide coding rules?

Project-wide rules should be stored in the root ./CLAUDE.md file or within the ./.claude/rules/ directory to be shared with your team via Git.

Can I use memory to store local preferences that aren't shared?

Yes, use ./CLAUDE.local.md for project-specific instructions that only apply to you, or ~/.claude/CLAUDE.md for global preferences across all your projects.

Claude Code Memory and Rules Manager

Name: Claude Code Memory and Rules Manager
Author: dwmkerr

bydwmkerr

•

Developer Tools

Configures and optimizes Claude Code's persistent memory system, including CLAUDE.md files and modular project rules.

This skill provides comprehensive guidance on managing Claude Code’s persistent memory hierarchy, enabling developers to maintain consistent coding conventions, project instructions, and session learnings. It facilitates the setup of CLAUDE.md files at various scopes—from organizational policies to local project preferences—and the implementation of path-scoped modular rules within the .claude/rules directory. By distinguishing between natural language rules and deterministic hooks, it ensures Claude has the right context to follow specific architectural patterns and style guides across different files and projects.

Key Features

01Guidance on choosing between natural language rules and automated hooks

02Standardized CLAUDE.md structure generation and refinement

0312 GitHub stars

04Comprehensive memory hierarchy management from Global to Local scopes

05Automated memory persistence and session learning optimization

06Modular rule configuration with path-scoped glob patterns

Use Cases

01Persisting personal developer preferences across multiple local development worktrees

02Enforcing project-specific coding standards and architectural patterns across a team

03Scoping specific security or documentation requirements to relevant file paths using rules

Key Features

01Guidance on choosing between natural language rules and automated hooks

02Standardized CLAUDE.md structure generation and refinement

0312 GitHub stars

04Comprehensive memory hierarchy management from Global to Local scopes

05Automated memory persistence and session learning optimization

06Modular rule configuration with path-scoped glob patterns

Use Cases

01Persisting personal developer preferences across multiple local development worktrees

02Enforcing project-specific coding standards and architectural patterns across a team

03Scoping specific security or documentation requirements to relevant file paths using rules