Been testing out the Figma Agent using component library and have found it sometimes uses slots ok and often times bombs. I asked it what the problem was and got this response to pass along...it’s one of 3 patterns of problems the agent encountered.
Pattern 1 — Slot-based composition not supported as JSX children (20 of 33 failures)
This is the biggest issue. The design agent tried to nest child components inside container components via JSX children:
jsx code
<ComponentBox2 hasHeader={true} boxHeader={{heading:"Staff Info"}}>
<ComponentDescriptionList3 mode="vertical" numOfPairs="4" .../> ← REJECTED
</ComponentBox2>
But Library's Box uses a SLOT property (Content#20610:16) for its content area — the guidelines say "Append children directly to the SLOT node." The JSX renderer doesn't support passing components as children into slot-based containers. This affects every Box (6 failures) and every Tile (9 failures in v1). The preferred slot values are correctly defined (Description list, Toolbar, Data grid, Repeater row DIY, List summary details), but the agent has no way to populate them via JSX.
Note: The box component has a slot node that’s also surface as the property with the same name.