mcpField
F
fusion-rules

fusion-rules

github.com/equinorAgent workflows1.1k installs
Repository

About fusion-rules

fusion-rules routes AI coding-assistant rule tasks to the agent for Copilot, Cursor, or Claude Code. It supports authoring and reviewing rules, and requires approval before writing files.

Key features

  1. 01Detects editor intent and routes
  2. 02Authors or improves editor rules
  3. 03Coordinates rules across editors
  4. 04Requires approval before file writes
  5. 05Avoids inventing project conventions

Use cases

  1. 01Setting up rules for a Cursor project
  2. 02Updating Claude Code rule files
  3. 03Creating rules for a mixed-editor team

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/equinor/fusion-skills --skill fusion-rules

After installing, type/fusion-rulesin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

CHANGELOG.md
agents/
claude-code.agent.md
copilot.agent.md
cursor.agent.md

Details

From the project README

Fusion Rules

Gateway for AI coding assistant rule authoring. Detects the target editor and routes to the right agent.

Routing

IntentAgent
Set up GitHub Copilot instructions / rulesagents/copilot.agent.md
Set up Cursor project rulesagents/cursor.agent.md
Set up Claude Code rules / CLAUDE.mdagents/claude-code.agent.md
Set up rules for all editors / mixed teamRun all three agents sequentially
Review or improve existing rulesRoute to the agent matching the file format

Intent detection

Detect target editor from the request:

  • Copilot — "copilot", "copilot-instructions", ".github/instructions", "applyTo"
  • Cursor — "cursor", ".cursor/rules", "mdc", "alwaysApply", "globs"
  • Claude Code — "claude", "CLAUDE.md", ".claude/rules", "paths"
  • All / unknown — "rules", "instructions", "set up AI rules", or no editor specified

Route directly on detected intent. No editor specified → run all three agents.

Loading behavior

Load ONLY the routed agent file. Each agent carries the full workflow and references .system/fusion-rule-author/ assets and templates on demand. Don't preload all agents.

Multi-editor workflow

When targeting multiple editors:

  1. Run first agent's scan and interview (Steps 1–3) in full
  2. Pass scan summary + interview answers as context to remaining agents — they skip Steps 1–3 and start at Step 4 (Classify)
  3. Each agent drafts, reviews, and writes files for its own editor format
  4. Generate parallel files with equivalent content — no duplication within a single editor

What this skill does NOT do

  • Author skills (SKILL.md) — use fusion-skill-authoring
  • Author agent definitions (.agent.md) — separate concern
  • Write CI checks for rule validation — out of scope
  • Migrate entire legacy codebases — incremental adoption only

Safety

  • No secrets or credentials in rule files
  • No overwrites without showing diff and getting approval
  • No invented conventions — only document what the developer confirms
  • Show drafts before writing any files

Comments

Markdown supported