[FEATURE] Add support for RULE.md

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code’s rules system treats every .md file under .claude/rules/ as a rule.

This file-centric approach creates ambiguity when a rule requires additional context such as supporting markdown, scripts, or examples. Supporting files cannot be safely colocated with a rule without risking accidental interpretation as independent rules.

Proposed Solution

Define rules in Claude Code as directory-scoped units rather than standalone markdown files. Each rule is represented by a directory, whose name is the rule’s identifier, and contains a single RULE.md file as the canonical entry point.

Only RULE.md files are treated as loadable rules. All other files within the directory—additional markdown, scripts, prompts, examples, or fixtures—are considered support artifacts and are never interpreted as rules.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

API and model interactions

Use Case Example

_No response_

Additional Context

Recently, the Cursor folks have moved their rules into this approach.