rules-guide

Organize Claude memory rules into modular, path-scoped Markdown files.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/biwakonbu/cc-plugins --skill rules-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rules-guide
Source: https://github.com/biwakonbu/cc-plugins/tree/main/plugins/memory-optimizer/skills/rules-guide
Command: npx skills add https://github.com/biwakonbu/cc-plugins --skill rules-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a clear framework for organizing Claude memory rules into modular, maintainable components that scale with team needs and project complexity.

Core Features & Use Cases

  • Modular rule organization for CLAUDE memory and behavior
  • Path-scoped rule files to apply rules selectively across projects
  • Guidance on splitting large CLAUDE.md content into smaller, reusable modules for teams

Quick Start

Create a .claude/rules/ directory with topic-based Markdown files and compare them against the path guidelines described in this guide.

Frequently Asked Questions about rules-guide

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

FAQPage Schema
How do I structure Claude memory rules for a large team project?

Structure Claude memory rules by creating a .claude/rules/ directory with topic-based Markdown files, using frontmatter to define metadata and path-based scoping to apply rules selectively across different project areas.

What is the best way to split a large CLAUDE.md file into reusable modules?

Split a large CLAUDE.md file by separating content into modular rule files, ensuring components are categorized into rules, references, and assets to maintain scalability and reusability for team workflows.

Can I scope Claude memory rules to specific project directories?

Yes, you can scope Claude memory rules to specific directories by using path-based scoping within the frontmatter of your modular rule files, ensuring guidelines apply selectively based on project paths.

When do I need to modularize my Claude memory rules?

You need to modularize Claude memory rules when managing large rule sets, multiple topics, or evolving guidelines, ensuring the structure remains maintainable and scalable as team needs and project complexity grow.

Does organizing memory rules into modular files affect how Claude processes guidelines?

Organizing memory rules into modular files with frontmatter and path-based scoping ensures Claude processes guidelines selectively, applying only the relevant rules to the appropriate project contexts and directories.

Are there limitations to splitting CLAUDE.md content into separate rules and references?

When splitting CLAUDE.md content, ensure the separated rules, references, and assets maintain clear path-based scoping and frontmatter definitions, as poorly structured modules may not apply correctly to their intended project directories.