Login
equinor/fusion-skillsMIT5 files

Fusion Rules

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.

Use this skillView repositoryView on skills.sh
Specification
Skill ID
equinor/fusion-skills/fusion-rules
Publisher
equinor
Repository
fusion-skills
Installs
0
Files
5
License
MIT
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

equinor/fusion-skills/fusion-rulesInstalls these files
  • CHANGELOG.md
  • SKILL.md
  • agents/claude-code.agent.md
  • agents/copilot.agent.md
  • agents/cursor.agent.md

What this skill tells the agent

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

More from equinor

equinor/fusion-skills

Fusion

Main Copilot skill gate for the Fusion ecosystem — cross-domain router. USE FOR: routing between different Fusion domains (skills, issues, PRs, reviews) when the right domain skill is unclear; getting install guidance for missing skills. DO NOT USE FOR: skill lifecycle operations (use fusion-skills directly), tasks where a specific Fusion skill is already active.

equinor/fusion-skills

Fusion Backend Dev

Guides consumption and understanding of Fusion backend services, APIs, and patterns for frontend/client developers, integrators, and architects. Shows reference implementations, explains architectural decisions, and clarifies contracts. USE FOR: understanding Fusion backend APIs, learning implementation patterns, exploring reference code, choosing the right integration point, and understanding authorization/validation/async patterns. DO NOT USE FOR: modifying backend services, creating new endpoints, database changes, or backend-specific development (use the fusion-services-developer agent or the target backend service repo instead).

equinor/fusion-skills

Fusion Code Conventions

Applies and explains code conventions across TypeScript, React, C#, and Markdown. Enforces naming rules, file naming patterns, TSDoc and XML doc standards, inline comment intent (the *why*, not the *what*), code structure, error handling, async patterns, and dead code policy. Also enforces ADR and contributor doc decisions, and flags decisions that appear stale or misaligned with current tooling. USE FOR: convention questions, code review against project standards, applying naming rules, auditing intent comments, checking TSDoc completeness, enforcing recorded ADR decisions, and flagging stale architectural decisions. DO NOT USE FOR: security vulnerability scanning, performance profiling, runtime debugging, or generating net-new code without a review target.

Use this skill in a project

Open any RiverX project, search the Skills panel for equinor/fusion-skills/fusion-rules, and install it in one click.

Use this skill