recursica-skill-selection-controls

Use a switch only inside a form when the value's inverse is binary, known, and unique (true/false, on/off), and the label alone names what is controlled. A checkbox flips a true/false flag on any value, so it works in groups where switches do not.

Use a radio group for mutually exclusive options up to roughly 7 ± 2 options, fewer if options are dissimilar or need domain expertise. Above that ceiling, use a dropdown only when the option set is predictable enough that users know what is inside before opening it.

Pre-select a radio option only when roughly 90 percent of users would choose it anyway, and never pre-select options with major downstream consequences. Most users cannot deselect a radio, so a default silently becomes the answer.

Clicking an indeterminate header checkbox always selects all rows, never deselects. Indeterminate is reachable only by selecting or deselecting individual rows, and no separate clear or deselect-all control should exist beside the header checkbox.

No, checkboxes and radios must be stacked vertically because horizontal arrangement breaks the pairing between control and label. For horizontal layouts, use a segmented control for single select (2–5 options) or selectable chips for multi-select.

Batch submit behind a submit button is the default; field-level instant writes must never mix with batch submit in the same system. If instant save is used, a persistent save-status message is required, and switches must commit consistently throughout.