Route editor-specific rule authoring requests and scaffold instruction files.
npx skills add https://github.com/equinor/fusion-skills --skill fusion-rules
Please help me install this Agent Skill. Skill: fusion-rules Source: https://github.com/equinor/fusion-skills/tree/main/skills/fusion-rules Command: npx skills add https://github.com/equinor/fusion-skills --skill fusion-rules
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.
Ask fusion-rules to detect the target editor and scaffold or review project rules for GitHub Copilot, Cursor, or Claude Code.
High-intent search queries and answers about installing and using this skill.
Scaffolding editor-specific rule files involves routing your authoring request to the correct agent based on detected editor intent, then generating validated instruction files with proper frontmatter and glob patterns. Fusion Rules automates routing, validation, and file creation.
Multi-editor rule orchestration runs editor-specific agents sequentially and passes scan summaries between them. This prevents redundant scans and generates equivalent instruction files for Copilot, Cursor, and Claude Code without cross-editor duplication.
Yes, you can validate frontmatter and glob patterns in existing rule files. The review process checks frontmatter fields like applyTo, globs, and paths, enforcing quality gates for length and structure before requiring diffs and approval for any writes.
Managing path-scoped rules for multiple AI assistants requires centralizing intent detection and routing requests to editor-specific agents. This ensures equivalent guidance is created consistently across Copilot, Cursor, and Claude Code instruction files.
No, you do not need to manually select an agent. The system parses user intent to detect the target editor automatically and loads only the routed agent file, streamlining the creation of Claude Code or Cursor rules.
Using a routing orchestrator solves the problem of choosing the correct format, validating frontmatter, and keeping guidance consistent across editors. It ensures drafts and validations are shown with diffs before any file writes occur.
djb258Normalize and classify incoming work requests into Planner Intake Packets.
sridBootstrap or refresh srid/agency integration in a codebase using uvx.
yigitkonurGenerate and refine GitHub Copilot code review instruction files with YAML frontmatter and glob patterns.
vitoSynchronize Dang syntax definitions across VSCode, Zed, and Neovim.
