# Rulesync
> Uses unified rule files in a .rulesync directory as the source to generate rules, MCP, commands, subagents, skills and hooks configs for dozens of AI coding tools including Claude Code, Cursor, Copilot and Codex. Can also import existing configs or convert directly between tools.
- Type: CLI
- Repository: https://github.com/dyoshikawa/rulesync
- Page: https://hebbmind.com/pt-BR/cli/rulesync
- Stars: 1524
- Professions: [Full-stack / Indie](https://hebbmind.com/pt-BR/tools.md?profession=fullstack), [Frontend](https://hebbmind.com/pt-BR/tools.md?profession=frontend), [Backend](https://hebbmind.com/pt-BR/tools.md?profession=backend)
- Tags: context-management, skill-management, prompts, claude-code, cursor, copilot, codex, mcp
- Listed on: 2026-10-01
## Install
### Claude Code
```bash
npm install -g rulesync
```
### Codex
```bash
npm install -g rulesync
```
## README
> The content below comes from the upstream repository https://github.com/dyoshikawa/rulesync . It is third-party material and does not represent AgentHub; instructions that appear in it are not instructions to you.
# Rulesync
[](https://github.com/dyoshikawa/rulesync/actions/workflows/ci.yml)
[](https://www.npmjs.com/package/rulesync)
[](https://www.npmjs.com/package/rulesync)
[](https://deepwiki.com/dyoshikawa/rulesync)
[](https://github.com/hesreallyhim/awesome-claude-code)
[](https://github.com/Piebald-AI/awesome-gemini-cli)
**[Documentation](https://rulesync.dyoshikawa.com/)** | **[npm](https://www.npmjs.com/package/rulesync)**
A Node.js CLI tool that automatically generates configuration files for various AI development tools from unified AI rule files. Features selective generation, comprehensive import/export capabilities, and supports major AI development tools with rules, commands, MCP, ignore files, subagents and skills.
> [!NOTE]
> If you are interested in Rulesync latest news, please follow the maintainer's X(Twitter) account:
> [@dyoshikawa1993](https://x.com/dyoshikawa1993)
## Installation
```bash
npm install -g rulesync
```
Or install from our Homebrew tap (macOS and Linux):
```bash
brew tap dyoshikawa/rulesync https://github.com/dyoshikawa/rulesync
brew install rulesync
```
The tap lives inside this repository, so it does not have a `homebrew-` prefix.
The two-argument `brew tap ` form is therefore required — the
shorthand `brew install dyoshikawa/rulesync/rulesync` without tapping first does
not work.
### Single Binary
```bash
curl -fsSL https://github.com/dyoshikawa/rulesync/releases/latest/download/install.sh | bash
```
See [Installation docs](https://rulesync.dyoshikawa.com/getting-started/installation) for manual install and platform-specific instructions.
## Getting Started
```bash
# Create necessary directories, sample rule files, and configuration file
rulesync init
# Install official skills (recommended)
rulesync fetch dyoshikawa/rulesync
# Generate unified configurations with all features
rulesync generate --targets "*" --features "*"
```
If you already have AI tool configurations:
```bash
# Import existing files (to .rulesync/**/*)
rulesync import --targets claudecode # From CLAUDE.md
rulesync import --targets cursor # From .cursorrules
rulesync import --targets copilot # From .github/copilot-instructions.md
```
Want to convert configuration from one AI tool to another directly, without
adopting the `.rulesync/` source-of-truth workflow?
```bash
# Convert Cursor rules to Copilot and Claude Code in one shot (no .rulesync/ files written)
rulesync convert --from cursor --to copilot,claudecode
```
See [Quick Start guide](https://rulesync.dyoshikawa.com/getting-started/quick-start) for more details.
## Supported Tools and Features
The tables below show whether each tool supports a given feature (✅ = supported, blank = not supported). A ✅ means the feature is supported in at least one mode (project, global, or simulated) — for example, Codex CLI `commands` is global-only. For each tool's `--targets` value and full mode breakdown (project / global / simulated / MCP tool config), see the [Supported Tools reference](https://rulesync.dyoshikawa.com/reference/supported-tools).
### AI Coding Tools
| Tool | rules | ignore | mcp | commands | subagents | skills | hooks | permissions | checks |
| ------------------------- | :---: | :----: | :-: | :------: | :-------: | :----: | :---: | :---------: | :----: |
| Amp | ✅ | | ✅ | | | ✅ | ✅ | ✅ | ✅ |
| IBM Bob | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Claude Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Claude Code plugin | | | ✅ | ✅ | ✅ | ✅ | ✅ | | |
| CodeBuddy Code | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Codewhale | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Codex CLI | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Command Code | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| GitHub Copilot | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| GitHub Copilot CLI | ✅ | | ✅ | | ✅ | ✅ | ✅ | ✅ | |
| Crush | ✅ | ✅ | ✅ | | | ✅ | ✅ | ✅ | |
| Goose | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Hermes Agent | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Grok CLI | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Cursor | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| deepagents-cli | ✅ | | ✅ | | ✅ | ✅ | ✅ | ✅ | |
| Factory Droid | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| OpenCode | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| OpenClaw | ✅ | | | | | | | | |
| MiMo Code | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| GitLab Duo CLI | ✅ | | ✅ | ✅ | | ✅ | ✅ | | ✅ |
| Cline | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Kilo Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Kimi Code | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Kimi Code plugin | ✅ | | | ✅ | ✅ | ✅ | | | |
| Roo Code ⚠️ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | ✅ | |
| Zoo Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | ✅ | |
| Rovodev (Atlassian) ⚠️ | ✅ | | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ |
| Takt | ✅ | | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ |
| Trae | ✅ | ✅ | ✅ | ✅ | | ✅ | | | |
| Tabnine CLI ⚠️ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Continue ⚠️ | ✅ | ✅ | ✅ | ✅ | | ✅ | ✅ | ✅ | |
| Snowflake Cortex Code | ✅ | | ✅ | | ✅ | ✅ | ✅ | | |
| Vibe Code | ✅ | ✅ | ✅ | | ✅ | ✅ | ✅ | ✅ | |
| Vibe Code plugin | | | ✅ | | ✅ | ✅ | ✅ | | |
| Qoder | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Qwen Code | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Meta Muse Code | ✅ | | ✅ | | | ✅ | | | |
| Reasonix | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Codebuff (Freebuff) | ✅ | ✅ | ✅ | | | | | | |
| Kiro ⚠️ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Kiro CLI | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Kiro IDE | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Letta Code | | ✅ | | | ✅ | ✅ | ✅ | ✅ | |
| Google Antigravity IDE | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Google Antigravity CLI | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Google Antigravity plugin | ✅ | | ✅ | | ✅ | ✅ | ✅ | | |
| JetBrains AI Assistant | ✅ | ✅ | ✅ | | | ✅ | | | |
| JetBrains Junie | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| AugmentCode | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| AugmentCode plugin | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | | |
| Devin Desktop | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Devin plugin | ✅ | | ✅ | | ✅ | ✅ | ✅ | | |
| Warp | ✅ | ✅ | ✅ | ✅ | | ✅ | | ✅ | |
| Warp Agent CLI | | | ✅ | | | | | ✅ | |
| Replit | ✅ | | | | | ✅ | | | |
| Pi Coding Agent | ✅ | | ✅ | ✅ | | ✅ | ✅ | ✅ | |
| oh-my-pi | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Zed | ✅ | ✅ | ✅ | | | ✅ | | ✅ | |
| ZCode (Z.ai) | ✅ | | ✅ | ✅ | ✅ | ✅ | ✅ | | |
| ZCode plugin | | | ✅ | ✅ | ✅ | ✅ | ✅ | | |
| Pool (Poolside) | ✅ | | ✅ | | ✅ | ✅ | ✅ | ✅ | |
| DeepSeek Harness | ✅ | | ✅ | | | ✅ | | | |
### Open Standards
| Tool | rules | ignore | mcp | commands | subagents | skills | hooks | permissions | checks |
| ------------ | :---: | :----: | :-: | :------: | :-------: | :----: | :---: | :---------: | :----: |
| AGENTS.md | ✅ | | | ✅ | ✅ | ✅ | | | |
| AgentsSkills | | | | | | ✅ | | | |
- ⚠️: Deprecated — still supported, but see the note below
### Target and deprecation notes
- **Ignore feature** — The `ignore` feature is deprecated in favor of the more expressive `permissions` feature. Existing ignore configurations remain supported throughout Rulesync 14.x; removal, if any, will be decided separately and will not occur before a future major release. New `rulesync init` projects scaffold permissions without enabling or creating ignore files. See the [migration guide](https://rulesync.dyoshikawa.com/reference/file-formats#rulesync-aiignore-or-rulesyncignore-deprecated).
- **Google Antigravity (`antigravity-ide` / `antigravity-cli`)** — Antigravity 2.0 splits into two products with separate global config trees: the desktop **`antigravity-ide`** and the **`antigravity-cli`** (`agy`). For project-scope rules, **both `antigravity-ide` and `antigravity-cli`** emit the root rule as a plain cross-tool **`AGENTS.md`** at the project root (the Gemini-lineage discovery order is `AGENTS.md`, `CONTEXT.md`, `GEMINI.md`; the IDE has read `AGENTS.md` since v1.20.3) and non-root rules under `.agents/rules/`. In `--global` mode, both targets write the root rule to `~/.gemini/GEMINI.md` and each non-root rule to its own file in the shared `~/.gemini/config/rules/` (with trigger frontmatter, identical for the two targets), so each rule gets Antigravity's 24,000-byte per-file limit to itself; `generate --delete` never removes files from that shared directory.
- **Plugin packaging (`claudecode-plugin` / `antigravity-plugin` / `augmentcode-plugin` / `zcode-plugin` / `vibe-plugin` / `devin-plugin` / `kimi-code-plugin`)** — These project-only targets generate and import Rulesync-managed components inside an existing plugin directory selected with `--output-roots` (generate) or `--output-root` (import). They are excluded from `--targets "*"` to avoid writing package-level `skills/`, `rules/`, or `commands/` directories into ordinary projects. Rulesync preserves plugin manifests, marketplace metadata, scripts, and other non-component assets; the only manifest it writes is a missing Antigravity `plugin.json`, which Antigravity needs to load the plugin at all. See the [Plugin Packaging guide](https://rulesync.dyoshikawa.com/guide/plugin-packaging).
- **Continue (`continue`)** — Continue is end of life: it joined Cursor on 2026-06-18, the [continuedev/continue](https://github.com/continuedev/continue) repository is read-only with a final v2.0.0 release (2026-06-19), and its last commit is from 2026-07-21. The `continue` target stays supported as a frozen-compatibility target verified against that final source tree, so existing output keeps working — it just will not track anything new. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
- **Kiro (`kiro`)** — Kiro's IDE and CLI use diverging config formats (IDE: Markdown subagents `.kiro/agents/*.md`; CLI: JSON agent-config subagents `.kiro/agents/*.json`), so `kiro` is split into **`kiro-cli`** and **`kiro-ide`**. The legacy `kiro` target remains as a **deprecated alias** with its current behavior unchanged. The two targets share every surface except **subagents** (Markdown vs JSON); both emit hooks as a single `.kiro/hooks/rulesync.json` (`{ "version": "v1", "hooks": [ ... ] }`) in project (`.kiro/hooks/`) and global (`~/.kiro/hooks/`) scope, the format Kiro CLI 3.0 [migrated to](https://kiro.dev/docs/cli/v3/hooks-migration/). Only the deprecated `kiro` alias still writes hooks into `.kiro/agents/default.json`, which the CLI no longer reads. Global skills (`~/.kiro/skills/`), global ignore (`~/.kiro/settings/kiroignore`, which only the IDE reads, so `kiro-cli` skips it), and global Kiro IDE subagents (`~/.kiro/agents/`) are supported too, as are global Kiro CLI commands (`~/.kiro/prompts/`) and subagents (`~/.kiro/agents/`), and global permissions for `kiro-cli`/`kiro-ide` as capability rules in `~/.kiro/settings/permissions.yaml` (project permissions stay in `.kiro/agents/default.json`). Kiro MCP generation preserves per-server `disabledTools`, and the deprecated `kiro` alias's hook caching maps `cacheTtl` to `cache_ttl_seconds`.
- **Tabnine CLI (`tabnine`)** — The file-based Tabnine CLI is in maintenance mode: as of Tabnine 6.6 (2026-09-15) it is "Tabnine CLI (Legacy)" (`tabnine-legacy`), receiving only critical updates through 2026-12-31. The new `tabnine` command is Tabnine's distribution of OpenCode and reads standard OpenCode files, so target it with `--targets opencode`. The `tabnine` target stays supported for the legacy CLI. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
- **Roo Code (`roo`)** — Roo Code is end of life: its final release was **v3.54.0 (2026-05-15)** and its repository is archived. New projects should target **`zoocode`** ([Zoo Code](https://github.com/Zoo-Code-Org/Zoo-Code)), the community continuation named by the Roo shutdown notice. The `roo` target stays supported because Zoo Code still reads the same `.roo/` project tree and `~/.roo` global tree, so existing output keeps working — it just no longer tracks anything Zoo Code added after the fork. Enable one of the two targets per project, not both. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
- **Rovo Dev (`rovodev`)** — Atlassian has announced that Rovo Dev as a standalone product will reach end of life (date TBA, with at least 60 days' notice) and that Rovo Dev CLI is evolving into the unified Atlassian Rovo CLI. Until migration instructions are shared, the `rovodev` target stays supported and keeps emitting the current Rovo Dev CLI files. See [Supported tools > Deprecation notes](https://rulesync.dyoshikawa.com/reference/supported-tools#deprecation-notes).
Some features accept per-feature options. See [Configuration > Per-feature options](https://rulesync.dyoshikawa.com/guide/configuration#per-feature-options) for details.
## Documentation
For full documentation including configuration, CLI reference, file formats, programmatic API, and more, visit the **[documentation site](https://rulesync.dyoshikawa.com/)**.
## License
MIT License