FollowUpSuggestions

Live

Behavior

• ·They are OFFERS, not actions: picking one seeds the composer's next question rather than silently running it.
• ·They stagger in on the control motion role, because they arrive after the answer settles — a row that appears all at once reads as chrome that was always there.
• ·ONE SHAPE, deliberately. A pill row was the obvious second variant and it was removed: a real follow-up is a sentence, so it wraps to two lines and needs a target the width of the surface. A pill could hold neither.
• ·Each row carries the open-arrow that says picking it goes somewhere; the heading ("Ask more") names the group, and label={null} drops it.
• ·Renders nothing when there are no suggestions; an empty invitation row is worse than none.
• ·It is ALSO the panel's empty state — the character opens the conversation and this card carries the offers, drawing them from the page's own suggestions (setPageIntel). An empty state that hand-rolls its own list is a second component nobody maintains, and it drifts the moment this one changes.

When to use

• ·After an answer that opens obvious next questions — a diff to review, a test to write.
• ·In an empty conversation, as the fastest way to show what the assistant can do.

When not to

• ·As navigation to product features; that is the palette's job.
• ·More than about four at a time — a menu of prompts is a decision, not a shortcut.