recursica-skill-segmented-control

Use a segmented control when the layout calls for a horizontal single-select with 2 to 5 short-labeled options, such as a view switcher or inline filter. Radio buttons remain the house pattern for vertical single-selects and are never rotated into a row.

A segmented control holds the values of a single-select field, while tabs hold parts of one whole with their own content and routes. They are not interchangeable, and tabs must never be the fallback when a segmented control's option set grows beyond five.

A segmented control supports 2 to 5 options, and this ceiling overrides the general 7 ± 2 house rule because the control is horizontal and compact. Larger sets should use a vertical radio group or a dropdown instead.

Build it as a radio group with an accessible group name, programmatic selected state, and explicit names for icon-only segments. The group must be a single tab stop with arrow keys moving selection, and focus must land on the selected segment.

No, a segmented control is strictly single-select with exactly one option always selected. For multi-select, use selectable chips horizontally or a checkbox group vertically instead.

Avoid it when there are more than five options, labels are long, switching triggers heavy reloads or destructive actions, or the choice is a simple on/off state. Those cases call for a dropdown, radio group, explicit submission control, or switch.