rules-organizer

Organize Claude Code instructions into modular rule files under .claude/rules.

1|Updated May 5, 2025
One-click install
npx skills add https://github.com/jdeweedata/circletel --skill rules-organizer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rules-organizer
Source: https://github.com/jdeweedata/circletel/tree/main/.claude/skills/rules-organizer
Command: npx skills add https://github.com/jdeweedata/circletel --skill rules-organizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizing Claude Code instructions into modular rule files helps teams standardize guidance, improve discoverability, and enable cross-project reuse of best practices.

Core Features & Use Cases

  • Modular rule files: Break CLAUDE.md into focused, topic-specific rules under .claude/rules.
  • Directory structure guidance: Provide recommended layouts (general, frontend, backend, domain, testing) to keep rules organized.
  • Migration and sharing: Support migrating large CLAUDE.md into files and enabling symlinks or shared rule repos across projects.

Quick Start

Create a .claude/rules/ directory and place focused rule files (one topic per file) such as .claude/rules/general/code-style.md, .claude/rules/backend/api.md, etc. Then update CLAUDE.md to reference the extracted rule files. Use symlinks for cross-project sharing if needed.

Frequently Asked Questions about rules-organizer

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

FAQPage Schema
How do I organize Claude Code instructions into modular rule files?▼

To organize Claude Code instructions, create a .claude/rules/ directory and place focused, topic-specific rule files inside it. Update CLAUDE.md to reference these extracted files, ensuring consistent project standards and improved discoverability.

What is the recommended directory structure for Claude Code rules?▼

The recommended directory structure for Claude Code rules uses categorized subdirectories under .claude/rules/, such as general, frontend, backend, domain, and testing. This layout keeps topic-specific rules organized and easily discoverable.

How do I migrate a large CLAUDE.md into separate rule files?▼

Migrating a large CLAUDE.md involves breaking it down into focused, single-topic files within a .claude/rules/ directory. After extracting the content into modular files, update CLAUDE.md to reference them, enabling better management and cross-project reuse.

Can I share Claude Code rule files across multiple projects?▼

You can share Claude Code rule files across multiple projects by using symlinks or shared rule repositories. This approach enables cross-project reuse of best practices and maintains consistent coding standards without duplicating rule files.

Why should I break down coding standards into modular rule files?▼

Breaking down coding standards into modular rule files helps teams standardize guidance, improve discoverability, and enable cross-project reuse of best practices. It replaces large, monolithic instruction files with structured, focused domain-specific rules.