fusion-rule-author
Skill2 starsChanged 2 months agoMITView on GitHub
Support skill providing the workflow, templates, and references for AI coding assistant rule authoring. Invoked by fusion-rules gateway agents — not intended for direct use.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- caveman-compressSkill
- fusion-core-servicesSkill
- fusion-dependency-reviewSkill
- fusion-designSkill
- fusion-framework-mockingSkill
- fusion-framework-testingSkill
- fusion-github-review-resolutionSkill
- fusion-issue-solvingSkill
- fusion-issue-task-planningSkill
- fusion-mcpSkill
- fusion-package-scribeSkill
- fusion-pm-mcpSkill
- fusion-backend-devSkill
- fusion-developer-appSkill
- fusion-developer-portalSkill
- fusion-devtoolsSkill
- fusion-help-apiSkill
- fusion-help-docsSkill
- fusion-help-integrationSkill
- fusion-infra-cliSkill
- fusion-issue-authoringSkill
- fusion-roles-cliSkill
- fusion-rulesSkill
- fusion-skill-authoringSkill
- fusionSkill
- fusion-skillsSkill
- equinor-design-systemSkill
- fusion-code-conventionsSkill
- fusion-researchSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 58
Check the repository for existing rule files:
- Distinctive: line 77
Before interviewing, scan for existing documentation and configuration that encodes conventions.
- Distinctive: line 98
Test files — testing framework, naming conventions, file placement
- Distinctive: line 116
Use scan results to skip areas already well-documented.
- Distinctive: line 159
Decision rule: If a convention applies to all files in the repo, it belongs in root / always-on instructions.
- Distinctive: line 161
When targeting multiple editors, generate parallel files with equivalent content — do not duplicate guidance within a single editor's files.
- Very specific: line 172
Use assets/cursor-rule-template.mdc and set frontmatter accordingly
- Distinctive: line 180
Keep instructions concise — actionable directives, not explanations
- Distinctive: line 181
Use imperative voice ("Use camelCase for variables", not "Variables should use camelCase")
- Distinctive: line 182
Avoid duplicating guidance between root and scoped files
- Distinctive: line 195
Ask for approval or edits
- Very specific: line 199
After approval, write rule files to the repository.
- Distinctive: line 238
Keep instructions concise and actionable
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Rule Author
Canonical workflow, templates, and references for authoring AI coding assistant rules. Supports GitHub Copilot, Cursor, and Claude Code.
Internal skill. Users interact via the
fusion-rulesgateway, which routes to editor-specific agents that follow the workflow defined here.
Scope
This skill provides:
- Workflow (Steps 1–7 below) — the guided authoring process
- Templates (
assets/) — starter files for each editor format - References (
references/) — tech-stack examples
It does not provide agents. Agents live in fusion-rules/agents/ and reference this skill's assets and workflow.
Required inputs
Mandatory
- Repository context (working directory or repo URL)
Gathered during interview
- Tech stack (languages, frameworks, build tools)
- Code conventions (naming, formatting, patterns)
- Testing expectations (framework, coverage, style)
- Documentation preferences (comments, TSDoc/JSDoc, README standards)
- Commit and PR conventions
- Error handling patterns
- Security or compliance constraints
- File/path-specific conventions that need scoped rules
Instructions
Step 1 — Assess current state
Check the repository for existing rule files:
.github/copilot-instructions.md
.github/instructions/*.instructions.md
.cursor/rules/*.md
.cursor/rules/*.mdc
.cursor/rules/**/*.md
.cursor/rules/**/*.mdc
CLAUDE.md
.claude/CLAUDE.md
.claude/rules/*.md
.claude/rules/**/*.mdReport what exists, what is missing, and whether updates or new files are needed.
Step 2 — Scan repository
Before interviewing, scan for existing documentation and configuration that encodes conventions. Extract actionable directives from:
Documentation files:
README.md— project overview, setup, tech stackCONTRIBUTING.md— code style, PR workflow, commit conventionsAGENTS.md,CLAUDE.md— existing AI instructionsdocs/adr/**,adr/**,docs/decisions/**— Architecture Decision Recordsdocs/**/*.md— developer guides, onboarding docs, style guidesSECURITY.md— security policiesCODE_OF_CONDUCT.md— collaboration guidelines (rarely rule-relevant)
Configuration files:
package.json/pyproject.toml/*.csproj— tech stack, scripts, dependenciestsconfig.json/jsconfig.json— language settings, strictnessbiome.json/.eslintrc*/.prettierrc*/ruff.toml/.editorconfig— formatting and linting.github/workflows/*.yml— CI checks, required validations, test commandsDockerfile/docker-compose.yml— runtime environmentMakefile/Justfile/Taskfile.yml— build and task commands
Code patterns (sample, don't exhaustively read):
- Entry points (
src/index.*,src/main.*,app.*) — architecture patterns - Test files — testing framework, naming conventions, file placement
- Directory structure — architectural boundaries, feature organization
For each source, extract:
- Concrete conventions that can become imperative directives
- Build/test/lint commands the AI should know
- Architecture boundaries or patterns to follow
- Explicit "do this / don't do that" rules
Skip:
- Implementation details that change frequently
- Content that restates language/framework defaults
- Aspirational rules not enforced by CI or team practice
Present summary of discovered conventions to the developer, organized by area, before proceeding to the interview.
Step 3 — Interview (fill gaps)
Use scan results to skip areas already well-documented. Ask focused questions only for gaps. Cover these areas one at a time:
- Tech stack — languages, frameworks, runtime, package manager
- Code style — naming conventions, formatting rules, import ordering
- Architecture — project structure, key patterns (MVC, hexagonal, etc.)
- Testing — framework, conventions, coverage expectations
- Documentation — inline comments style, doc generation, README standards
- Git workflow — branch naming, commit message format, PR expectations
- Security — sensitive data handling, auth patterns, compliance rules
- Path-specific concerns — directories or file types needing specialized guidance
For each area, present what the scan found and ask: "Is this accurate? Anything to add or correct?" Don't re-ask for information already captured.
For each convention needing deeper context, use follow-up questions in assets/creation-follow-up.md — purpose, exceptions, boundaries, voice.
Step 4 — Classify guidance
Separate the gathered conventions into buckets:
GitHub Copilot:
| Bucket | Target file | When it activates |
| Always-on conventions | .github/copilot-instructions.md | Every Copilot interaction |
| Scoped conventions | .github/instructions/<name>.instructions.md | Only when matching files are open/referenced |
Cursor:
| Bucket | Target file | When it activates |
| Always-on conventions | .cursor/rules/<name>.mdc with alwaysApply: true | Every Cursor Agent session |
| Auto-attached conventions | .cursor/rules/<name>.mdc with globs | When matching files are in context |
| Agent-selected conventions | .cursor/rules/<name>.mdc with description only | When the Agent decides it is relevant |
| Manual conventions | .cursor/rules/<name>.mdc (no alwaysApply, no globs) | Only when @-mentioned in chat |
Claude Code:
| Bucket | Target file | When it activates |
| Always-on conventions | CLAUDE.md or .claude/CLAUDE.md | Every Claude Code session |
| Scoped conventions | .claude/rules/<name>.md with paths frontmatter | When Claude reads matching files |
| Unconditional rule | .claude/rules/<name>.md (no paths) | Every session (like always-on) |
Decision rule: If a convention applies to all files in the repo, it belongs in root / always-on instructions. If it applies only to specific paths or file types, create a scoped rule.
When targeting multiple editors, generate parallel files with equivalent content — do not duplicate guidance within a single editor's files.
Step 5 — Draft rule files
Generate files using templates in assets/:
GitHub Copilot:
- Root instructions: use
assets/copilot-instructions-template.md - Scoped instructions: use
assets/scoped-rule-template.mdwith correctapplyToglob
Cursor:
- Use
assets/cursor-rule-template.mdcand set frontmatter accordingly
Claude Code:
- Project instructions: use
assets/claude-rule-template.md - Scoped rules: place in
.claude/rules/withpathsfrontmatter
Quality rules (enforced during drafting):
- Keep instructions concise — actionable directives, not explanations
- Use imperative voice ("Use camelCase for variables", not "Variables should use camelCase")
- Avoid duplicating guidance between root and scoped files
- Validate
applyTo/globs/pathsglob patterns match intended files - Warn if total root instructions exceed ~80 lines (risk of context dilution)
- Warn if scoped instruction file exceeds ~50 lines (GitHub Copilot), ~500 lines (Cursor), ~200 lines (Claude Code CLAUDE.md)
- See
references/examples.mdfor concrete good/bad examples - See
assets/quality-checklist.mdfor full checklist
Step 6 — Review and refine
Present drafted files to the developer. For each file:
- Show full content
- Highlight quality warnings (length, broad globs, duplication)
- Ask for approval or edits
Step 7 — Write files
After approval, write rule files to the repository. Create .github/instructions/, .cursor/rules/, and/or .claude/rules/ directories as needed.
Confirm final file list and paths before writing.
Expected output
.github/copilot-instructions.md— root instructions file (created or updated).github/instructions/*.instructions.md— zero or more scoped instruction files.cursor/rules/*.mdc— zero or more Cursor rule files (when Cursor is targeted)CLAUDE.mdor.claude/CLAUDE.md— project instructions (when Claude Code is targeted).claude/rules/*.md— zero or more Claude Code scoped rule files- Summary of what was created/updated and why
Instructions vs skills vs rules — when to use which
| Need | GitHub Copilot | Cursor | Claude Code |
| Always-on coding conventions | copilot-instructions.md | .cursor/rules/*.mdc with alwaysApply: true | CLAUDE.md |
| File/path-specific guidance | .github/instructions/*.instructions.md | .cursor/rules/*.mdc with globs | .claude/rules/*.md with paths |
| Task-specific multi-step workflows | A skill (SKILL.md) | .cursor/rules/*.mdc (manual or agent-selected) | Skills / subagents |
| Agent routing and orchestration | Agent definitions (.agent.md) | .cursor/rules/*.mdc with description | Subagent configs |
| Simple project-wide instructions | copilot-instructions.md | AGENTS.md | CLAUDE.md |
Instructions and rules shape how the AI writes code. Skills define what it can do as structured tasks.
Safety and constraints
Never:
- Embed secrets, tokens, or credentials in rule files
- Generate rules that contradict repository security policies
- Overwrite existing files without showing the diff and getting approval
- Invent conventions — only document what the developer confirms
Always:
- Show drafts before writing any files
- Validate glob patterns against actual repository paths
- Warn on overly broad globs (e.g.,
**/*captures everything) - Keep instructions concise and actionable
- Preserve existing content when updating (append or merge, never replace silently)
References
references/examples.md— concrete examples for different tech stacksassets/creation-follow-up.md— per-rule follow-up questions (purpose, exceptions, boundaries, voice)assets/frontmatter-scenarios.md— scenario-based frontmatter guide for GitHub Copilot, Cursor, and Claude Codeassets/copilot-instructions-template.md— starter template for root instructionsassets/scoped-rule-template.md— starter template for scoped rulesassets/cursor-rule-template.mdc— starter template for Cursor rulesassets/claude-rule-template.md— starter template for Claude Code rulesassets/quality-checklist.md— quality review checklist
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
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.

