{"version":"2.1.269","anchor":"propose-skills-claudedesign-tools-refactored-to-create-b","canonical_anchor":"propose-skills-claudedesign-tools-refactored-to-create-b","heading":"propose_skills \/ ClaudeDesign tools refactored to create()-based instances","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/propose-skills-claudedesign-tools-refactored-to-create-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### propose_skills \/ ClaudeDesign tools refactored to create()-based instances\n\npropose_skills and the internal ClaudeDesign tool were rebuilt on the same factory pattern as other tools\n\n**What**\n\nThe `propose_skills` tool and an internal tool called `ClaudeDesign` now build their input validation, execution, and permission-check logic through a `create()` factory function, instead of defining those pieces directly on the tool. This matches a pattern already used elsewhere for other tools in this release.\n\n**Why**\n\nThis is a structural change to how these tools are put together internally; it does not change what the tools do or how they behave for someone using Claude Code.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}