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.
- License 许可
- MIT
- 最近更新
- 2026-07-18
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- fusion-rules
- license
- MIT
- metadata
- { "role": "orchestrator", "tags": [ "copilot", "cursor", "claude-code", "rules", "instructions", "developer-experience", "onboarding", "entrypoint" ], "owner": "@equinor/fusion-core", "skills": [ "agents/copilot.agent.md", "agents/cursor.agent.md", "agents/claude-code.agent.md" ], "status": "active", "version": "0.1.1", "orchestrator": ".system/fusion-rule-author" }
- description
- 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.
02 资源文件 1
- 参考文档metadata.json437 B
03 SKILL.md 正文
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:
- Run first agent's scan and interview (Steps 1–3) in full
- Pass scan summary + interview answers as context to remaining agents — they skip Steps 1–3 and start at Step 4 (Classify)
- Each agent drafts, reviews, and writes files for its own editor format
- 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
04 同仓库更多 Skills
arxiv-search
Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.
arxiv-search
Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.
working-with-legacy-code
Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.
working-with-legacy-code
Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.