{"summary":"開關、核取方塊、單選按鈕、分段控制項、下拉式清單和下拉式選單，分別適合什麼情境。","notes":"<p>這幾個控制項外觀相近，經常被混用。例如設定頁裡切換了開關，下面卻還有一個儲存按鈕，使用者離開頁面後設定並沒有生效。下面分四組說明區別：</p>\n        <ol>\n        <li><strong>開關與核取方塊</strong>：區別在於何時生效。開關切換後立即生效，適合設定頁這類自動儲存的情境，旁邊不放儲存按鈕；核取方塊隨表單一起送出，需要搭配送出按鈕。一件事的開與關用一個開關表示，不用「開／關」兩個單選按鈕。</li>\n        <li><strong>下拉式清單與下拉式選單</strong>：下拉式清單裡是值，選取後顯示在框中，例如語言；下拉式選單裡是動作，點擊後立即執行，按鈕文字不變，常用於收納工具列或頁面頂部的按鈕。最常用的動作可以做成主按鈕，旁邊用圖示按鈕展開其餘動作，例如「傳送」旁邊的「排程傳送」「儲存為草稿」。</li>\n        <li><strong>分段控制項與下拉式清單</strong>：都用於單選。2–5 個簡短的選項用分段控制項，一目了然；每項需要一行說明時，改用上下排列的單選按鈕。選項更多、文字較長，或者會變化（人名、日期、使用者新增的項目）時用下拉式清單，以免介面跳動；多達幾百個時（時區、國家），在清單頂部加上搜尋框，並做好沒有結果時的提示。</li>\n        <li><strong>單選按鈕與核取方塊</strong>：單選按鈕適合問卷這類需要讀完所有選項的單選題，選取後無法取消，所以要提供「暫不確定」之類的選項；可以選多個時用核取方塊。下拉式清單裡也一樣：單選時在選取項後打勾，不畫單選圓圈；多選時在每項前放核取方塊。</li>\n        </ol>\n        <p>另外，每個控制項的結果都要立刻可見：開啟桌面通知後馬上跳出一則通知；下拉式選單執行「匯出資料」後，用 Toast 告知結果。</p>\n        <h2>參數</h2>\n        <dl class=\"params\">\n        <dt>選項數量</dt><dd>2–5 個短選項用分段控制項；2–5 個、每項需要說明用單選按鈕；6 個以上用下拉式清單；幾百個用附搜尋功能的下拉式清單</dd>\n        <dt>開關</dt><dd>40×24px，圓角 8px；滑塊 18px；切換 220ms，cubic-bezier(.32, .72, 0, 1)</dd>\n        <dt>分段控制項</dt><dd>高 36px，內距 4px；滑塊高 28px，圓角 8px；切換 280ms</dd>\n        <dt>選項清單</dt><dd>選項高 36px；圓角 14px；展開 180ms，收起 120ms</dd>\n        <dt>單選按鈕與核取方塊</dt><dd>18px；單選按鈕為圓形，核取方塊圓角 5px</dd>\n        </dl>\n        <p>附帶的提示詞會先找出產品中所有的選擇控制項，逐一判斷是否用對、應換成哪一種，列成表格由你決定；確認後再依規則逐一改造。</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"}