DesignSync cannot access regular claude.ai projects — only design-system projects are listed
Problem
The DesignSync tool in Claude Code only lists and operates on claude.ai projects of type PROJECT_TYPE_DESIGN_SYSTEM. Regular claude.ai projects are invisible to it — list_projects filters them out entirely, so Claude Code can neither read nor write them.
In practice this breaks a common design workflow: our screen designs live in a regular claude.ai project (the project predates the design-system type and contains all app screen designs, e.g. a page per screen). From Claude Code there is no way to hand a design task to that project, read an approved design back, or add a proposal page to it. The only workaround is manual copy-paste by the user, or driving the browser via the Chrome extension.
Expected
Either:
DesignSync(or a sibling tool) can list/read/write regular claude.ai projects the user owns, or- at minimum read access to project files/pages of regular projects, so approved design artifacts can flow back into the repo without manual copy-paste.
Secondary friction (same session)
When writing a preview HTML into a design-system project with write_files, the Design System pane did not show the new card until _ds_manifest.json was hand-edited (and even register_assets was needed as a fallback). The docs say the pane indexes from the first-line @dsCard marker compiled by 'the app's self-check', but nothing triggers that compile for files uploaded via DesignSync alone — a card written with a valid @dsCard marker silently never appears. Expected: uploading a file with a @dsCard marker (re)builds the card index, or write_files warns that a manifest update is required.
Environment
- Claude Code CLI, model claude-fable-5
- macOS (darwin), Claude in Chrome extension available
- DesignSync methods used: list_projects, list_files, get_file, finalize_plan, write_files, delete_files, register_assets
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗