rulesync

Rulesync is a Node.js CLI tool that automatically generates configuration files for various AI development tools from unified AI rule files. It can import existing rule formats, fetch official skills, and generate unified configurations with support for multiple tools and features, including MCP configurations. You can create necessary directories, sample rule files, and a rulesync configuration with rulesync init, then pull official skills with rulesync fetch and generate your MCP-ready configurations with rulesync generate. The tool supports a broad set of targets such as Claude Code, Copilot, Cursor, Gemini CLI, Codex CLI, and many others, with options for including rules, ignore lists, subagents, skills, and hooks. This enables you to produce per-tool MCP blocks that your MCP runner can consume, along with the appropriate commands and tool-specific options.

Prerequisites:

• Node.js (LTS version) and npm installed on your system
• Sufficient permissions to install global npm packages

Installation steps:

1. Install Rulesync globally via npm: npm install -g rulesync

2. (Optional, macOS) If you prefer Homebrew: brew install rulesync

3. Verify installation: rulesync --version

4. (Optional) Install the latest experimental single-binary setup (for advanced users): curl -fsSL https://github.com/dyoshikawa/rulesync/releases/latest/download/install.sh | bash

5. Follow the Quick Start to initialize your project: rulesync init

For manual install and platform-specific instructions, see the documentation at the Rulesync site.

Tips and known considerations:

• Rulesync can generate MCP configurations across multiple tools. Review the generated MCP blocks to ensure they align with your environment and tool versions.
• Use rulesync fetch to pull official skills and rulesets before generating MCP configurations to maximize tool compatibility.
• If you maintain existing tool configurations, you can import them with rulesync import to consolidate into .rulesync/**/* within your project.
• Ensure proper permissions for the directory where rulesync stores generated configurations, especially when running in CI environments.
• The mcp_config above uses a placeholder path for the server entry point; replace path/to/server.js with the actual entry point if you run a local MCP server for Rulesync integration.