Ruler: Centralise Your AI Coding Assistant Instructions

---

Beta Research Preview

• Please test this version carefully in your environment
• Report issues at https://github.com/intellectronica/ruler/issues

Why Ruler?

Managing instructions across multiple AI coding tools becomes complex as your team grows. Different agents (GitHub Copilot, Claude, Cursor, Aider, etc.) require their own configuration files, leading to:

• Inconsistent guidance across AI tools
• Duplicated effort maintaining multiple config files
• Context drift as project requirements evolve
• Onboarding friction for new AI tools
• Complex project structures requiring context-specific instructions for different components

Ruler solves this by providing a single source of truth for all your AI agent instructions, automatically distributing them to the right configuration files. With support for nested rule loading, Ruler can handle complex project structures with context-specific instructions for different components.

Core Features

• Centralised Rule Management: Store all AI instructions in a dedicated .ruler/ directory using Markdown files
• Nested Rule Loading: Support complex project structures with multiple .ruler/ directories for context-specific instructions
• Automatic Distribution: Ruler applies these rules to configuration files of supported AI agents
• Targeted Agent Configuration: Fine-tune which agents are affected and their specific output paths via ruler.toml
• MCP Server Propagation: Manage and distribute Model Context Protocol (MCP) server settings
• .gitignore Automation: Keeps generated agent config files out of version control automatically
• Simple CLI: Easy-to-use commands for initialising and applying configurations

Supported AI Agents

Getting Started

Installation

Requires Node.js ^20.19.0 || ^22.12.0 || >=23.

Global Installation (Recommended for CLI use):

npm install -g @intellectronica/ruler

Using npx (for one-off commands):

npx @intellectronica/ruler apply

Project Initialisation

1. Navigate to your project's root directory
2. Run ruler init
3. This creates:

• .ruler/ directory
• .ruler/AGENTS.md: The primary starter Markdown file for your rules
• .ruler/ruler.toml: The main configuration file for Ruler (now contains sample MCP server sections; legacy .ruler/mcp.json no longer scaffolded)
• (Optional legacy fallback) If you previously used .ruler/instructions.md, it is still respected when AGENTS.md is absent. (The prior runtime warning was removed.)

Additionally, you can create a global configuration to use when no local .ruler/ directory is found:

ruler init --global

The global configuration will be created to $XDG_CONFIG_HOME/ruler (default: ~/.config/ruler).

Core Concepts

The .ruler/ Directory

This is your central hub for all AI agent instructions:

• Primary File Order & Precedence:
  1. A repository root AGENTS.md (outside .ruler/) if present (highest precedence, prepended)
  2. .ruler/AGENTS.md (new default starter file)
  3. Legacy .ruler/instructions.md (used as the primary file only if .ruler/AGENTS.md is absent; no longer emits a deprecation warning)
  4. Remaining discovered .md files under .ruler/ (and subdirectories) in sorted order, including instructions.md when both top-level files exist
• Rule Files (*.md): Discovered recursively from .ruler/ or $XDG_CONFIG_HOME/ruler and concatenated in the order above
• Concatenation Marker: Each file's content is prepended with <!-- Source: <relative_path_to_md_file> --> for traceability
• ruler.toml: Master configuration for Ruler's behavior, agent selection, output paths, and MCP server settings
• mcp.json: (Legacy, deprecated) Shared MCP server settings - no longer scaffolded but still supported for backward compatibility

This ordering lets you keep a short, high-impact root AGENTS.md (e.g. executive project summary) while housing detailed guidance inside .ruler/.

Nested Rule Loading

Ruler now supports nested rule loading with the --nested flag, enabling context-specific instructions for different parts of your project:

project/
├── .ruler/           # Global project rules
│   ├── AGENTS.md
│   └── coding_style.md
├── src/
│   └── .ruler/       # Component-specific rules
│       └── api_guidelines.md
├── tests/
│   └── .ruler/       # Test-specific rules
│       └── testing_conventions.md
└── docs/
    └── .ruler/       # Documentation rules
        └── writing_style.md

How it works:

• Discover all .ruler/ directories in the project hierarchy
• Load and concatenate rules from each directory in order
• Decide whether nested mode is enabled using the following precedence:
  1. ruler apply --nested (or --no-nested) takes top priority
  2. nested = true in ruler.toml
  3. Default to disabled when neither option is provided
• When a run is nested, downstream configs are forced to keep nested = true. If a child config attempts to disable it, Ruler keeps nested processing active and emits a warning in the logs.
• Nested processing carries forward each directory's own MCP bundle and configuration settings so that generated files remain scoped to their source directories while being normalized back to the project root.

[!CAUTION] Nested mode is experimental and may change in future releases. The CLI logs this warning the first time a nested run is detected so you know the behavior may evolve.

Perfect for:

• Monorepos with multiple services
• Projects with distinct components (frontend/backend)
• Teams needing different instructions for different areas
• Complex codebases with varying standards

Best Practices for Rule Files

Granularity: Break down complex instructions into focused .md files:

• coding_style.md
• api_conventions.md
• project_architecture.md
• security_guidelines.md

Example rule file (.ruler/python_guidelines.md):

# Python Project Guidelines

## General Style

- Follow PEP 8 for all Python code
- Use type hints for all function signatures and complex variables
- Keep functions short and focused on a single task

## Error Handling

- Use specific exception types rather than generic `Exception`
- Log errors effectively with context

## Security

- Always validate and sanitize user input
- Be mindful of potential injection vulnerabilities

Usage: The apply Command

Primary Command

ruler apply [options]

The apply command searches upward from --project-root (default: current directory) for the nearest .ruler/ directory. If no local .ruler/ directory is found, it falls back to $XDG_CONFIG_HOME/ruler.

Options

Common Examples

Apply rules to all configured agents:

ruler apply

Apply rules only to GitHub Copilot and Claude:

ruler apply --agents copilot,claude

Apply rules only to Firebase Studio:

ruler apply --agents firebase

Apply rules only to Warp:

ruler apply --agents warp

Apply rules only to Trae AI:

ruler apply --agents trae

Apply rules only to RooCode:

ruler apply --agents roo

Use a specific configuration file:

ruler apply --config ./team-configs/ruler.frontend.toml

Apply rules with verbose output:

ruler apply --verbose

Apply rules but skip MCP and .gitignore updates:

ruler apply --no-mcp --no-gitignore

Usage: The revert Command

The revert command safely undoes all changes made by ruler apply, restoring your project to its pre-ruler state. It intelligently restores files from backups (.bak files) when available, or removes generated files that didn't exist before.

Why Revert is Needed

When experimenting with different rule configurations or switching between projects, you may want to:

• Clean slate: Remove all ruler-generated files to start fresh
• Restore originals: Revert modified files back to their original state
• Selective cleanup: Remove configurations for specific agents only
• Safe experimentation: Try ruler without fear of permanent changes

Primary Command

ruler revert [options]

Options

Common Examples

Revert all ruler changes:

ruler revert

Preview what would be reverted (dry-run):

ruler revert --dry-run

Revert only specific agents:

ruler revert --agents claude,copilot

Revert with detailed output:

ruler revert --verbose

Keep backup files after reverting:

ruler revert --keep-backups

Configuration (ruler.toml) in Detail

Location

Defaults to .ruler/ruler.toml in the project root. Override with --config CLI option.

Complete Example

# Default agents to run when --agents is not specified
# Uses case-insensitive substring matching
default_agents = ["copilot", "claude", "aider"]

# --- Global MCP Server Configuration ---
[mcp]
# Enable/disable MCP propagation globally (default: true)
enabled = true
# Global merge strategy: 'merge' or 'overwrite' (default: 'merge')
merge_strategy = "merge"

# --- MCP Server Definitions ---
[mcp_servers.filesystem]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/project"]

[mcp_servers.git]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-git", "--repository", "."]

[mcp_servers.remote_api]
url = "https://api.example.com"

[mcp_servers.remote_api.headers]
Authorization = "Bearer your-token"

# --- Global .gitignore Configuration ---
[gitignore]
# Enable/disable automatic .gitignore updates (default: true)
enabled = true
# Write managed entries to .git/info/exclude instead of .gitignore (default: false)
local = false

# --- Backup Configuration ---
[backup]
# Enable/disable creation of .bak backup files (default: true)
enabled = true

# --- Agent-Specific Configurations ---
[agents.copilot]
enabled = true

[agents.claude]
enabled = true
output_path = "CLAUDE.md"

[agents.aider]
enabled = true
output_path_instructions = "AGENTS.md"
output_path_config = ".aider.conf.yml"

# OpenAI Codex CLI agent and MCP config
[agents.codex]
enabled = true
output_path = "AGENTS.md"
output_path_config = ".codex/config.toml"

# Agent-specific MCP configuration for Codex CLI
[agents.codex.mcp]
enabled = true
merge_strategy = "merge"

[agents.firebase]
enabled = true
output_path = ".idx/airules.md"

[agents.gemini-cli]
enabled = true

[agents.jules]
enabled = true

[agents.junie]
enabled = true
output_path = ".junie/guidelines.md"

[agents.junie.mcp]
enabled = true
merge_strategy = "merge"

# Agent-specific MCP configuration
[agents.cursor.mcp]
enabled = true
merge_strategy = "merge"

# Disable specific agents
[agents.windsurf]
enabled = false

[agents.kilocode]
enabled = true
output_path = "AGENTS.md"

[agents.warp]
enabled = true
output_path = "WARP.md"

Configuration Precedence

1. CLI flags (e.g., --agents, --no-mcp, --mcp-overwrite, --no-gitignore)
2. Settings in ruler.toml (default_agents, specific agent settings, global sections)
3. Ruler's built-in defaults (all agents enabled, standard output paths, MCP enabled with 'merge')

MCP (Model Context Protocol) Server Configuration

MCP provides broader context to AI models through server configurations. Ruler can manage and distribute these settings across compatible agents.

TOML Configuration (Recommended)

You can now define MCP servers directly in ruler.toml using the [mcp_servers.<name>] syntax:

# Global MCP behavior
[mcp]
enabled = true
merge_strategy = "merge"  # or "overwrite"

# Local (stdio) server
[mcp_servers.filesystem]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/project"]

[mcp_servers.filesystem.env]
API_KEY = "your-api-key"

# Remote server
[mcp_servers.search]
url = "https://mcp.example.com"

[mcp_servers.search.headers]
Authorization = "Bearer your-token"
"X-API-Version" = "v1"

Agent-specific MCP servers can be defined under [agents.<agent>.mcp_servers.<name>]. They are applied only to that agent and override global servers with the same name:

[agents.cursor.mcp_servers.slack]
url = "https://mcp.slack.com/mcp"
auth = { CLIENT_ID = "CURSOR_ID" }

[agents.claude.mcp_servers.slack]
type = "http"
url = "https://mcp.slack.com/mcp"
oauth = { clientId = "CLAUDE_ID", callbackPort = 3118 }

Legacy .ruler/mcp.json (Deprecated)

For backward compatibility, you can still use the JSON format; a warning is issued encouraging migration to TOML. The file is no longer created during ruler init.

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/project"
      ]
    },
    "git": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-git", "--repository", "."]
    }
  }
}

Configuration Precedence

When both TOML and JSON configurations are present:

1. TOML servers take precedence over JSON servers with the same name
2. Servers are merged from both sources (unless using overwrite strategy)
3. Deprecation warning is shown encouraging migration to TOML (warning shown once per run)

Server Types

Local/stdio servers require a command field:

[mcp_servers.local_server]
command = "node"
args = ["server.js"]

[mcp_servers.local_server.env]
DEBUG = "1"

Remote servers require a url field (headers optional; bearer Authorization token auto-extracted for OpenHands when possible):

[mcp_servers.remote_server]
url = "https://api.example.com"

[mcp_servers.remote_server.headers]
Authorization = "Bearer token"

Ruler uses this configuration with the merge (default) or overwrite strategy, controlled by ruler.toml or CLI flags.

Home Directory Safety: Ruler never writes MCP configuration files outside your project root. Any historical references to user home directories (e.g. ~/.codeium/windsurf/mcp_config.json or ~/.zed/settings.json) have been removed; only project-local paths are targeted.

Note for OpenAI Codex CLI: To apply the local Codex CLI MCP configuration, set the CODEX_HOME environment variable to your project’s .codex directory:

export CODEX_HOME="$(pwd)/.codex"

Skills Support (Experimental)

⚠️ Experimental Feature: Skills support is currently experimental. Skills are only propagated to agents with native skills support; other agents are skipped with a warning.

Ruler can manage and propagate skills to supported AI agents. Skills are stored in .ruler/skills/ and are automatically distributed to compatible agents when you run ruler apply.

How It Works

Skills are specialized knowledge packages that extend AI agent capabilities with domain-specific expertise, workflows, or tool integrations. Ruler discovers skills in your .ruler/skills/ directory and propagates them to compatible agents:

• Agents with native skills support: Skills are copied directly to each agent's native skills directory:
  • Claude Code: .claude/skills/
  • GitHub Copilot: .claude/skills/ (shared with Claude Code)
  • Kilo Code: .claude/skills/ (shared with Claude Code)
  • OpenAI Codex CLI: .agents/skills/ (shared with Goose, Amp, and Zed)
  • OpenCode: .opencode/skills/
  • Pi Coding Agent: .pi/skills/
  • Goose: .agents/skills/
  • Amp: .agents/skills/ (shared with Goose)
  • Zed: .agents/skills/ (shared with Goose)
  • Antigravity: .agent/skills/
  • Factory Droid: .factory/skills/
  • Mistral Vibe: .vibe/skills/
  • Roo Code: .roo/skills/
  • Gemini CLI: .gemini/skills/
  • Junie: .junie/skills/
  • Cursor: .cursor/skills/
  • Windsurf: .windsurf/skills/
  • Kiro: .kiro/skills/

Skills Directory Structure

Skills can be organized flat or nested:

.ruler/skills/
├── my-skill/
│   ├── SKILL.md           # Required: skill instructions/knowledge
│   ├── helper.py          # Optional: additional resources (scripts)
│   └── reference.md       # Optional: additional resources (docs)
└── another-skill/
    └── SKILL.md

Each skill must contain:

• SKILL.md - Primary skill file with instructions or knowledge base

Skills can optionally include additional resources like:

• Markdown files with supplementary documentation
• Python, JavaScript, or other scripts
• Configuration files or data

Configuration

Skills support is enabled by default but can be controlled via:

CLI flags:

# Enable skills (default)
ruler apply --skills

# Disable skills
ruler apply --no-skills

Configuration in ruler.toml:

[skills]
enabled = true  # or false to disable

Non-native Agents

If you run Ruler for agents that do not support native skills, Ruler logs a warning and skips skills propagation for those agents.

.gitignore Integration

When skills support is enabled and gitignore integration is active, Ruler automatically adds:

• .claude/skills/ (for Claude Code, GitHub Copilot, and Kilo Code)
• .agents/skills/ (for OpenAI Codex CLI, Goose, Amp, and Zed)
• .opencode/skills/ (for OpenCode)
• .pi/skills/ (for Pi Coding Agent)
• .agent/skills/ (for Antigravity)
• .factory/skills/ (for Factory Droid)
• .vibe/skills/ (for Mistral Vibe)
• .roo/skills/ (for Roo Code)
• .gemini/skills/ (for Gemini CLI)
• .junie/skills/ (for Junie)
• .cursor/skills/ (for Cursor)
• .windsurf/skills/ (for Windsurf)
• .kiro/skills/ (for Kiro)

to your .gitignore file within the managed Ruler block.

Requirements

• For agents with native skills support (Claude Code, GitHub Copilot, Kilo Code, OpenAI Codex CLI, OpenCode, Pi Coding Agent, Goose, Amp, Zed, Antigravity, Factory Droid, Mistral Vibe, Roo Code, Gemini CLI, Junie, Cursor, Windsurf, Kiro): No additional requirements.

Validation

Ruler validates discovered skills and issues warnings for:

• Missing required file (SKILL.md)
• Invalid directory structures (directories without SKILL.md and no sub-skills)

Warnings don't prevent propagation but help identify potential issues.

Dry-Run Mode

Test skills propagation without making changes:

ruler apply --dry-run

This shows which skills would be copied.

Example Workflow

# 1. Add a skill to your project
mkdir -p .ruler/skills/my-skill
cat > .ruler/skills/my-skill/SKILL.md << 'EOF'
# My Custom Skill

This skill provides specialized knowledge for...

## Usage

When working on this project, always follow these guidelines:
- Use TypeScript for all new code
- Write tests for all features
- Follow the existing code style
EOF

# 2. Apply to all agents (skills enabled by default)
ruler apply

# 3. Skills are now available to compatible agents:
#    - Claude Code, GitHub Copilot & Kilo Code: .claude/skills/my-skill/
#    - OpenAI Codex CLI, Goose, Amp & Zed: .agents/skills/my-skill/
#    - OpenCode: .opencode/skills/my-skill/
#    - Pi Coding Agent: .pi/skills/my-skill/
#    - Antigravity: .agent/skills/my-skill/
#    - Factory Droid: .factory/skills/my-skill/
#    - Mistral Vibe: .vibe/skills/my-skill/
#    - Roo Code: .roo/skills/my-skill/
#    - Gemini CLI: .gemini/skills/my-skill/
#    - Junie: .junie/skills/my-skill/
#    - Cursor: .cursor/skills/my-skill/
#    - Windsurf: .windsurf/skills/my-skill/
#    - Kiro: .kiro/skills/my-skill/

Subagents Support (Experimental)

⚠️ Experimental: Subagents support is experimental and behavior may change in future releases.

Ruler can distribute named, delegatable subagents from a single source of truth (.ruler/agents/) to each agent's native subagent location. Each source file is one Markdown file with YAML frontmatter; Ruler transforms it into the format the target agent expects.

How It Works

For agents with a native subagent primitive, Ruler writes one file per subagent into the target directory:

Other agents (Windsurf, RooCode, Aider, Gemini CLI, …) do not yet have a comparable native subagent primitive and are skipped with a warning. Subagent propagation will be added when those agents ship a comparable file format.

Source Format

Author each subagent as .ruler/agents/<name>.md (nested folders are supported and preserved in outputs):

---
name: code-reviewer
description: Use PROACTIVELY after a feature/fix is implemented. Reviews against SOLID/DRY/KISS. Read-only.
tools: [Read, Grep, Glob, Bash]
model: inherit
readonly: true
is_background: false
---

# Code Reviewer

You operate in a fresh context window with read-only access. Your job is to
review the diff and surrounding code against the design principles and return
a structured verdict.

Required frontmatter fields:

Optional frontmatter fields:

For GitHub Copilot, source tools (Claude vocabulary: Read, Grep, Bash, …) are translated to Copilot's aliases (read, search, execute, …). Tools that do not have a Copilot equivalent are dropped silently on a normal apply; pass --verbose (or use --dry-run to preview) to see which tools were dropped.

Configuration

Subagent propagation is disabled by default. Opt in via CLI flag or ruler.toml:

ruler apply --subagents   # enable subagent propagation for one run

# .ruler/ruler.toml
[agents]
enabled = true
# include_in_rules = true  # also append .ruler/agents/*.md into top-level CLAUDE.md / AGENTS.md (default: false)
# cleanup_orphaned = true   # allow ruler to delete stale native subagent dirs (default: false)

Note: the previous release used [subagents] for these keys. [subagents] is still honored as a fallback with a deprecation warning, and will be removed in a future release. Please migrate to [agents].

[agents] enabled controls only native subagent propagation from .ruler/agents/. It is independent from [agents.<name>] enabled (which toggles per-coding-agent output like CLAUDE.md / AGENTS.md).

CLI flags take precedence over ruler.toml, which takes precedence over the default (disabled).

Validation

Source files are validated at discovery time:

• Files without YAML frontmatter are skipped with a warning.
• Files missing required name or description are skipped with a warning.
• Files where name does not match the filename stem are skipped with a warning.
• Unknown frontmatter keys are dropped (not errored).

Dry-Run Mode

Use --dry-run to preview which files would be written without touching disk.

.gitignore Integration

When subagents are enabled, the four target directories are added to the Ruler-managed block of .gitignore:

.claude/agents/
.cursor/agents/
.codex/agents/
.github/agents/

Use --no-gitignore to opt out.

Cleanup

Subagent propagation does not currently have explicit ruler revert support. By default, ruler apply is non-destructive and leaves existing native subagent directories untouched when subagents are disabled or missing. To allow automatic cleanup of stale generated directories, set [agents] cleanup_orphaned = true, then disable subagents ([agents] enabled = false or --no-subagents) and run ruler apply.

Example Workflow

# 1. Author a subagent in your project
mkdir -p .ruler/agents
cat > .ruler/agents/code-reviewer.md << 'EOF'
---
name: code-reviewer
description: Reviews changes against SOLID/DRY/KISS
tools: [Read, Grep, Glob]
readonly: true
---

You review code changes for quality.
EOF

# 2. Opt subagents in (default is disabled — see [agents] section above)
echo -e "\n[agents]\nenabled = true" >> .ruler/ruler.toml

# 3. Apply
ruler apply

# 4. The subagent is now available in each agent's native location:
#    - Claude Code:  .claude/agents/code-reviewer.md
#    - Cursor:       .cursor/agents/code-reviewer.md
#    - Codex CLI:    .codex/agents/code-reviewer.toml
#    - GitHub Copilot: .github/agents/code-reviewer.md

Limitations

• No explicit revert command. Optional cleanup is available via [agents] cleanup_orphaned = true and a subsequent apply.
• Atomic replace, not merge. Ruler regenerates each agent's subagent directory from the source on every apply. Manual edits to generated files will be overwritten.
• No support yet for agents without a native subagent primitive. Windsurf, RooCode, Aider, Gemini CLI, and others are skipped with a warning. Propagation will be added when those agents ship a comparable file format.

.gitignore Integration

Ruler automatically manages your .gitignore file to keep generated agent configuration files out of version control.

How it Works

• Creates or updates .gitignore in your project root
• Adds paths to a managed block marked with # START Ruler Generated Files and # END Ruler Generated Files
• Preserves existing content outside this block
• Sorts paths alphabetically and uses relative POSIX-style paths

Example .gitignore Section (sample - actual list depends on enabled agents)

# Your existing rules
node_modules/
*.log

# START Ruler Generated Files
.aider.conf.yml
.clinerules
AGENTS.md
CLAUDE.md
# END Ruler Generated Files

dist/

Control Options

• CLI flags: --gitignore, --no-gitignore, --gitignore-local, --no-gitignore-local
• Configuration: [gitignore].enabled and [gitignore].local in ruler.toml
• Default: enabled

Backup Control

• CLI flags: --backup, --no-backup
• Configuration: [backup].enabled in ruler.toml
• Default: enabled

Practical Usage Scenarios

Scenario 1: Getting Started Quickly

# Initialize Ruler in your project
cd your-project
ruler init

# Edit the generated files
# - Add your coding guidelines to .ruler/AGENTS.md (or keep adding additional .md files)
# - Customize .ruler/ruler.toml if needed

# Apply rules to all AI agents
ruler apply

Scenario 2: Working with worktrees

When using the default git worktree add command (which is also run by agent apps such as Claude Code or Codex through the interface), the gitignored files are not copied over. You will need to ask your agent to run ruler apply at the start of every session.

As an alternative you can commit your default agents files to source control.

# .ruler/ruler.toml
default_agents = ["claude", "codex"]

[gitignore]
enabled = false

# Do not ignore AGENTS.md and CLAUDE.md
/.claude/*
!/.claude/skills/
/.codex/*
!/.codex/skills/
/.cursor
/AGENTS.md.bak
/CLAUDE.md.bak

To avoid having other contributors commit instructions outside of .ruler you can setup a github action to check there is no diff when running ruler apply in CI.

# .github/workflows/ruler-check.yml

# Verifies the committed agent files (AGENTS.md, CLAUDE.md, skills) match the .ruler/ source.
# They are committed so a fresh clone/worktree has guidance immediately; this guards against drift.
name: Ruler guidance in sync

on:
  pull_request:
  push:
    branches:
      - main
      - 'build/**'

permissions:
  contents: read

env:
  CI_NODE_VERSION: 24.15.0

jobs:
  ruler-check:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v6

      - uses: pnpm/action-setup@v5
      - name: Setup Node
        uses: actions/setup-node@v6
        with:
          node-version: ${{ env.CI_NODE_VERSION }}
          cache: 'pnpm'

      - name: Verify committed agent files match .ruler/
        run: |
          pnpm dlx @intellectronica/ruler apply --no-gitignore --no-mcp
          DRIFT="$(git status --porcelain -- AGENTS.md CLAUDE.md .claude/skills .codex/skills)"
          if [ -n "$DRIFT" ]; then
            echo "::error::Committed agent files are out of sync with .ruler/. Run 'pnpm dlx @intellectronica/ruler apply --no-gitignore --no-mcp' and commit the result."
            echo "$DRIFT"
            git --no-pager diff -- AGENTS.md CLAUDE.md .claude/skills .codex/skills
            exit 1
          fi
          echo "Agent files are in sync with .ruler/."

Scenario 3: Complex Projects with Nested Rules

For large projects with multiple components or services, enable nested rule loading so each directory keeps its own rules and MCP bundle:

# Set up nested .ruler directories
mkdir -p src/.ruler tests/.ruler docs/.ruler

# Add component-specific instructions
echo "# API Design Guidelines" > src/.ruler/api_rules.md
echo "# Testing Best Practices" > tests/.ruler/test_rules.md
echo "# Documentation Standards" > docs/.ruler/docs_rules.md

# .ruler/ruler.toml
nested = true

# The CLI inherits nested mode from ruler.toml
ruler apply --verbose

# Override from the CLI at any time
ruler apply --no-nested

This creates context-specific instructions for different parts of your project while maintaining global rules in the root .ruler/ directory. Nested runs automatically keep every nested config enabled even if a child tries to disable it.

[!NOTE] The CLI prints "Nested mode is experimental and may change in future releases." the first time nested processing runs. Expect refinements in future versions.

Scenario 4: Team Standardization

1. Create .ruler/coding_standards.md, .ruler/api_usage.md
2. Commit the .ruler directory to your repository
3. Team members pull changes and run ruler apply to update their local AI agent configurations

Scenario 5: Project-Specific Context for AI

1. Detail your project's architecture in .ruler/project_overview.md
2. Describe primary data structures in .ruler/data_models.md
3. Run ruler apply to help AI tools provide more relevant suggestions

Integration with NPM Scripts

{
  "scripts": {
    "ruler:apply": "ruler apply",
    "dev": "npm run ruler:apply && your_dev_command",
    "precommit": "npm run ruler:apply"
  }
}

Integration with GitHub Actions

# .github/workflows/ruler-check.yml
name: Check Ruler Configuration
on:
  pull_request:
    paths: ['.ruler/**']

jobs:
  check-ruler:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'

      - name: Install Ruler
        run: npm install -g @intellectronica/ruler

      - name: Apply Ruler configuration
        run: ruler apply --no-gitignore

      - name: Check for uncommitted changes
        run: |
          if [[ -n $(git status --porcelain) ]]; then
            echo "::error::Ruler configuration is out of sync!"
            echo "Please run 'ruler apply' locally and commit the changes."
            exit 1
          fi

Troubleshooting

Common Issues

"Cannot find module" errors:

• Ensure Ruler is installed globally: npm install -g @intellectronica/ruler
• Or use npx @intellectronica/ruler

Permission denied errors:

• On Unix systems, you may need sudo for global installation

Agent files not updating:

• Check if the agent is enabled in ruler.toml
• Verify agent isn't excluded by --agents flag
• Use --verbose to see detailed execution logs

Configuration validation errors:

• Ruler now validates ruler.toml format and will show specific error details
• Check that all configuration values match the expected types and formats

Debug Mode

Use --verbose flag to see detailed execution logs:

ruler apply --verbose

This shows:

• Configuration loading details
• Agent selection logic
• File processing information
• MCP configuration steps

FAQ

Q: Can I use different rules for different agents? A: Currently, all agents receive the same concatenated rules. For agent-specific instructions, include sections in your rule files like "## GitHub Copilot Specific" or "## Aider Configuration".

Q: How do I set up different instructions for different parts of my project? A: Enable nested mode either by setting nested = true in ruler.toml or by passing ruler apply --nested. The CLI inherits the config setting by default, but --no-nested always wins if you need to opt out for a run. Nested mode keeps loading rules (and MCP settings) from every .ruler/ directory in the hierarchy, forces child configs to remain nested, and logs "Nested mode is experimental and may change in future releases." if any nested processing occurs.

Q: How do I temporarily disable Ruler for an agent? A: Set enabled = false in ruler.toml under [agents.agentname], or use --agents flag to specify only the agents you want.

Q: What happens to my existing agent configuration files? A: Ruler creates backups with .bak extension before overwriting any existing files.

Q: Can I run Ruler in CI/CD pipelines? A: Yes! Use ruler apply --no-gitignore in CI to avoid modifying .gitignore. See the GitHub Actions example above.

Q: How do I migrate from older versions using instructions.md? A: Simply rename .ruler/instructions.md to .ruler/AGENTS.md (recommended). If you keep the legacy file and omit AGENTS.md, Ruler will still use it (without emitting the old deprecation warning). Having both causes AGENTS.md to take precedence; the legacy file is still concatenated afterward.

Q: How does OpenHands MCP propagation classify servers? A: Local stdio servers become stdio_servers. Remote URLs containing /sse are classified as sse_servers; others become shttp_servers. Bearer tokens in an Authorization header are extracted into api_key where possible.

Q: Where is Zed configuration written now? A: Ruler writes .zed/settings.json inside the project root (not the user home dir) and transforms MCP server definitions to Zed's context_servers format including source: "custom".

Q: What changed about MCP initialization? A: ruler init now only adds example MCP server sections to ruler.toml instead of creating .ruler/mcp.json. The JSON file is still consumed if present, but TOML servers win on name conflicts.

Q: Is Kiro supported? A: Yes. Kiro receives concatenated rules at .kiro/steering/ruler_kiro_instructions.md, MCP servers at .kiro/settings/mcp.json, and skills at .kiro/skills/.

Development

Setup

git clone https://github.com/intellectronica/ruler.git
cd ruler
npm install
npm run build

Testing

# Run all tests
npm test

# Run tests with coverage
npm run test:coverage

# Run tests in watch mode
npm run test:watch

Code Quality

# Run linting
npm run lint

# Run formatting
npm run format

Contributing

Contributions are welcome! Please:

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests for new functionality
5. Ensure all tests pass
6. Submit a pull request

For bugs and feature requests, please open an issue.

License

MIT

---

© Eleanor Berger
ai.intellectronica.net