{"version":"2.1.317","anchor":"design-sync-validates-path-names-claudeaidesign-cannot-sto","canonical_anchor":"design-sync-validates-path-names-claudeaidesign-cannot-sto","heading":"DesignSync now checks file names claude.ai\/design would change","tier":"notice","area":"DesignSync","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/design-sync-validates-path-names-claudeaidesign-cannot-sto","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### DesignSync now checks file names claude.ai\/design would change\n\nDesignSync now refuses paths claude.ai\/design cannot store cleanly and uses the stored names in plans and listings\n\n**What**\n\nclaude.ai\/design stores some files under a plainer name than they have on disk. It drops \"#\", \"?\" and invisible characters, and evens out quotes, dashes and spaces. DesignSync, the tool Claude uses to sync files with claude.ai\/design, now takes this into account:\n\n- Uploads, deletes and paths are refused when dropping those characters would leave no usable name, when the path is too long, or when two paths would end up with the same stored name. Each refusal tells Claude how to fix it.\n\n- Plans and listings now use the stored names. Before, Claude was told to list every path exactly as passed.\n\n- `finalize_plan` gets an extra validation step.\n\n- The bundled design skill gains a top-level SKILL.md entry.\n\n**Why**\n\nFiles are no longer quietly renamed or overwritten by another file with the same stored name, and the plan Claude shows matches what actually ends up in the design project.\n\n- Area: DesignSync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}