Skill Detail

Synchronize AI coding rules across agent tools with Rulesync

Use Rulesync to maintain one set of AI coding rules and generate the right configuration files for Claude Code, Cursor, Gemini CLI, and other development agents.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Security Reviewed
⭐ 1.2k GitHub stars ⬇ 748.2k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill synchronize-ai-coding-rules-across-agent-tools-with-rulesync Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Node.js/npm or Homebrew, Rulesync CLI, target AI coding tools
Install & setup
Install with npm install -g rulesync or brew install rulesync, run rulesync init, optionally fetch official skills with rulesync fetch dyoshikawa/rulesync --features skills, then generate target configs with rulesync generate --targets "*" --features "*".
Author
dyoshikawa
Publisher
Individual
Last updated
Jul 8, 2026
Quick brief

Use Rulesync when a team wants a single source of truth for AI coding instructions and needs those rules exported into each agent tool’s expected config format. An operator can initialize rule files, import existing Claude Code or other tool instructions, fetch official skills, and generate target-specific configs during setup or CI. The boundary is AI-agent rule synchronization across development tools, not general dotfile management or a generic CLI listing.

How it works

What this skill actually does

Inputs and prerequisites: Node.js/npm or Homebrew, Rulesync CLI, target AI coding tools.

Setup notes: Install with npm install -g rulesync or brew install rulesync , run rulesync init , optionally fetch official skills with rulesync fetch dyoshikawa/rulesync –features skills , then generate target configs with rulesync generate –targets “*” –features “*” .

Source and verification boundary: use https://dyoshikawa.github.io/rulesync/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.