Fusion Rules

by equinore8fd6cfaf8edMIT2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Entrypoint for AI coding assistant rule authoring across GitHub Copilot, Cursor, and Claude Code. USE FOR: setting up rules, reviewing existing rules, scaffolding instruction files, or asking which editor format to use. DO NOT USE FOR: authoring skills (SKILL.md), agent definitions (.agent.md), or CI enforcement of rule files.

Instructions onlyAI & Agents
AI-generated overview

Routes requests for authoring AI coding assistant rule files to the right editor-specific agent.

What it does
This skill acts as an entrypoint for authoring rule and instruction files for AI coding assistants. It detects the target editor from the request and routes to the matching agent file for GitHub Copilot, Cursor, or Claude Code, or runs all three sequentially when no editor is specified. It also handles reviewing or improving existing rule files by routing to the agent matching the file format. It explicitly does not author skills, agent definitions, or CI validation checks.
When to use it
Use it when setting up rules or instruction files for Copilot, Cursor, or Claude Code, reviewing existing rules, scaffolding instruction files, or deciding which editor format to use. It is intended for mixed teams that need equivalent rule files across multiple editors.
Requirements
Instructions only; no scripts are shipped. It relies on the bundled agent files (agents/copilot.agent.md, agents/cursor.agent.md, agents/claude-code.agent.md) and references .system/fusion-rule-author/ assets and templates on demand. No credentials or network access are stated.

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

Source and attribution

Source:equinor/fusion-skillsinskills/fusion-rulesat commite8fd6cf

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal