agentleFS
Sign inStart free
equinorequinor/fusion-skills/skills/fusion-rules/SKILL.md

fusion-rules

Skill2 starsChanged 2 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When targeting multiple editors:

    line 57
  2. Distinctive:

    Run first agent's scan and interview (Steps 1–3) in full

    line 59
  3. Distinctive:

    Write CI checks for rule validation — out of scope

    line 68
  4. Distinctive:

    No secrets or credentials in rule files

    line 73
  5. Distinctive:

    No overwrites without showing diff and getting approval

    line 74
  6. Distinctive:

    No invented conventions — only document what the developer confirms

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free