Mirzaaghazadeh Claude Code External Rules
mirzaaghazadeh-claude-code-external-rules is a Claude Code plugin for the Build phase that imports and injects coding rules from Cursor, Windsurf, Copilot, and Aider into Claude Code sessions.
Install this plugin when you are standardizing on Claude Code but already invested in Cursor, Windsurf, Copilot, or Aider rules files and want them imported without duplicate maintenance.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install mirzaaghazadeh-claude-code-external-rules@mirzaaghazadeh/claude-code-external-rulesBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:mirzaaghazadeh/claude-code-external-rules") and the paste-ready config with skillselion.get_install_config("plugin:mirzaaghazadeh/claude-code-external-rules").
What it does
mirzaaghazadeh-claude-code-external-rules is a one-plugin Claude Code marketplace that solves a common solo-builder friction point: you refined project rules in Cursor, Windsurf, GitHub Copilot, or Aider, then switched primary agent to Claude Code and do not want to rewrite or manually copy those files every sprint. The plugin imports external rule definitions and keeps them available so Claude Code sessions inherit the same constraints, style, and workspace conventions you already encoded elsewhere. It is intentionally narrow—configuration and rule bridging—not feature development or deployment. Best used early in a Claude Code adoption or when maintaining parallel editors on one repo. Confidence is high on scope from the repository description; exact file paths and merge behavior should be confirmed in the plugin README at install time.
Highlights
- Single-plugin marketplace focused on importing rules from Cursor, Windsurf, Copilot, and Aider.
- Automatically brings external rule files into Claude Code context.
- Designed to avoid duplicating rule sets across assistants.
- Rules can be injected for every conversation once configured.
- Productivity category: migration and consistency for multi-editor workflows.
Why builders use it
You already maintain assistant-specific rule files in another editor, and rewriting them for Claude Code duplicates effort and drifts standards.
After registration, external rules are imported and injected into conversations so Claude Code follows the same project guardrails without maintaining parallel copies by hand.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is mirzaaghazadeh-claude-code-external-rules for?
It is for developers who use Claude Code as their main agent but already have rule files from Cursor, Windsurf, Copilot, or Aider they want to reuse.
When should I use mirzaaghazadeh-claude-code-external-rules?
Use it at the start of a Claude Code setup or whenever you change editors and need consistent injected rules every conversation.
How do I add mirzaaghazadeh-claude-code-external-rules to my agent?
Register the mirzaaghazadeh/claude-code-external-rules marketplace in Claude Code and enable its single external-rules plugin per the repository install instructions.
Comments
Share how you use mirzaaghazadeh-claude-code-external-rules, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.