{"summary":"When to use a switch, checkbox, radio button, segmented control, select or dropdown menu.","notes":"<p>These controls look alike and are often mixed up. For example, a settings page has a switch to flip, yet there is also a Save button below it, and the setting does not take effect once the user leaves the page. The differences are explained below in four pairs:</p>\n        <ol>\n        <li><strong>Switches and checkboxes</strong>: The difference is when the change takes effect. A switch takes effect as soon as it is flipped and suits auto-saving contexts such as settings pages, with no Save button next to it; checkboxes are submitted with a form and need a submit button. Represent turning one thing on and off with a single switch, not two radio buttons for “On” and “Off”.</li>\n        <li><strong>Selects and dropdown menus</strong>: A select holds values, and the chosen one shows in the box, such as a language; a dropdown menu holds actions, which run as soon as they are clicked while the button label stays the same, and is often used to tuck away buttons in a toolbar or at the top of a page. The most used action can be the main button, with an icon button beside it opening the rest, such as “Schedule send” and “Save as draft” next to “Send”.</li>\n        <li><strong>Segmented controls and selects</strong>: Both are for picking one. Use a segmented control for 2–5 short options, which can be taken in at a glance; when each option needs a line of explanation, use radio buttons stacked vertically instead. Use a select when there are more options, the text is long, or the options change (names, dates, items users add), so the interface does not jump; for up to hundreds (time zones, countries), add a search box at the top of the list and a clear message for when nothing matches.</li>\n        <li><strong>Radio buttons and checkboxes</strong>: Radio buttons suit single-choice questions where all options should be read, as in a survey; once a choice is made it cannot be cleared, so provide an option such as “Not sure yet”; when several can be picked, use checkboxes. The same goes inside a select: for a single choice, put a check mark after the chosen item instead of drawing a radio circle; for multiple choice, put a checkbox before each item.</li>\n        </ol>\n        <p>Also, the result of every control must be visible right away: turning on desktop notifications immediately shows a notification; after “Export data” runs from a dropdown menu, a Toast reports the result.</p>\n        <h2>Parameters</h2>\n        <dl class=\"params\">\n        <dt>Number of options</dt><dd>2–5 short options: segmented control; 2–5 that each need explaining: radio buttons; 6 or more: select; hundreds: select with search</dd>\n        <dt>Switch</dt><dd>40×24px, 8px corners; 18px thumb; 220ms, cubic-bezier(.32, .72, 0, 1)</dd>\n        <dt>Segmented control</dt><dd>36px tall, 4px padding; 28px thumb, 8px corners; 280ms</dd>\n        <dt>Option list</dt><dd>36px options; 14px corners; opens in 180ms, closes in 120ms</dd>\n        <dt>Radio buttons and checkboxes</dt><dd>18px; radio buttons round, checkboxes with 5px corners</dd>\n        </dl>\n        <p>The included prompt first finds every selection control in the product, decides whether each one is used correctly and what it should change to, and lists them in a table for you to decide; once you confirm, it changes them one by one according to these rules.</p>","prompt":"Review the choice controls in my product, and decide for each one whether it is the right control: switches, checkboxes, radio buttons, segmented controls, tabs, selects and dropdown menus. Then, if I want it, change the ones I approve. This is about judgment first: diagnose and recommend, and change only what I approve.\n\nThis is a change to my product, not a demo. Work inside my code, on my stack, with my components, tokens and copy style. Do not add a dependency or a new visual pattern without asking. When a control I need is missing (a segmented control, a select with search), say so and propose one from my component library or the platform before building it.\n\n0. Read the product first\n- Find every place a person picks something, turns something on or off, or runs an action from a list: settings and preferences, forms and dialogs, sign-up and onboarding questions, filters and toolbars, page headers, row menus.\n- For each control, note:\n  - what it sets, or what it does;\n  - the options: how many, how long their labels are, and whether each needs a line of explanation;\n  - how many can be picked, and whether picking none is a valid answer;\n  - when a change takes effect: at once, or on Save or Submit;\n  - where it sits: a settings list, a form, a survey, a toolbar or page header;\n  - what it shows after a pick.\n- Find the shared components behind them (switch, checkbox, radio group, segmented control, tabs, select, combobox, menu).\n- Tell me in a few lines what you found before going on.\n\n1. How to choose\nSettle each control by these pairs. Each pair differs in one thing.\n\na. Switch or checkbox: when the change takes effect.\n- Switch: it takes effect the moment it is flipped, like a light switch. Use it in settings and preferences that save on their own, with no Save button nearby. The effect should show at once, or be easy to see (a notification turned on, a panel shown).\n- Checkbox: it is one answer in a form, and takes effect when the form is submitted (Make it private, in a New project dialog; Email me a copy, before Send).\n- One thing on or off is never two radio buttons (On / Off): the reader has to read both to know the state, and it looks like a bigger choice than it is.\n- The test: if the opposite of the option is just \"not\", it is one thing on or off. If both sides have names of their own (Light / Dark, Monthly / Yearly), it is a choice of one: go to (c).\n- Wrong: a switch in a form with a Save button (people flip it, leave, and nothing was saved); a checkbox in a list that saves on its own (people look for a Save button).\n\nb. Select or dropdown menu: a value or an action.\n- Select: it holds a value. After a pick the field shows the new value, and a setting takes effect at once (pick a language and the page is in that language). In its list the picked option has a tick.\n- Dropdown menu: it holds actions (Export data, Duplicate, Delete). A pick runs the action, the button keeps its own name (More, a \"…\" icon, Export), and the result is shown elsewhere (a toast, a new page, a download). Menus belong in page headers, toolbars and at the end of rows, not among a form's fields.\n- Split button: a main action with an icon beside it that opens a dropdown menu of the actions that go with it (Send, and beside it Send tomorrow at 9:00, Send a test to me, Save as draft). Each item runs as it is picked, and the main button keeps its name. Use it when one action is used far more often than the others that go with it.\n- Wrong: a menu whose button turns into the picked item; a select whose options are verbs, or that sits on \"Actions\" and stays on the action just run; a value whose current setting can't be seen without opening the list.\n- Tabs and segmented controls differ the same way: tabs switch to a different page of content and set nothing; a segmented control sets a value, or switches the view of the same content (List / Board / Calendar).\n\nc. One of several: by how many options there are.\n- 2 to 5 short options: a segmented control. One press picks, and every option stays in view.\n- 2 to 5 options that each need a line: radio buttons, one under another, each with its line under its label. Put the group under the setting's label, on the same left edge, rather than squeezed into the control column.\n- 6 or more: a select.\n- Options whose labels change or whose number can grow (names, counts, dates, items people add): a select, even when there are only a few today, so a longer label or a new option never pushes the layout around.\n- Hundreds (time zones, countries, people): a select with a search field at the top of its list; typing narrows the list, and when nothing matches, the list says so (No time zones match \"xyz\") rather than going blank.\n- Wrong: three short options hidden in a select (two presses, and only one option in view); a long list laid out in a row that runs off its end or wraps.\n\nd. Radio button or checkbox: how many can be picked.\n- Radio buttons: exactly one, with every option shown. Use them where all the options must be read before answering: a survey or onboarding question, a plan in a form, options that need explaining (see c). A radio can't be cleared once picked, so when \"none\" is a fair answer, add it as an option (Not sure yet, None of these), or make it a checkbox list.\n- Checkboxes: any number, none included. Stack them, one under another.\n- Inside a select it is the same: one value gets a tick on the picked option, never radio circles; several values get a checkbox before each option, and the field shows what is picked as chips, or as a count when there are many.\n\n2. Rules for every control\n- Each control says what it sets, in its label, not only in its options.\n- The current value is always visible without opening anything.\n- A control that takes effect at once shows the effect; a form shows nothing has happened until it is submitted.\n- Defaults are the safe and common choice; nothing is pre-ticked that signs the person up for something.\n- When a control is unavailable, say why, rather than only greying it out.\n- Keyboard and screen readers: a switch is role=\"switch\" with aria-checked; radio buttons are one radiogroup moved with the arrow keys; a select opens with Enter or Space and moves with the arrows; a menu is role=\"menu\" and closes with Escape. Touch targets are at least 44 by 44.\n\n3. Report before changing anything\nGive me a table first, and do not change code yet. One row per control:\n- Where: the screen, and the setting or question.\n- What it sets or does, in a phrase: its options, how many can be picked, when it takes effect.\n- Now: the control in use.\n- Should be: the control it should be, or \"right as it is\".\n- Why: one line that points to the rule in section 1.\n- Change: what changes besides the control, if anything: a Save button added or removed, a \"none\" option added, an action moved out of the form into a menu.\nGroup the rows by the pairs in section 1. Mark the ones that are already right. When a case could go either way, say what decides it and ask me. Call out every change that alters behaviour (a switch that becomes a checkbox now waits for Save; an action that leaves a form moves to the page header). Then ask me which rows to change, and wait.\n\n4. Change what I approve\n- List the files you will touch and wait for my go-ahead.\n- Change one control at a time and keep what it sets and does, unless I agreed to change that too. Keep the value people already saved.\n- Use my own components where they exist; follow the platform's own controls where they don't:\n  - Web: a native select or a listbox with a search field (combobox); role=\"switch\" for switches; a radiogroup for radios; a menu button for menus.\n  - iOS: Toggle, Picker with the .segmented or .menu style, Menu, and a searchable list for long ones.\n  - Android: Switch, Checkbox, RadioButton, SegmentedButton, ExposedDropdownMenu for values and DropdownMenu for actions.\n  - Flutter: Switch, Checkbox, Radio, SegmentedButton, DropdownMenu with search for values, and MenuAnchor for actions.\n\n5. Check\n- Every switch takes effect at once, and every checkbox only on submit.\n- Every select shows its value after a pick; every menu button keeps its name after an action.\n- No radio pair stands for on and off, and every radio question that allows none has a way to say so.\n- Long lists can be searched, and say so when nothing matches; short ones are laid out.\n- Keyboard, screen reader, phone and desktop layouts, light and dark; existing tests still pass.","skill":"/skills/kubai-choice-controls/SKILL.md","skillText":"# 选择控件的诊断与改造\n\n《999 个小技巧，让你 Vibe 的产品更有质感》第 020 期 · @kubai087\n\n在用户的项目里按下面的要求改造。要求以用户的口吻写成：文中的 I、me、my 指用户；写着要先问的地方，先停下来问用户再继续。\n\n## 改造要求\n\nReview the choice controls in my product, and decide for each one whether it is the right control: switches, checkboxes, radio buttons, segmented controls, tabs, selects and dropdown menus. Then, if I want it, change the ones I approve. This is about judgment first: diagnose and recommend, and change only what I approve.\n\nThis is a change to my product, not a demo. Work inside my code, on my stack, with my components, tokens and copy style. Do not add a dependency or a new visual pattern without asking. When a control I need is missing (a segmented control, a select with search), say so and propose one from my component library or the platform before building it.\n\n0. Read the product first\n- Find every place a person picks something, turns something on or off, or runs an action from a list: settings and preferences, forms and dialogs, sign-up and onboarding questions, filters and toolbars, page headers, row menus.\n- For each control, note:\n  - what it sets, or what it does;\n  - the options: how many, how long their labels are, and whether each needs a line of explanation;\n  - how many can be picked, and whether picking none is a valid answer;\n  - when a change takes effect: at once, or on Save or Submit;\n  - where it sits: a settings list, a form, a survey, a toolbar or page header;\n  - what it shows after a pick.\n- Find the shared components behind them (switch, checkbox, radio group, segmented control, tabs, select, combobox, menu).\n- Tell me in a few lines what you found before going on.\n\n1. How to choose\nSettle each control by these pairs. Each pair differs in one thing.\n\na. Switch or checkbox: when the change takes effect.\n- Switch: it takes effect the moment it is flipped, like a light switch. Use it in settings and preferences that save on their own, with no Save button nearby. The effect should show at once, or be easy to see (a notification turned on, a panel shown).\n- Checkbox: it is one answer in a form, and takes effect when the form is submitted (Make it private, in a New project dialog; Email me a copy, before Send).\n- One thing on or off is never two radio buttons (On / Off): the reader has to read both to know the state, and it looks like a bigger choice than it is.\n- The test: if the opposite of the option is just \"not\", it is one thing on or off. If both sides have names of their own (Light / Dark, Monthly / Yearly), it is a choice of one: go to (c).\n- Wrong: a switch in a form with a Save button (people flip it, leave, and nothing was saved); a checkbox in a list that saves on its own (people look for a Save button).\n\nb. Select or dropdown menu: a value or an action.\n- Select: it holds a value. After a pick the field shows the new value, and a setting takes effect at once (pick a language and the page is in that language). In its list the picked option has a tick.\n- Dropdown menu: it holds actions (Export data, Duplicate, Delete). A pick runs the action, the button keeps its own name (More, a \"…\" icon, Export), and the result is shown elsewhere (a toast, a new page, a download). Menus belong in page headers, toolbars and at the end of rows, not among a form's fields.\n- Split button: a main action with an icon beside it that opens a dropdown menu of the actions that go with it (Send, and beside it Send tomorrow at 9:00, Send a test to me, Save as draft). Each item runs as it is picked, and the main button keeps its name. Use it when one action is used far more often than the others that go with it.\n- Wrong: a menu whose button turns into the picked item; a select whose options are verbs, or that sits on \"Actions\" and stays on the action just run; a value whose current setting can't be seen without opening the list.\n- Tabs and segmented controls differ the same way: tabs switch to a different page of content and set nothing; a segmented control sets a value, or switches the view of the same content (List / Board / Calendar).\n\nc. One of several: by how many options there are.\n- 2 to 5 short options: a segmented control. One press picks, and every option stays in view.\n- 2 to 5 options that each need a line: radio buttons, one under another, each with its line under its label. Put the group under the setting's label, on the same left edge, rather than squeezed into the control column.\n- 6 or more: a select.\n- Options whose labels change or whose number can grow (names, counts, dates, items people add): a select, even when there are only a few today, so a longer label or a new option never pushes the layout around.\n- Hundreds (time zones, countries, people): a select with a search field at the top of its list; typing narrows the list, and when nothing matches, the list says so (No time zones match \"xyz\") rather than going blank.\n- Wrong: three short options hidden in a select (two presses, and only one option in view); a long list laid out in a row that runs off its end or wraps.\n\nd. Radio button or checkbox: how many can be picked.\n- Radio buttons: exactly one, with every option shown. Use them where all the options must be read before answering: a survey or onboarding question, a plan in a form, options that need explaining (see c). A radio can't be cleared once picked, so when \"none\" is a fair answer, add it as an option (Not sure yet, None of these), or make it a checkbox list.\n- Checkboxes: any number, none included. Stack them, one under another.\n- Inside a select it is the same: one value gets a tick on the picked option, never radio circles; several values get a checkbox before each option, and the field shows what is picked as chips, or as a count when there are many.\n\n2. Rules for every control\n- Each control says what it sets, in its label, not only in its options.\n- The current value is always visible without opening anything.\n- A control that takes effect at once shows the effect; a form shows nothing has happened until it is submitted.\n- Defaults are the safe and common choice; nothing is pre-ticked that signs the person up for something.\n- When a control is unavailable, say why, rather than only greying it out.\n- Keyboard and screen readers: a switch is role=\"switch\" with aria-checked; radio buttons are one radiogroup moved with the arrow keys; a select opens with Enter or Space and moves with the arrows; a menu is role=\"menu\" and closes with Escape. Touch targets are at least 44 by 44.\n\n3. Report before changing anything\nGive me a table first, and do not change code yet. One row per control:\n- Where: the screen, and the setting or question.\n- What it sets or does, in a phrase: its options, how many can be picked, when it takes effect.\n- Now: the control in use.\n- Should be: the control it should be, or \"right as it is\".\n- Why: one line that points to the rule in section 1.\n- Change: what changes besides the control, if anything: a Save button added or removed, a \"none\" option added, an action moved out of the form into a menu.\nGroup the rows by the pairs in section 1. Mark the ones that are already right. When a case could go either way, say what decides it and ask me. Call out every change that alters behaviour (a switch that becomes a checkbox now waits for Save; an action that leaves a form moves to the page header). Then ask me which rows to change, and wait.\n\n4. Change what I approve\n- List the files you will touch and wait for my go-ahead.\n- Change one control at a time and keep what it sets and does, unless I agreed to change that too. Keep the value people already saved.\n- Use my own components where they exist; follow the platform's own controls where they don't:\n  - Web: a native select or a listbox with a search field (combobox); role=\"switch\" for switches; a radiogroup for radios; a menu button for menus.\n  - iOS: Toggle, Picker with the .segmented or .menu style, Menu, and a searchable list for long ones.\n  - Android: Switch, Checkbox, RadioButton, SegmentedButton, ExposedDropdownMenu for values and DropdownMenu for actions.\n  - Flutter: Switch, Checkbox, Radio, SegmentedButton, DropdownMenu with search for values, and MenuAnchor for actions.\n\n5. Check\n- Every switch takes effect at once, and every checkbox only on submit.\n- Every select shows its value after a pick; every menu button keeps its name after an action.\n- No radio pair stands for on and off, and every radio question that allows none has a way to say so.\n- Long lists can be searched, and say so when nothing matches; short ones are laid out.\n- Keyboard, screen reader, phone and desktop layouts, light and dark; existing tests still pass.\n"}