{"version":"2.1.317","anchor":"design-sync-messages-for-design-systems-that-moved-to-claud","canonical_anchor":"design-sync-messages-for-design-systems-that-moved-to-claud","heading":"\/design-sync explains when a design system has moved to Claude","tier":"notice","area":"DesignSync","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/design-sync-messages-for-design-systems-that-moved-to-claud","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### \/design-sync explains when a design system has moved to Claude\n\nNew `\/design-sync` messages say a design system has moved, or is moving, to Claude, that updates can't be sent there yet, and how to open it\n\n**What**\n\n`\/design-sync` has new messages for a design system that has moved to Claude, or is in the middle of moving there. They tell you that `\/design-sync` can't send updates to Claude yet. They also include an \"Open it in Claude:\" prompt that points you to where the design system now lives.\n\n**Why**\n\nIf your design system has moved, you see a clear notice that `\/design-sync` can't update it yet, along with a way to open it in Claude.\n\n- Area: DesignSync\n- Names: `\/design-sync`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}