{"version":"2.1.317","anchor":"plugin-reserved-name-error-spells-out-the-rule","canonical_anchor":"plugin-reserved-name-error-spells-out-the-rule","heading":"Reserved plugin name error now explains which names are not allowed","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/plugin-reserved-name-error-spells-out-the-rule","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Reserved plugin name error now explains which names are not allowed\n\nThe error for a reserved plugin name now lists the forbidden prefixes and the rule about \"official\" with \"claude\" or \"anthropic\"\n\n**What**\n\nWhen a plugin's name is reserved, the error now spells out the rule instead of a general message. It lists the prefixes a name may not start with, and says a name may not put \"official\" beside \"claude\" or \"anthropic\".\n\n**Why**\n\nIf you write plugins, you can see from the error what to rename instead of guessing.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}