[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754X8WRJECM6GTQ90P8P7RM":3,"skill-same:01M754X8WRJECM6GTQ90P8P7RM":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M754X8WRJECM6GTQ90P8P7RM","recursica-skill-button",null,"Rules for the Recursica button — button versus link, button styles, sizes and content, how many primary buttons, labels, destructive actions, icon-only buttons, and accessibility. Use for any button, submit and cancel pair, toolbar, or row action. Not for going to another page — see recursica-skill-link. Button hierarchy is in recursica-skill-buttons-links, and undo in recursica-skill-undo.","borderux\u002Frecursica-knowledge","borderux","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14911137?v=4","01M754SG94XX2Y7176KM2WGZG3","Border LLC","01M754SGA9E7YSNK6NWVMKMHYC",1,"MIT","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fcomponents\u002Frecursica-skill-button\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: recursica-skill-button\ndescription: Rules for the Recursica button — button versus link, button styles, sizes and content, how many primary buttons, labels, destructive actions, icon-only buttons, and accessibility. Use for any button, submit and cancel pair, toolbar, or row action. Not for going to another page — see recursica-skill-link. Button hierarchy is in recursica-skill-buttons-links, and undo in recursica-skill-undo.\nlicense: MIT\nmetadata:\n  author: hi@borderux.com\n  version: 0.2.0\n---\n\n# Button\n\nA button performs an action, such as saving a form or deleting a record. A button never takes the persona to a different page or URL.\n\n## When to use a button\n\n- The action saves, submits, deletes, applies a change, or opens a modal.\n- The persona stays on the same page after the action.\n- The action moves a process forward or back, such as Next and Back in a stepper. Next and Back change the step, not the page.\n\n## When not to use a button\n\n| Situation                                                                         | Use instead                                                                                                    |\n| --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |\n| Clicking goes to a different page or URL                                          | A link, with a real `href`. See `recursica-skill-link`.                                                        |\n| A table row opens a related record, such as the customer on an order              | A link. A link has less visual weight than a button. A dense table needs less visual weight in each table row. |\n| The persona chooses one of two to five options, such as a view, like List or Grid | A segmented control. See `recursica-skill-segmented-control`.                                                  |\n| The persona turns a setting on or off, such as email alerts                       | A switch or a checkbox. See `recursica-skill-selection-controls`.                                              |\n| A table row has more action buttons than the table row has room for               | Fewer actions in the table row, not smaller buttons. See `recursica-skill-tables`.                             |\n\n**Never use a button to go to a different page or URL.** For example, \"View order\" opens the order's page, so \"View order\" is a link.\n\n- If clicking a control changes the URL, build the control as a link, even when the design shows a button.\n- If a control that goes to a different page needs less visual weight, use a link. Never use a button in the text style instead. A link has less visual weight than a button.\n\nUsing a button to go to a different page is the most common misuse of buttons.\n\n## Variants\n\n**Use only the button variants and options that the knowledge MCP server lists for the theme (the design a designer sets in Theme Forge: the token values, the components, and each component's variants, states and sizes).** Get the list with the server's `component_api` tool. Use the names the code uses. Never invent a variant or an option. Each theme can differ, because a designer can add variants and options in Theme Forge.\n\nThe rules below describe each option by role, such as \"the primary style\". The names in the standard UI kit (the unchanged UI kit in the official Recursica release) are examples only.\n\n- **Style.** Use the primary style for the main action, such as \"Save invoice\". Use the secondary style for the next most important action. Use the least prominent style for every other action. In the standard UI kit, the styles are `solid`, `outline` and `text`. The `text` style is also called \"Ghost\".\n- **Size.** A button has a default size and a smaller size. The standard UI kit calls the smaller size `small`.\n- **Content.** A button shows a label alone, an icon with a label, or an icon alone. The same variant puts an icon before the label, after the label, or on both sides of the label.\n- **Disabled state.** How to turn on the disabled state is an open question.\n- **Destructive action.** If the theme has a destructive style, use the destructive style. Color alone cannot mark a destructive action (an action that deletes data or cannot be undone).\n  - Name the destructive action in the label, as in \"Delete invoice\".\n  - Confirm an action only when the action is massively destructive, hard to recreate, and cannot be undone. See `recursica-skill-undo`.\n- **Loading.** A loading button is a button whose action is still running, such as \"Save invoice\" while the save runs. If the theme has a loading state, use the loading state. Otherwise, show the loading button in the disabled look. Give the loading button an animated icon, with or without a label.\n  - Never add a spinner beside the button.\n  - Never change the label.\n  - Never invent a state.\n- **Success.** If the theme has a success state, use the success state. Otherwise, show any confirmation of a finished action outside the button, such as \"Invoice saved\" in a toast. See `recursica-skill-toast`.\n- **Width.** If the theme has a full-width option, use the full-width option. Otherwise, never stretch a button to fill the container the button sits in, such as a card.\n\n## Rules\n\n**Write the label as a verb and an object.** Write \"Save page\", not \"OK\". Write \"Delete invoice\", not \"Yes\". The label alone must say what the button does. A screen reader often reads the label without the text around the button.\n\n**Use one primary button per page, panel, or modal.** For example, a modal that edits an invoice has one primary button, \"Save invoice\".\n\n- The primary button uses the primary style.\n- The button for the next most important action uses the secondary style.\n- Every other button uses the least prominent style.\n- No other button in the same page, panel, or modal uses the primary style.\n\n**Put action buttons at the bottom right of a form footer or a modal footer.** Put the primary button last in reading order. For example, a modal footer shows \"Cancel\", then \"Save invoice\" at the far right. `recursica-skill-buttons-links` sets this rule.\n\n**Give every icon-only button a tooltip and an accessible name** (the name a screen reader reads out for a control). For example, a trash-can icon button gets the tooltip and the accessible name \"Delete invoice\". The tooltip is for sighted personas using a mouse. A screen reader does not read the tooltip unless the tooltip text is also the accessible name.\n\n**Show a count in parentheses after the label, never in place of the label.** For example, a button that sets the status of selected items reads `Apply status`, then `Apply status (1)`, then `Apply status (102)`.\n\n- The label words stay the same, and only the number changes.\n- Never build the number into the label words, as in `Apply 102 statuses`.\n- Never change the label words between one item and many items.\n\n**Show no count when no item is selected.** Never show `(0)`.\n\n- Add the count when the persona selects the first item.\n- Remove the count when the last selected item is cleared.\n\nA zero only repeats what the persona can already see. A zero also makes the button look as if an item is selected.\n\n**Label a toggle button with the button's current state.** \"Follow\" becomes \"Following\" after the persona presses Follow.\n\n**While a submit action runs, show the submit button as a disabled button with a spinner.** `recursica-skill-forms` requires a disabled button with a spinner. If the theme has a loading state, use the loading state. Otherwise, build the disabled button with a spinner from the disabled state and an icon, with or without a label. Animate the icon. Keep the button the same size and in the same place. A button that moves or resizes is no longer under the persona's pointer.\n\n**Never use the smaller size to fit more side-by-side buttons**, in a toolbar, a footer, or a table row. Change the screen's structure instead of shrinking the buttons. Too many buttons side by side means the screen offers too many actions. See `recursica-skill-design-system-conventions`.\n\n**Hide a button the persona has no permission to use.** Never show the button disabled instead. For example, a persona who cannot delete invoices sees no \"Delete invoice\" button. See `recursica-skill-navigation`.\n\n## Accessibility\n\nThe rules below add to the accessibility baseline in `recursica-skill-design-system-conventions`, which every Recursica component follows.\n\nThe button component shows the focus ring. The button component also responds to a press by click and by keyboard. The application must add every behavior in the two lists below.\n\n### Screen readers\n\n- **Give every button an accessible name.** Set the accessible name explicitly on an icon-only button. A screen reader does not read the icon. A button with no accessible name is read only as \"button\".\n- **The accessible name should match the visible label.** When the accessible name and the label differ, the accessible name must still contain the label. A persona using voice control presses a button by saying the label.\n- **Name the object in an action button in a table row or a list.** Put the object in the accessible name, as in \"Delete invoice 1043\". Or, in the code, set the object on the row as context for the button. A table of thirteen rows might show \"Delete\" in every table row. A screen reader then announces \"Delete\" thirteen times, with nothing to tell the rows apart.\n- **Update the accessible name when a toggle button's label changes.** An accessible name that is out of date after a press is worse than no accessible name.\n- **Spell out the count in the accessible name.** The label shows `Apply status (102)`, and the screen reader says \"Apply status to 102 items.\" A bare number after the label, as in \"Apply status 102\", is unclear when heard. The number could be a quantity, an ID, or part of the name.\n- **The count is the one allowed case where the accessible name and the label differ.** The count still follows the rule that the accessible name must contain the label. The accessible name keeps the label words. A persona using voice control can still say \"Apply status\".\n- **Update the accessible name as the count changes.** With no item selected, the accessible name is `Apply status`, with no count. Do not announce every increase in the count while the persona selects items. The accessible name must be correct by the time the persona reaches the button.\n- **Use a real `button` element**, never a `div` or a `span` with a click handler. A screen reader announces only a real `button` element as a button. Only a real `button` element responds to Enter and Space by default.\n- **Put the meaning in the accessible name, not only in the icon.** A screen reader announces the accessible name of an icon-only button and nothing about the icon. `recursica-skill-design-system-conventions` requires every meaning to be shown in more than one way.\n- **Mark a loading button as busy, and hide the animated icon from screen readers.** The animation is visual only. Without the busy state, a persona using a screen reader hears nothing and presses the button again.\n- **Keep the accessible name while the button is busy**, or change the accessible name to another useful name, such as \"Saving\". Never leave the accessible name empty.\n\n### Keyboard and non-mouse navigation\n\n- **Do not intercept, remap, or block Enter or Space on a button.** Enter and Space both press a button.\n- **Each button is a tab stop (a place the Tab key lands), in the order the buttons appear on screen.** A persona using a keyboard must reach the primary button without tabbing through the whole page.\n- **Never show an action, label, or value the persona needs only on hover.** Show every action, or put the action in a menu the persona can reach. A hover action appears only while the pointer is over a table row or list item. Personas using a keyboard or touch cannot reach a hover action.\n- **When a button opens a modal or a menu, move focus into the modal or menu.** When the modal or menu closes, return focus to the button. If focus is not returned, focus can go to the top of the page. A persona using a keyboard then has to tab through the whole page to get back to the button.\n- **When a button does not open a modal or a menu, leave focus on the button after a press.** The persona can then press the button again.\n- **A loading button is disabled.** A disabled button cannot receive focus and leaves the tab order. Nothing has focus while the action runs.\n- **The animated icon follows the persona's reduced-motion preference** (a setting that asks for less animation).\n\n## Styling set by tokens\n\n**Never set or override the button's styling.** Do not add extra containers or spacers to change the button's look. If the design needs a look the theme does not give, report the missing look as a design-system gap. The theme sets every visual property of the button, such as size, spacing, borders, colors and animation. See `recursica-skill-design-router`.\n\n## Related skills\n\n- `recursica-skill-buttons-links` — button versus link, label wording, button hierarchy and placement. The skill also covers confirming destructive actions, toggles, row actions, bulk actions, and buttons that open a modal.\n- `recursica-skill-undo` — when an action gets an undo, and where the Undo button goes.\n- `recursica-skill-forms` — what submit and cancel buttons do, the form's save mode, and where the form footer goes.\n- `recursica-skill-design-system-conventions` — showing meaning in more than one way, and changing the screen's structure instead of shrinking controls to fit.\n\n## Open questions\n\n- **When to use the smaller size.** No rule says which screens use the smaller size.\n- **Full-width buttons.** When the theme has no full-width option, no rule says whether a full-width button is ever allowed, or where.\n- **The icon for a loading button.** A loading button uses the theme's loading state, or the disabled look with an animated icon. That part is settled. Which icon to use is not settled. Whether the UI kit or the adapter (the Recursica component library for one framework, such as Mantine or Angular Material) defines the animation is also unknown.\n- **Split buttons and button groups.** Use a split button or a button group only when the theme has that component. Never build either one from separate buttons.\n- **Setting the disabled state.** Nobody has confirmed that each adapter offers the disabled state as a setting. Check the button's settings with the knowledge MCP server, or confirm with the user, before relying on the disabled state.\n\n## Pre-flight checklist\n\n- [ ] No button goes to a different page or URL.\n- [ ] Every label is a verb and an object, and says what the button does without the text around the button.\n- [ ] Any count is in parentheses after label words that do not change, and no count appears at zero.\n- [ ] The accessible name spells out the count, as in \"Apply status to 102 items\", while the label shows the count in parentheses.\n- [ ] Each page, panel, or modal has exactly one button in the primary style.\n- [ ] Every icon-only button has a tooltip and an accessible name.\n- [ ] Every button is a real `button` element, is in the tab order, and works with Enter and Space.\n- [ ] No action appears only on hover.\n- [ ] Every row action names the object, or gets the object from the row.\n- [ ] Focus returns to the button when a modal or menu that the button opened closes.\n- [ ] A loading button shows the theme's loading state, or the disabled look with an animated icon. The loading button has no spinner beside the button, no new label and no new state. The loading button does not move or resize.\n- [ ] A loading button is disabled, marked busy, and keeps the accessible name.\n- [ ] A loading button follows the persona's reduced-motion preference.\n- [ ] Every variant, size, and state is one the theme's UI kit lists, and no variant or option is invented.\n- [ ] No styling is set or overridden on the button.\n- [ ] No container or spacer is added to change the button's look.\n- [ ] The focus ring comes from the button component.\n- [ ] Actions the persona has no permission for are hidden, not disabled.\n- [ ] Open questions were asked about, not decided: when to use the smaller size, full-width buttons, the icon for a loading button, split buttons and button groups, and setting the disabled state.\n","# Button\n\nA button performs an action, such as saving a form or deleting a record. A button never takes the persona to a different page or URL.\n\n## When to use a button\n\n- The action saves, submits, deletes, applies a change, or opens a modal.\n- The persona stays on the same page after the action.\n- The action moves a process forward or back, such as Next and Back in a stepper. Next and Back change the step, not the page.\n\n## When not to use a button\n\n| Situation                                                                         | Use instead                                                                                                    |\n| --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |\n| Clicking goes to a different page or URL                                          | A link, with a real `href`. See `recursica-skill-link`.                                                        |\n| A table row opens a related record, such as the customer on an order              | A link. A link has less visual weight than a button. A dense table needs less visual weight in each table row. |\n| The persona chooses one of two to five options, such as a view, like List or Grid | A segmented control. See `recursica-skill-segmented-control`.                                                  |\n| The persona turns a setting on or off, such as email alerts                       | A switch or a checkbox. See `recursica-skill-selection-controls`.                                              |\n| A table row has more action buttons than the table row has room for               | Fewer actions in the table row, not smaller buttons. See `recursica-skill-tables`.                             |\n\n**Never use a button to go to a different page or URL.** For example, \"View order\" opens the order's page, so \"View order\" is a link.\n\n- If clicking a control changes the URL, build the control as a link, even when the design shows a button.\n- If a control that goes to a different page needs less visual weight, use a link. Never use a button in the text style instead. A link has less visual weight than a button.\n\nUsing a button to go to a different page is the most common misuse of buttons.\n\n## Variants\n\n**Use only the button variants and options that the knowledge MCP server lists for the theme (the design a designer sets in Theme Forge: the token values, the components, and each component's variants, states and sizes).** Get the list with the server's `component_api` tool. Use the names the code uses. Never invent a variant or an option. Each theme can differ, because a designer can add variants and options in Theme Forge.\n\nThe rules below describe each option by role, such as \"the primary style\". The names in the standard UI kit (the unchanged UI kit in the official Recursica release) are examples only.\n\n- **Style.** Use the primary style for the main action, such as \"Save invoice\". Use the secondary style for the next most important action. Use the least prominent style for every other action. In the standard UI kit, the styles are `solid`, `outline` and `text`. The `text` style is also called \"Ghost\".\n- **Size.** A button has a default size and a smaller size. The standard UI kit calls the smaller size `small`.\n- **Content.** A button shows a label alone, an icon with a label, or an icon alone. The same variant puts an icon before the label, after the label, or on both sides of the label.\n- **Disabled state.** How to turn on the disabled state is an open question.\n- **Destructive action.** If the theme has a destructive style, use the destructive style. Color alone cannot mark a destructive action (an action that deletes data or cannot be undone).\n  - Name the destructive action in the label, as in \"Delete invoice\".\n  - Confirm an action only when the action is massively destructive, hard to recreate, and cannot be undone. See `recursica-skill-undo`.\n- **Loading.** A loading button is a button whose action is still running, such as \"Save invoice\" while the save runs. If the theme has a loading state, use the loading state. Otherwise, show the loading button in the disabled look. Give the loading button an animated icon, with or without a label.\n  - Never add a spinner beside the button.\n  - Never change the label.\n  - Never invent a state.\n- **Success.** If the theme has a success state, use the success state. Otherwise, show any confirmation of a finished action outside the button, such as \"Invoice saved\" in a toast. See `recursica-skill-toast`.\n- **Width.** If the theme has a full-width option, use the full-width option. Otherwise, never stretch a button to fill the container the button sits in, such as a card.\n\n## Rules\n\n**Write the label as a verb and an object.** Write \"Save page\", not \"OK\". Write \"Delete invoice\", not \"Yes\". The label alone must say what the button does. A screen reader often reads the label without the text around the button.\n\n**Use one primary button per page, panel, or modal.** For example, a modal that edits an invoice has one primary button, \"Save invoice\".\n\n- The primary button uses the primary style.\n- The button for the next most important action uses the secondary style.\n- Every other button uses the least prominent style.\n- No other button in the same page, panel, or modal uses the primary style.\n\n**Put action buttons at the bottom right of a form footer or a modal footer.** Put the primary button last in reading order. For example, a modal footer shows \"Cancel\", then \"Save invoice\" at the far right. `recursica-skill-buttons-links` sets this rule.\n\n**Give every icon-only button a tooltip and an accessible name** (the name a screen reader reads out for a control). For example, a trash-can icon button gets the tooltip and the accessible name \"Delete invoice\". The tooltip is for sighted personas using a mouse. A screen reader does not read the tooltip unless the tooltip text is also the accessible name.\n\n**Show a count in parentheses after the label, never in place of the label.** For example, a button that sets the status of selected items reads `Apply status`, then `Apply status (1)`, then `Apply status (102)`.\n\n- The label words stay the same, and only the number changes.\n- Never build the number into the label words, as in `Apply 102 statuses`.\n- Never change the label words between one item and many items.\n\n**Show no count when no item is selected.** Never show `(0)`.\n\n- Add the count when the persona selects the first item.\n- Remove the count when the last selected item is cleared.\n\nA zero only repeats what the persona can already see. A zero also makes the button look as if an item is selected.\n\n**Label a toggle button with the button's current state.** \"Follow\" becomes \"Following\" after the persona presses Follow.\n\n**While a submit action runs, show the submit button as a disabled button with a spinner.** `recursica-skill-forms` requires a disabled button with a spinner. If the theme has a loading state, use the loading state. Otherwise, build the disabled button with a spinner from the disabled state and an icon, with or without a label. Animate the icon. Keep the button the same size and in the same place. A button that moves or resizes is no longer under the persona's pointer.\n\n**Never use the smaller size to fit more side-by-side buttons**, in a toolbar, a footer, or a table row. Change the screen's structure instead of shrinking the buttons. Too many buttons side by side means the screen offers too many actions. See `recursica-skill-design-system-conventions`.\n\n**Hide a button the persona has no permission to use.** Never show the button disabled instead. For example, a persona who cannot delete invoices sees no \"Delete invoice\" button. See `recursica-skill-navigation`.\n\n## Accessibility\n\nThe rules below add to the accessibility baseline in `recursica-skill-design-system-conventions`, which every Recursica component follows.\n\nThe button component shows the focus ring. The button component also responds to a press by click and by keyboard. The application must add every behavior in the two lists below.\n\n### Screen readers\n\n- **Give every button an accessible name.** Set the accessible name explicitly on an icon-only button. A screen reader does not read the icon. A button with no accessible name is read only as \"button\".\n- **The accessible name should match the visible label.** When the accessible name and the label differ, the accessible name must still contain the label. A persona using voice control presses a button by saying the label.\n- **Name the object in an action button in a table row or a list.** Put the object in the accessible name, as in \"Delete invoice 1043\". Or, in the code, set the object on the row as context for the button. A table of thirteen rows might show \"Delete\" in every table row. A screen reader then announces \"Delete\" thirteen times, with nothing to tell the rows apart.\n- **Update the accessible name when a toggle button's label changes.** An accessible name that is out of date after a press is worse than no accessible name.\n- **Spell out the count in the accessible name.** The label shows `Apply status (102)`, and the screen reader says \"Apply status to 102 items.\" A bare number after the label, as in \"Apply status 102\", is unclear when heard. The number could be a quantity, an ID, or part of the name.\n- **The count is the one allowed case where the accessible name and the label differ.** The count still follows the rule that the accessible name must contain the label. The accessible name keeps the label words. A persona using voice control can still say \"Apply status\".\n- **Update the accessible name as the count changes.** With no item selected, the accessible name is `Apply status`, with no count. Do not announce every increase in the count while the persona selects items. The accessible name must be correct by the time the persona reaches the button.\n- **Use a real `button` element**, never a `div` or a `span` with a click handler. A screen reader announces only a real `button` element as a button. Only a real `button` element responds to Enter and Space by default.\n- **Put the meaning in the accessible name, not only in the icon.** A screen reader announces the accessible name of an icon-only button and nothing about the icon. `recursica-skill-design-system-conventions` requires every meaning to be shown in more than one way.\n- **Mark a loading button as busy, and hide the animated icon from screen readers.** The animation is visual only. Without the busy state, a persona using a screen reader hears nothing and presses the button again.\n- **Keep the accessible name while the button is busy**, or change the accessible name to another useful name, such as \"Saving\". Never leave the accessible name empty.\n\n### Keyboard and non-mouse navigation\n\n- **Do not intercept, remap, or block Enter or Space on a button.** Enter and Space both press a button.\n- **Each button is a tab stop (a place the Tab key lands), in the order the buttons appear on screen.** A persona using a keyboard must reach the primary button without tabbing through the whole page.\n- **Never show an action, label, or value the persona needs only on hover.** Show every action, or put the action in a menu the persona can reach. A hover action appears only while the pointer is over a table row or list item. Personas using a keyboard or touch cannot reach a hover action.\n- **When a button opens a modal or a menu, move focus into the modal or menu.** When the modal or menu closes, return focus to the button. If focus is not returned, focus can go to the top of the page. A persona using a keyboard then has to tab through the whole page to get back to the button.\n- **When a button does not open a modal or a menu, leave focus on the button after a press.** The persona can then press the button again.\n- **A loading button is disabled.** A disabled button cannot receive focus and leaves the tab order. Nothing has focus while the action runs.\n- **The animated icon follows the persona's reduced-motion preference** (a setting that asks for less animation).\n\n## Styling set by tokens\n\n**Never set or override the button's styling.** Do not add extra containers or spacers to change the button's look. If the design needs a look the theme does not give, report the missing look as a design-system gap. The theme sets every visual property of the button, such as size, spacing, borders, colors and animation. See `recursica-skill-design-router`.\n\n## Related skills\n\n- `recursica-skill-buttons-links` — button versus link, label wording, button hierarchy and placement. The skill also covers confirming destructive actions, toggles, row actions, bulk actions, and buttons that open a modal.\n- `recursica-skill-undo` — when an action gets an undo, and where the Undo button goes.\n- `recursica-skill-forms` — what submit and cancel buttons do, the form's save mode, and where the form footer goes.\n- `recursica-skill-design-system-conventions` — showing meaning in more than one way, and changing the screen's structure instead of shrinking controls to fit.\n\n## Open questions\n\n- **When to use the smaller size.** No rule says which screens use the smaller size.\n- **Full-width buttons.** When the theme has no full-width option, no rule says whether a full-width button is ever allowed, or where.\n- **The icon for a loading button.** A loading button uses the theme's loading state, or the disabled look with an animated icon. That part is settled. Which icon to use is not settled. Whether the UI kit or the adapter (the Recursica component library for one framework, such as Mantine or Angular Material) defines the animation is also unknown.\n- **Split buttons and button groups.** Use a split button or a button group only when the theme has that component. Never build either one from separate buttons.\n- **Setting the disabled state.** Nobody has confirmed that each adapter offers the disabled state as a setting. Check the button's settings with the knowledge MCP server, or confirm with the user, before relying on the disabled state.\n\n## Pre-flight checklist\n\n- [ ] No button goes to a different page or URL.\n- [ ] Every label is a verb and an object, and says what the button does without the text around the button.\n- [ ] Any count is in parentheses after label words that do not change, and no count appears at zero.\n- [ ] The accessible name spells out the count, as in \"Apply status to 102 items\", while the label shows the count in parentheses.\n- [ ] Each page, panel, or modal has exactly one button in the primary style.\n- [ ] Every icon-only button has a tooltip and an accessible name.\n- [ ] Every button is a real `button` element, is in the tab order, and works with Enter and Space.\n- [ ] No action appears only on hover.\n- [ ] Every row action names the object, or gets the object from the row.\n- [ ] Focus returns to the button when a modal or menu that the button opened closes.\n- [ ] A loading button shows the theme's loading state, or the disabled look with an animated icon. The loading button has no spinner beside the button, no new label and no new state. The loading button does not move or resize.\n- [ ] A loading button is disabled, marked busy, and keeps the accessible name.\n- [ ] A loading button follows the persona's reduced-motion preference.\n- [ ] Every variant, size, and state is one the theme's UI kit lists, and no variant or option is invented.\n- [ ] No styling is set or overridden on the button.\n- [ ] No container or spacer is added to change the button's look.\n- [ ] The focus ring comes from the button component.\n- [ ] Actions the persona has no permission for are hidden, not disabled.\n- [ ] Open questions were asked about, not decided: when to use the smaller size, full-width buttons, the icon for a loading button, split buttons and button groups, and setting the disabled state.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"hi@borderux.com","0.2.0","main","110b382bfe525d171ba33c7074d6ad1f3762548f","skills\u002Fcomponents\u002Frecursica-skill-button",0,"https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge","https:\u002F\u002Fgithub.com\u002Fborderux","https:\u002F\u002Fborderux.com","2026-11-09 16:39:27",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-button",{"tool":41,"command":42},"bunx","bunx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-button",{"tool":44,"command":45},"pnpm","pnpm dlx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-button","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fcomponents\u002Frecursica-skill-button\u002FSKILL.md",true,[],[50,58,65,72,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7556E67F3DCE39P7ZTVT5TA","recursica-skill-template","Replace with a description of the skill and its purpose.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Ftemplate\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M75569FCJXWWGXRVMTJFBK0W","recursica-skill-working-memory","The research behind Recursica's item-count limits, with citations — Miller's 7 ± 2, Cowan's 4, chunking, and recognition versus recall. Use when a decision turns on how many options, navigation items, or chips to show at once, or to justify or challenge a count. Not for choosing a control — see recursica-skill-selection-controls.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fpsychology\u002Frecursica-skill-working-memory\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M75564EC5E5QKBPNWARQVDBC","recursica-skill-discoverability","The research behind Recursica's rule that rarely needed settings get a real but unpromoted entry point — the paradox of the active user, satisficing (settling for the first method that is good enough), and progressive disclosure, with citations. Use when deciding whether to hide, promote, or build a configuration or customization feature, or to justify that choice. Not for item counts — see recursica-skill-working-memory.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fpsychology\u002Frecursica-skill-discoverability\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7555Z2YRG9YSM01KMYT1FY5","recursica-skill-design-router","Start here for any Recursica screen work. The router says what to decide in what order, which skill owns each decision, which rule wins when two rules conflict, and when to confirm with the user instead of guessing. Load the router first to design, build, review, or refactor a screen, page, panel, or flow, or when rules seem to disagree or no rule applies. The router routes, and the owning skill holds the rules.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fmeta\u002Frecursica-skill-design-router\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7555RYHBH6XM48V2420Z66X","recursica-skill-undo","House rules for undo — when an action gets an undo instead of a confirmation, where the undo goes (on the page, in place, or in a toast), when a toast is needed at all, and the Undo button's accessible name. Use whenever an action can be reversed, or when choosing between an undo and a confirmation. Not for building the toast that holds an Undo button — see recursica-skill-toast. Not for the confirmation modal — see recursica-skill-buttons-links.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-rules\u002Frecursica-skill-undo\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7555K4E6TKJ9E9P7GCQYJZ8","recursica-skill-typography-semantics","House rules for type and semantic markup — real elements instead of styled divs, one H1 per page, type styles from tokens only, loading the brand typefaces, hidden headings, emphasis with em and strong, abbreviations, and AP style. Use for headings, body copy, emphasis, and the markup under a visual hierarchy. Not for naming — see recursica-skill-names-and-terms.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-rules\u002Frecursica-skill-typography-semantics\u002FSKILL.md",[],[]]