Rules that load only when needed.

Founder OS - Path-Scoped Rules

Rules that load only when needed.

Most people dump everything into one CLAUDE.md. 3% know about .claude/rules/ - a folder where each file can have its own path filter. API rules only load when you touch API files.

The problem with one big CLAUDE.md

Why splitting rules into a folder beats a single file

the wrong way

One CLAUDE.md with 500 lines. API style guides, test conventions, DB rules, frontend patterns, security policies, all at once.

Problem: every rule loads on every file. Context bloat. Reduced adherence. Irrelevant instructions taking up tokens.

the right way

Split into .claude/rules/. Each file has a paths: filter. API rules only load when src/api/** is touched.

Result: Claude gets exactly the rules it needs. Nothing extra. Better adherence. Lower token cost.

Example structure

Click any file to see the rule content

← click a file to see the rule

How path scoping works

The frontmatter syntax

Real rule examples

Common patterns you can use today

playbooks, templates, and tools that actually save you hours. straight to your inbox. no spam. unsubscribe anytime.

Want this running in your business, not just your terminal? Our Claude Code development agency ships it for you, or book a free consultation to scope your setup.

Day 19: Founder OS - Custom Subagents & Model Routing

Day 21: Founder OS - Output Styles & Explanatory Mode