fusion-rules

What problem does it solve?

Many repositories need editor-specific instruction and rule files (GitHub Copilot, Cursor, Claude Code) but teams struggle to choose the right format, validate frontmatter/globs, and keep equivalent guidance consistent across editors. Fusion Rules centralizes intent detection, routes requests to the correct editor agent, and ensures drafts, validations, and diffs are shown before any file writes.

Core Features & Use Cases

• Editor detection and routing: Parse user intent to select Copilot, Cursor, or Claude Code workflows and load only the routed agent.
• Scaffolding and validation: Create or improve root and path-scoped instruction files, validate frontmatter (applyTo, globs, paths), and enforce quality gates (length, structure).
• Multi-editor orchestration: Run agents sequentially, pass scan summaries to avoid redundant scans, and generate equivalent files per editor without cross-editor duplication.
• Use case: Onboard a mixed team by detecting the preferred editor and scaffolding repository-specific Copilot instructions, Cursor rules, and a CLAUDE.md with consistent content and safe defaults.

Quick Start

Ask fusion-rules to detect the target editor and scaffold or review project rules for GitHub Copilot, Cursor, or Claude Code.