Reference claude design projects vs design sessions gap

The Claude Design connection (DesignSync tool) has a narrower scope than expected: it can list and read/write design-system projects (component-library type, like CreatorTrack Design System), but it has no API surface into Design sessions where a user generates a mockup/design using that system. Confirmed via live test: after Justin created a new design in claude.ai/design using the CreatorTrack Design System, DesignSync's project listing stayed frozen at exactly the files previously pushed, and the artifacts list only showed one unrelated old item. The data flow is one-way: Claude can push components up and read them back down, but a Design session's output does not flow back into the project automatically.

Workarounds when a user says "look at the design I just made": (1) ask them to save/add the result into the design-system project from the claude.ai Design UI, if that option exists, which makes it instantly visible as a file; (2) use the forge browser stream with a logged-in claude.ai profile to open claude.ai/design directly and read/screenshot it; (3) ask for a share link to fetch; (4) ask for a plain-language description of what was requested and reconstruct it from the same tokens/components.

Why: Justin was confused why Claude couldn't see a design he made, expecting the same visibility he gets for the design-system project itself. This is a product boundary, not a setup problem.

How to apply: When Justin references something he "just made" in claude.ai/design, don't assume DesignSync will show it. Check the design-system project first (may be genuinely new if he saved it there), then offer the browser-stream or share-link workaround rather than treating it as a bug to fix locally.

[auto-memory session 7dcb3507-9c2d-4196-97bf-7dcab2608348, confidence 0.85, mode direct]