SkillFoxx

Rulesync CLI

A CLI that keeps rules, commands, MCP, subagents and skills in one source and generates config files for many AI coding tools

  • 1,600 ★ on the repository
  • Last commit
  • MIT
CLI

Extended access

Why this level

  • Reads and writes configuration files in the project directory
All reasons and checks

dyoshikawa/rulesyncAuthor:dyoshikawa

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add cli/rulesync

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Reads and writes configuration files in the project directory

This is third-party code. Review the repository files before installing.

What it does

Rulesync keeps your project's AI agent rules and settings in one .rulesync directory and generates ready config files for each tool. Besides rules it emits commands, MCP servers, subagents, skills, hooks, permissions and ignore files, and you can pick which targets and which features to build. The import command pulls existing settings such as CLAUDE.md, .cursorrules or copilot-instructions into the shared source. The convert command moves a config from one tool to another without adopting the .rulesync workflow. It supports a long list of editors and CLIs, from Claude Code and Cursor to Codex, Copilot, Cline, OpenCode and more.

Who it is for. For developers and teams who use several AI coding agents at once and want their settings in one place.

Good fit when

  • The team uses several AI agents and needs one rule instead of copies per tool
  • You need to bring an existing CLAUDE.md or .cursorrules into a shared source
  • You need a one-off conversion of one agent's config into another's format

Not a fit when

  • You use only one agent and its native config is enough
  • You need the agent itself, not a way to sync its settings

Example request

Generate Claude Code and Cursor configs from my .rulesync directory

Limitations

Rulesync only generates and converts configuration files; it does not replace the agents themselves. It needs Node.js to install via npm. Some targets are marked deprecated or frozen because the source tools shut down, and the set of supported formats changes between versions.

How to disable. Remove the package with npm uninstall -g rulesync. Generated config files stay in the project; delete them by hand if you no longer need them.

FAQ

Do I have to adopt the .rulesync directory?

No. The convert command moves a config from one tool to another directly, without writing .rulesync files.

How do I install without npm?

There is a Homebrew tap for macOS and Linux and a single-binary install script; the links and commands are in the README.

Discussion

No questions or reviews yet.

CLI tools

One rules directory generates instructions, skills, MCP and settings for 52 AI coding assistants and checks them in CI

CLIExtended access169

A CLI that keeps agent instructions in one place and distributes them to the right config files for Claude Code, Cursor, Codex, Copilot and two dozen other tool

CLIExtended access3K

Skill that generates matching project rules for Cursor, Claude Code and Codex built around layered development and BDD

SkillExtended access2
Russian stack

Rules, subagents, skills and MCP integrations for 1C:Enterprise 8 development with Cursor, Claude Code, Codex and other agents

PluginBroad access539

A CLI that analyses a repository in six model phases and writes AGENTS.md or CLAUDE.md, with ExecPlan planning on top.

CLIExtended access124

README in short

The README presents Rulesync as a Node.js CLI that generates config files for various AI development tools from unified rule files. It covers install via npm, Homebrew and a binary, a quick start with init, fetch and generate, plus the import and convert commands. A large table shows which features (rules, ignore, MCP, commands, subagents, skills, hooks, permissions, checks) are supported per tool. Deprecated and frozen targets are listed separately with reasons. Full documentation lives on a dedicated site; the license is MIT.

README badge

Report a problem