Fusion Rules
- 873 installs
- 1 repo stars
- Updated August 4, 2026
- equinor/fusion-skills
fusion-rules is a skill-development orchestrator at version 0.1.1 that sets up, reviews, and scaffolds AI coding assistant rule files across GitHub Copilot, Cursor, and Claude Code for developers standardizing editor ins
About
fusion-rules is an Equinor fusion-skills entrypoint at version 0.1.1 under the MIT license that orchestrates AI coding assistant rule authoring across GitHub Copilot, Cursor, and Claude Code. The skill routes setup, review, and scaffolding tasks to editor-specific agents such as agents/copilot.agent.md, agents/cursor.agent.md, and agents/claude-code.agent.md while explicitly excluding SKILL.md authoring, .agent.md agent definitions, and CI enforcement of rule files. Developers reach for fusion-rules when onboarding a repo to consistent assistant behavior or auditing fragmented instruction files across editors. The orchestrator role delegates to .system/fusion-rule-author for format decisions. Use fusion-rules during build when teams adopt multiple AI assistants and need one entrypoint to pick the correct rule file format per editor.
- Detects target editor from natural language intent and routes to the matching agent
- Supports GitHub Copilot, Cursor, and Claude Code rule formats
- One command to set up rules for all three editors sequentially for mixed teams
- Handles both initial setup and iterative review/improvement of existing rules
- Serves as the single entrypoint for all AI coding assistant rule authoring
Fusion Rules by the numbers
- 873 all-time installs (skills.sh)
- +22 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #1,258 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/equinor/fusion-skills --skill fusion-rulesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 873 |
|---|---|
| repo stars | ★ 1 |
| Last updated | August 4, 2026 |
| Repository | equinor/fusion-skills ↗ |
How do you set up AI coding assistant rules?
Quickly set up, review, or scaffold the right instruction and rule files for whichever AI coding assistant they are using.
Who is it for?
Teams standardizing AI assistant instructions across GitHub Copilot, Cursor, and Claude Code in one repository.
Skip if: Authoring SKILL.md skills, defining .agent.md agents, or enforcing rules through CI pipelines.
When should I use this skill?
A developer asks which editor rule format to use, wants to scaffold Copilot or Cursor rules, or review existing assistant instructions.
What you get
Editor-specific rule and instruction files for Copilot, Cursor, or Claude Code plus reviewed scaffolding guidance.
- Editor-specific rule files
- Reviewed instruction scaffolding
By the numbers
- fusion-skills version 0.1.1 under MIT license
- Orchestrates rule authoring across 3 editors: Copilot, Cursor, and Claude Code
Files
Fusion Rules
Gateway for AI coding assistant rule authoring. Detects the target editor and routes to the right agent.
Routing
| Intent | Agent |
|---|---|
| Set up GitHub Copilot instructions / rules | agents/copilot.agent.md |
| Set up Cursor project rules | agents/cursor.agent.md |
| Set up Claude Code rules / CLAUDE.md | agents/claude-code.agent.md |
| Set up rules for all editors / mixed team | Run all three agents sequentially |
| Review or improve existing rules | Route 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) — usefusion-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
Claude Code Rules Agent
Set up Claude Code project instructions and rules for a repository.
When to use
- "set up CLAUDE.md"
- "add Claude Code rules"
- "configure Claude Code for this repo"
- "create .claude/rules"
- "set up Claude instructions"
When not to use
- GitHub Copilot instructions — use
copilot.agent.md - Cursor rules — use
cursor.agent.md - Authoring skills (
SKILL.md) — usefusion-skill-authoring
Context
This agent focuses exclusively on Claude Code instruction files:
CLAUDE.mdor.claude/CLAUDE.md— project instructions (loaded every session, target under 200 lines).claude/rules/*.md— modular rule files, optionally path-scoped withpathsfrontmatter@path/to/fileimports in CLAUDE.md to pull in additional context
Activation modes
| Mode | Setup | When it activates |
|---|---|---|
| Unconditional | No paths frontmatter | Every session |
| Path-scoped | paths frontmatter with globs | When Claude reads matching files |
CLAUDE.md locations
| Location | Scope |
|---|---|
./CLAUDE.md or ./.claude/CLAUDE.md | Project (shared via VCS) |
~/.claude/CLAUDE.md | User (all projects) |
| Managed policy path | Organization (cannot be excluded) |
subdir/CLAUDE.md | Subdirectory (on-demand) |
Workflow
Follow .system/fusion-rule-author Steps 1–7, scoped to Claude Code:
1. Skip editor selection — target is Claude Code only 2. Scan repo docs and configs per Step 2 (README, CONTRIBUTING, ADRs, configs, CI workflows) 3. Assess CLAUDE.md, .claude/CLAUDE.md, and .claude/rules/**/*.md 4. Interview — present scan findings, fill gaps per Step 3 5. Classify into two buckets: always-on (CLAUDE.md / unconditional rules) and path-scoped rules 6. Draft using .system/fusion-rule-author/assets/claude-rule-template.md 7. Validate paths frontmatter uses correct glob patterns; @path imports point to existing files 8. Quality gate — CLAUDE.md under ~200 lines, one topic per rule file
Key references
.system/fusion-rule-author/assets/creation-follow-up.md— per-rule follow-up questions (purpose, exceptions, boundaries, voice).system/fusion-rule-author/assets/frontmatter-scenarios.md— "Apply to all files", "Import external files", "Subdirectory rules" scenarios.system/fusion-rule-author/references/examples.md— Claude Code equivalent examples.system/fusion-rule-author/assets/quality-checklist.md— "Claude Code" section
Safety & constraints
- Never embed secrets in instruction files
- Show drafts before writing
- Validate glob patterns and
@pathimports against actual repo paths - Do not invent conventions — only document what the developer confirms
Copilot Rules Agent
Set up GitHub Copilot custom instructions for a repository.
When to use
- "set up Copilot instructions"
- "add custom instructions for Copilot"
- "configure Copilot for this repo"
- "create copilot-instructions.md"
- "add scoped instruction files"
When not to use
- Cursor rules — use
cursor.agent.md - Claude Code rules — use
claude-code.agent.md - Authoring skills (
SKILL.md) — usefusion-skill-authoring
Context
This agent focuses exclusively on GitHub Copilot instruction files:
.github/copilot-instructions.md— root instructions (always-on).github/instructions/*.instructions.md— path-scoped instructions withapplyTofrontmatter
Workflow
Follow .system/fusion-rule-author Steps 1–7, scoped to GitHub Copilot:
1. Skip editor selection — target is GitHub Copilot only 2. Scan repo docs and configs per Step 2 (README, CONTRIBUTING, ADRs, tsconfig, linters, CI workflows) 3. Assess only .github/copilot-instructions.md and .github/instructions/*.instructions.md 4. Interview — present scan findings, fill gaps per Step 3 5. Classify into two buckets: always-on (root) and scoped (applyTo) 6. Draft using .system/fusion-rule-author/assets/copilot-instructions-template.md and .system/fusion-rule-author/assets/scoped-rule-template.md (GitHub Copilot section) 7. Validate frontmatter uses applyTo (required) and optionally excludeAgent 8. Quality gate — root under ~80 lines, scoped under ~50 lines
Key references
.system/fusion-rule-author/assets/creation-follow-up.md— per-rule follow-up questions (purpose, exceptions, boundaries, voice).system/fusion-rule-author/assets/frontmatter-scenarios.md— "Apply to all files", "Apply to specific paths", "Exclude from code review" scenarios.system/fusion-rule-author/references/examples.md— root and scoped instruction examples.system/fusion-rule-author/assets/quality-checklist.md— "Root instructions" and "Scoped instructions" sections
Safety & constraints
- Never embed secrets in instruction files
- Show drafts before writing
- Validate glob patterns against actual repo paths
- Do not invent conventions — only document what the developer confirms
Cursor Rules Agent
Set up Cursor project rules for a repository.
When to use
- "set up Cursor rules"
- "add Cursor rules"
- "configure Cursor for this repo"
- "create .cursor/rules"
- "add project rules for Cursor"
When not to use
- GitHub Copilot instructions — use
copilot.agent.md - Claude Code rules — use
claude-code.agent.md - Authoring skills (
SKILL.md) — usefusion-skill-authoring
Context
This agent focuses exclusively on Cursor rule files:
.cursor/rules/*.mdc— project rules with frontmatter controlling activation.cursor/rules/**/*.mdc— subdirectory-organized rules
Activation modes
| Mode | Frontmatter | When it activates |
|---|---|---|
| Always apply | alwaysApply: true | Every Agent session |
| Glob-scoped | globs: "<pattern>" | When matching files are in context |
| Agent-selected | description: "..." (no globs) | When Agent decides it is relevant |
| Manual | No alwaysApply, no globs, no description | Only when @-mentioned |
Workflow
Follow .system/fusion-rule-author Steps 1–7, scoped to Cursor:
1. Skip editor selection — target is Cursor only 2. Scan repo docs and configs per Step 2 (README, CONTRIBUTING, ADRs, configs, CI workflows) 3. Assess only .cursor/rules/** 4. Interview — present scan findings, fill gaps per Step 3 5. Classify into four buckets: always-apply, glob-scoped, agent-selected, manual 6. Draft using .system/fusion-rule-author/assets/cursor-rule-template.mdc 7. Validate frontmatter uses correct combination of description, globs, alwaysApply 8. Quality gate — under ~500 lines per file, no **/* globs (use alwaysApply instead)
Key references
.system/fusion-rule-author/assets/creation-follow-up.md— per-rule follow-up questions (purpose, exceptions, boundaries, voice).system/fusion-rule-author/assets/frontmatter-scenarios.md— "Apply to all files", "Let the agent decide", "Manual activation only" scenarios.system/fusion-rule-author/references/examples.md— Cursor equivalent examples.system/fusion-rule-author/assets/quality-checklist.md— "Cursor rules" section
Safety & constraints
- Never embed secrets in rule files
- Show drafts before writing
- Validate glob patterns against actual repo paths
- Do not invent conventions — only document what the developer confirms
Changelog
0.1.1 - 2026-05-07
patch
- Drop articles, filler, hedging from SKILL.md activation body
0.1.0 - 2026-03-21
minor
Gateway entrypoint that detects the target editor (GitHub Copilot, Cursor, Claude Code) and routes to the matching agent for guided rule scaffolding.
agents/copilot.agent.md— GitHub Copilot instructions workflowagents/cursor.agent.md— Cursor project rules workflowagents/claude-code.agent.md— Claude Code rules workflow
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Pick fusion-rules when multiple AI editors share one repo; use single-editor rule skills when only Cursor or only Claude Code is in play.
FAQ
Which AI editors does fusion-rules support?
fusion-rules version 0.1.1 orchestrates rule authoring for GitHub Copilot, Cursor, and Claude Code. Dedicated agent files exist for each editor under the fusion-skills repository.
What tasks should fusion-rules not handle?
fusion-rules excludes authoring SKILL.md skills, creating .agent.md agent definitions, and CI enforcement of rule files. Use other fusion-skills entrypoints for those workflows.