Seems that with Figma’s MCP integration with Claude (via VSCode Chat) It is struggling to replace contents dynamically. is this a known limitation given the newness of slots?
Actually, I'm realizing the real constraint in Figma's component model depends on whether the component uses defined component properties or slot-based children. For slot components, I need to navigate the instance tree correctly to modify the slot frame's children, but the approach differs based on how the component is structured.
Looking at how the DetailsPage component is set up, it has named frames like "Heading", "Content", and "Aside" that act as slots, each with default content that gets replaced when properties are passed in. This means within an instance, I should be able to modify what's inside those slot frames by targeting them correctly.
The key insight is that I don't need to detach the instance to customize it. Instead, I can create the instance and then navigate into its internal structure to either hide the default content and add new frames, or swap out nested instances within those slots while keeping the parent instance intact.
But there's a limitation I'm running into—in the Figma plugin API, I can't actually add arbitrary new frames to an instance's internal frames since those children are read-only overrides. What I can do is modify text, change properties, swap nested component instances, and toggle visibility.
So I need to pivot away from the component instance approach entirely and instead treat the DetailsPage component as a frame reference to work from.