{"version":"2.1.140","anchor":"plugin-path-descriptions-clarified-override-vs-addition-sema","canonical_anchor":"plugin-path-descriptions-clarified-override-vs-addition-sema","heading":"Plugin Path Descriptions Clarified \u2014 Override vs. Addition Semantics","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140\/e\/plugin-path-descriptions-clarified-override-vs-addition-sema","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140","markdown":"### Plugin Path Descriptions Clarified \u2014 Override vs. Addition Semantics\n\n**What**\n\nPlugin `plugin.json` manifest fields that accept paths now clearly state whether they replace or extend the default auto-loaded directory.\n\n**Details**\n\n- Fields that fully replace the default directory (e.g., `agents`, `commands`, `output-styles`, `themes`) now document: \"When set, the `<name>\/` directory is not auto-loaded \u2014 list its files here if you want both.\"\n- Fields that load in addition to the default (e.g., the extra `skills` path) now document: \"Loaded in addition to the `skills\/` directory.\"\n- Previously, descriptions used \"in addition to those in the `<name>\/` directory\" uniformly, which was ambiguous.\n\n**Evidence**\n\nNew `.describe()` strings (search for `\"When set, the agents\/ directory is not auto-loaded\"`)"}