{"version":"2.1.265","anchor":"propose-skills-and-designsync-style-tools-refactored-to-per","canonical_anchor":"propose-skills-and-designsync-style-tools-refactored-to-per","heading":"propose_skills and DesignSync-style tools refactored to per-call factory pattern","tier":"internal","area":"Tooling Architecture","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/propose-skills-and-designsync-style-tools-refactored-to-per","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### propose_skills and DesignSync-style tools refactored to per-call factory pattern\n\npropose_skills and DesignSync tools refactored internally to a per-call factory pattern\n\n**What**\n\nThe `propose_skills` tool, along with a nearby DesignSync-related tool, now build their input-validation, permission-check, and call logic inside a `create(r)` method that returns an object, instead of defining those functions directly on the tool's definition.\n\n**Why**\n\nThis is an internal code restructuring with no described effect on behavior; it changes how the tool's implementation is organized rather than what the tool does.\n\n- Area: Tooling Architecture\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}