[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754Z8KFGSTMZ32ERQYFRWY3":3,"skill-same:01M754Z8KFGSTMZ32ERQYFRWY3":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},"01M754Z8KFGSTMZ32ERQYFRWY3","recursica-skill-number-input",null,"Rules for the Recursica number input — quantity versus digit string, right alignment and fixed precision, units and currency in the label or as affixes, stating limits up front, and numeric-field accessibility. Use for quantities and amounts. Not for free text — see recursica-skill-text-field; formatting rules live in recursica-skill-dates-and-currency.","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-number-input\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: recursica-skill-number-input\ndescription: Rules for the Recursica number input — quantity versus digit string, right alignment and fixed precision, units and currency in the label or as affixes, stating limits up front, and numeric-field accessibility. Use for quantities and amounts. Not for free text — see recursica-skill-text-field; formatting rules live in recursica-skill-dates-and-currency.\nlicense: MIT\nmetadata:\n  author: hi@borderux.com\n  version: 0.2.0\n---\n\n# Number input\n\nA number input records a quantity that the persona types.\n\n## When to use a number input\n\n- **Use a number input when the value is a quantity.** A quantity is a count, an amount, a rate or a measurement. For example, a number of seats, a price, an interest rate or a weight. Adding, subtracting or averaging a quantity makes sense.\n- **Use a number input when the persona knows the number, and the range is open-ended or too wide to list.** For example, a number of seats with no upper limit.\n- **Use a number input when precision matters.** The persona needs the exact value, such as a payment of 1,250.00, not a rough value.\n\n## When not to use a number input\n\n**In each situation below, use the component in the right column.** Do not change a number input to fit the situation.\n\n| Situation                                            | Use instead                                                                                                                       |\n| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |\n| The number comes from a short, fixed list of options | A radio group or a dropdown. See `recursica-skill-selection-controls`.                                                            |\n| The exact value does not matter across a large range | A slider. The persona chooses a position on the range, not a number. See `recursica-skill-slider`.                                |\n| The digits are an identifier, not a quantity         | A text field. Phone numbers, ZIP codes, account numbers and card numbers are text, not numbers. See `recursica-skill-text-field`. |\n| The value is a length of time                        | One field for each unit of time, formatted as `3h 20m`. See `recursica-skill-dates-and-currency`.                                 |\n| The value is a date or a time                        | A date picker or a time picker. See `recursica-skill-date-picker` or `recursica-skill-time-picker`.                               |\n| Nobody can ever edit the value in this place         | A read-only field, which shows the label and the text with no input. See `recursica-skill-read-only-field`.                       |\n\n**A value with a leading zero, a fixed number of digits, or a check digit is not a number.** Use a text field for every value where `007` and `7` are different values.\n\n**Do not use a disabled number input to show a value.** When nobody can ever edit a value in this place, the value does not belong in a form control.\n\n## Variants\n\n**Use only the number input 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).** A designer can add variants and options in Theme Forge, so each theme can differ. Never invent a variant or an option.\n\n**Look up the name the code uses for each variant before using the variant.** Get the list with the server's `component_api` tool, and use the names the code uses. The name in code can differ from the name in Figma and the UI kit. A wrong name in code has no effect and shows no error.\n\nEach option below is described by role, such as \"the error state\". A name from the standard UI kit (the unchanged UI kit in the official Recursica release) is only an example.\n\n- **The number input has an error state and a disabled state.** In the standard UI kit, the state variant is `states`, with the options `error` and `disabled`.\n- **If the theme has a size variant, use the size variant.**\n- **If the theme has a stepper, use the theme's stepper.** The same rule applies to two more options:\n\n  - If the theme has a collapsed or expanded state, use the theme's state.\n  - If the theme has a content variant, use the theme's content variant.\n\n  If the theme has none of the three, do not describe the number input as having increase and decrease buttons. Do not build increase and decrease buttons from buttons placed beside the field. See the open questions.\n\n- **A read-only field is a separate component, not a state of the number input.** A read-only field shows a label and text, with no input. The standard UI kit calls the read-only field `read-only-field`. A read-only field has the same label-placement variant as the number input.\n\n**Label placement is a variant.** A field's label sits beside the field or above the field. In the standard UI kit, the variant is `layouts`, with the options `side-by-side` and `stacked`. The label beside the field is the house default. The label above the field is the fallback when the form's container is too narrow for both side by side. The container's width decides, not the viewport's width. See `recursica-skill-forms`.\n\n**Set label placement explicitly on every field.** The house rule puts the label beside the input. The code library under an adapter may put the label above the input by default, at every container width. Set the label beside the input on every field. Use the names the code uses for the variant and the option.\n\n**Never build a focus state or a placeholder state.** Every Recursica field already shows the focus border and the placeholder text.\n\n## Rules\n\n**Always give the number input a visible label.** The label names the object the number counts or measures, such as \"Seats\". When the object does not make the unit obvious, the label also names the unit: \"Weight (kg)\", not \"Weight\". A persona using a screen reader hears the label without the text around the field.\n\n**Label placement is one decision per form, not per field.** This field uses the same label placement as every other field in the form. Apply the container-width test once, to the whole form. The result sets the placement of every field in the form. Short fields like this one that would fit side by side follow the result too. A form may change placement at a breakpoint. A form never mixes placements at one breakpoint. A form section never gets a separate placement. `recursica-skill-forms` sets this rule.\n\n**Right-align the value.** Right-align every number, whether or not the number is currency. Every number then lines up the same way. Use a different alignment only when the user explicitly asks for a different alignment. On an existing screen that is left-aligned throughout, confirm with the user which alignment the whole screen uses.\n\n**Keep the number of decimal places fixed.**\n\n- Currency always shows two decimal places, as in `0.00`, `0.01`, and `0.99`.\n- Numbers shown together keep the same number of decimal places: `4.5` and `7.0`, never `4.5` and `7`.\n\nWith a fixed number of decimal places, the decimal points of right-aligned numbers line up.\n\n**Read-only values and editable values on the same screen must use the same alignment.** A left-aligned read-only value next to a right-aligned editable value looks like the two values come from two different systems.\n\n**Name the unit or the currency in the label by default, as in \"Weight (kg)\".** Show the unit as an affix only when the user asks for an affix. An affix is text attached to the start or end of the field, such as \"$\" or \"kg\".\n\n- With an affix, put the currency symbol before the value, and the unit after the value.\n- Do not join the currency symbol or unit onto the value.\n- If several amounts appear in one column, put the currency symbol in the column header instead.\n\nSee `recursica-skill-dates-and-currency`.\n\n**State the minimum, the maximum, and the step between allowed values in the help text below the field.** For example: \"Enter 0 to 100, in steps of 5.\" Show the limits before the persona can type a value that breaks the limits. Preventing an error is better than catching the error.\n\n**Zero is a value, and an empty field is not zero.** Do not pre-fill `0` to avoid an empty field. A submitted zero states that the value is zero.\n\n**Do not pre-fill a number the persona would have to think about, look up, or check.** For example, do not pre-fill a tax rate the persona would have to look up. A pre-filled number that the persona cannot check gets submitted without a check. A pre-filled number that nobody checked is worse than an empty field.\n\n**On error, the error message replaces the help text.** Do not show the error message in addition to the help text. Replacing the help text keeps the field the same height, and the form below the field does not move.\n\n**The error message must restate the rule.** Write \"Enter a whole number between 1 and 99\", not \"Invalid number\".\n\n**Pair the error state with a signal that is not color**, either an icon or the error message. `recursica-skill-design-system-conventions` requires a signal that is not color.\n\n**Never quietly correct the value the persona typed, or force the typed value into the allowed range.** For example, when the maximum is 99 and the persona types 150, do not change 150 to 99. Show the error, and let the persona fix the value. Rewriting a value when the field loses focus destroys the persona's input without telling the persona.\n\n**A disabled number input and a read-only field are different components, not two styles of one component.**\n\n- **Use a disabled number input when the persona could make the field usable by taking a different action first.** For example, a quantity field stays disabled until the persona picks a product. A disabled number input is still a field and still clearly an input. The persona cannot use the disabled field right now.\n- **Use a read-only field when the persona viewing the field never edits the value in this place.** A read-only field is a different component, with a label and text and no input.\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 number input component connects the label to the input and shows the focus ring. The application provides the unit, the limits, and every control inside the field.\n\n### Screen readers\n\n- **Give the field a label, not only placeholder text.** Never let the placeholder text be the accessible name (the name a screen reader reads out for a control). A screen reader does not announce placeholder text as a label. The placeholder text also disappears when the persona types. A field with no label has no accessible name.\n- **State the unit in text, in the label or in the help text.** A screen reader may not announce an affix with the value. A currency symbol in a column header is not connected to the field at all. A persona who hears \"1000\" with no unit does not know what the number means.\n- **State the expected format, the minimum, and the maximum in the help text.** Describe in words the thousands separators, the decimal places, and whether negative numbers are allowed. A mask (a pattern that guides what the persona types) tells a screen reader nothing. Right alignment with two decimal places also tells a screen reader nothing.\n- **Give an accessible name to every icon inside the field that the persona can use.** Examples are a control that clears the field, and a stepper button if the theme ever adds a stepper. Hide every decorative icon from screen readers. A screen reader must never announce a decorative icon as an unlabeled graphic.\n- **If the field limits the range, give assistive technology the current value, the minimum, and the maximum.** A persona using a screen reader then knows the maximum.\n- **A screen reader announces the error message.** The error message replaces the help text, and a screen reader reads only the error message. The error message must state the rule and the limits.\n\n### Keyboard and non-mouse navigation\n\n- **Never remove the field from the tab order.** Never make a pointer, such as a mouse, the only way to reach the field.\n- **Typing is always enough to enter the value.** A persona must be able to enter the value by typing alone. A stepper button or any other adjustment control is only a shortcut. A persona never has to press a button forty times.\n- **Every control inside the field is a separate tab stop** (a place the Tab key lands). Every control inside the field works with Enter or Space, not only with a mouse click.\n- **Do not move focus for the persona.** Do not jump focus ahead when the value reaches a set number of digits, such as four digits. Do not jump focus on any keystroke. A focus jump sends the persona's next keystrokes to a different field.\n- **Never let a scroll wheel or an accidental arrow key press change a saved value.** The rule applies while the field has focus and the persona is only reading. Never take over the arrow keys that the persona needs to move the caret.\n- **Keep every part the persona needs to complete the field visible without hover.** The parts include the limits, the unit, and any adjustment control.\n\n## Styling set by tokens\n\n**Never set or override the number input's styling.** The theme sets every visual property of the number input, such as size, spacing, borders, colors and animation. Do not add extra containers or spacers to change the number input's look. If the theme does not give a look the design needs, report the missing look as a design-system gap. See `recursica-skill-design-router`.\n\n**Never set or override the link between the label and the input, or what each key does inside the field.** The number input component sets both.\n\n**Never style a number input without focus to look disabled.** An editable number input must look editable when the persona is not using the number input.\n\n## Related skills\n\n- `recursica-skill-dates-and-currency` — the number-formatting rules:\n  - right alignment\n  - two decimal places for currency\n  - the same precision across values\n  - the currency symbol in the column header\n  - accounting parentheses\n  - ranges\n  - rounding\n  - abbreviation\n- `recursica-skill-forms` — the form rules:\n  - label placement and one placement per form\n  - when validation runs\n  - pre-filled values and defaults\n  - the form's save mode\n  - the rule that no form control goes inside a card\n- `recursica-skill-label` — the label component, the label-placement variant, and required and optional markers.\n- `recursica-skill-assistive-element` — the help text and error text below the field, and why the error text replaces the help text.\n- `recursica-skill-design-system-conventions` — showing every meaning in more than one way.\n\n### Only if used on the same screen\n\n- `recursica-skill-slider` — the control for an approximate value across a range.\n- `recursica-skill-text-field` — the control for digits that are not quantities.\n\n## Open questions\n\n- **Increase and decrease controls.** Only the design-system website shows increase and decrease controls. The user must decide whether the number input ever gets a stepper, and what the stepper's step would be. Do not rely on a stepper without confirming with the user. Confirm with the user only when the theme has no stepper.\n- **Collapsed and expanded states.** Only the design-system website shows a `collapsed` state and an `expanded` state. The two states seem to describe whether a stepper is visible. Do not build either state, and do not rely on either state without confirming with the user. Confirm with the user only when the theme has no collapsed and expanded states.\n- **A content variant.** Only the design-system website shows a content variant, with the options `unvalued`, `unvalued with placeholder`, and `valued`. No rule says whether a number input should show a placeholder at all. Do not rely on the content variant without confirming with the user. Confirm with the user only when the theme has no content variant.\n- **Formatting while the persona types.** No rule says whether the field formats the value while the persona types, or only when the field loses focus. Adding thousands separators is one example of formatting.\n- **Negative values.** No rule says whether a number input ever uses the accounting parentheses from `recursica-skill-dates-and-currency`. The other choice is to use the parentheses only for a value shown outside an input.\n- **Choosing the unit.** No pattern exists for a value whose unit the persona can switch, such as kg or lb.\n\n## Pre-flight checklist\n\n- [ ] The value is a quantity, not an identifier, a length of time, or a position on a range.\n- [ ] The field has a visible label. The label names the object, and names the unit when the object does not make the unit obvious.\n- [ ] Label placement is side by side, unless the container is too narrow.\n- [ ] Label placement is set explicitly on every field, to side by side unless the form's container is too narrow. The setting uses the names the code uses, looked up with `component_api`. A field with no setting gets the label above the field (`stacked`), not the house rule.\n- [ ] Label placement matches every other field in the same form. Each form has one placement at each breakpoint, with no mixing between fields or form sections.\n- [ ] The value is right-aligned, and the alignment matches the read-only values on the same screen.\n- [ ] Precision is fixed, and the same across every value shown together. Currency has two decimal places.\n- [ ] The label names the unit or the currency, unless the user asked for an affix.\n- [ ] An affix unit or currency is also stated in the label or the help text.\n- [ ] The help text states the minimum, the maximum, the step, and the expected format.\n- [ ] The field is not pre-filled with `0` to avoid an empty field. The field holds no default the persona would have to understand to check.\n- [ ] Help text and error text are set through the number input component. The error text replaces the help text, and restates the rule and the limits.\n- [ ] The error state has a signal that is not color, and no value is quietly forced into range or rewritten.\n- [ ] Every icon inside the field that the persona can use has an accessible name. Every decorative icon is hidden from screen readers.\n- [ ] Typing alone can enter any valid value. Any adjustment control is only a shortcut, and is a separate tab stop.\n- [ ] The arrow keys and the scroll wheel do not change the value unexpectedly.\n- [ ] Every variant, size, and state is one the knowledge MCP server lists for the theme. No variant or option is invented. No stepper is built unless the knowledge MCP server lists a stepper for the theme.\n- [ ] No styling is set or overridden on the number input. No container or spacer is added to change the number input's look.\n- [ ] A number input without focus looks editable.\n- [ ] Numbers that are not editable here use the read-only field, not a disabled number input.\n- [ ] Open questions were asked about, not decided: increase and decrease controls, the `collapsed` and `expanded` states, a content variant, formatting as the persona types, negative values, and choosing the unit.\n","# Number input\n\nA number input records a quantity that the persona types.\n\n## When to use a number input\n\n- **Use a number input when the value is a quantity.** A quantity is a count, an amount, a rate or a measurement. For example, a number of seats, a price, an interest rate or a weight. Adding, subtracting or averaging a quantity makes sense.\n- **Use a number input when the persona knows the number, and the range is open-ended or too wide to list.** For example, a number of seats with no upper limit.\n- **Use a number input when precision matters.** The persona needs the exact value, such as a payment of 1,250.00, not a rough value.\n\n## When not to use a number input\n\n**In each situation below, use the component in the right column.** Do not change a number input to fit the situation.\n\n| Situation                                            | Use instead                                                                                                                       |\n| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |\n| The number comes from a short, fixed list of options | A radio group or a dropdown. See `recursica-skill-selection-controls`.                                                            |\n| The exact value does not matter across a large range | A slider. The persona chooses a position on the range, not a number. See `recursica-skill-slider`.                                |\n| The digits are an identifier, not a quantity         | A text field. Phone numbers, ZIP codes, account numbers and card numbers are text, not numbers. See `recursica-skill-text-field`. |\n| The value is a length of time                        | One field for each unit of time, formatted as `3h 20m`. See `recursica-skill-dates-and-currency`.                                 |\n| The value is a date or a time                        | A date picker or a time picker. See `recursica-skill-date-picker` or `recursica-skill-time-picker`.                               |\n| Nobody can ever edit the value in this place         | A read-only field, which shows the label and the text with no input. See `recursica-skill-read-only-field`.                       |\n\n**A value with a leading zero, a fixed number of digits, or a check digit is not a number.** Use a text field for every value where `007` and `7` are different values.\n\n**Do not use a disabled number input to show a value.** When nobody can ever edit a value in this place, the value does not belong in a form control.\n\n## Variants\n\n**Use only the number input 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).** A designer can add variants and options in Theme Forge, so each theme can differ. Never invent a variant or an option.\n\n**Look up the name the code uses for each variant before using the variant.** Get the list with the server's `component_api` tool, and use the names the code uses. The name in code can differ from the name in Figma and the UI kit. A wrong name in code has no effect and shows no error.\n\nEach option below is described by role, such as \"the error state\". A name from the standard UI kit (the unchanged UI kit in the official Recursica release) is only an example.\n\n- **The number input has an error state and a disabled state.** In the standard UI kit, the state variant is `states`, with the options `error` and `disabled`.\n- **If the theme has a size variant, use the size variant.**\n- **If the theme has a stepper, use the theme's stepper.** The same rule applies to two more options:\n\n  - If the theme has a collapsed or expanded state, use the theme's state.\n  - If the theme has a content variant, use the theme's content variant.\n\n  If the theme has none of the three, do not describe the number input as having increase and decrease buttons. Do not build increase and decrease buttons from buttons placed beside the field. See the open questions.\n\n- **A read-only field is a separate component, not a state of the number input.** A read-only field shows a label and text, with no input. The standard UI kit calls the read-only field `read-only-field`. A read-only field has the same label-placement variant as the number input.\n\n**Label placement is a variant.** A field's label sits beside the field or above the field. In the standard UI kit, the variant is `layouts`, with the options `side-by-side` and `stacked`. The label beside the field is the house default. The label above the field is the fallback when the form's container is too narrow for both side by side. The container's width decides, not the viewport's width. See `recursica-skill-forms`.\n\n**Set label placement explicitly on every field.** The house rule puts the label beside the input. The code library under an adapter may put the label above the input by default, at every container width. Set the label beside the input on every field. Use the names the code uses for the variant and the option.\n\n**Never build a focus state or a placeholder state.** Every Recursica field already shows the focus border and the placeholder text.\n\n## Rules\n\n**Always give the number input a visible label.** The label names the object the number counts or measures, such as \"Seats\". When the object does not make the unit obvious, the label also names the unit: \"Weight (kg)\", not \"Weight\". A persona using a screen reader hears the label without the text around the field.\n\n**Label placement is one decision per form, not per field.** This field uses the same label placement as every other field in the form. Apply the container-width test once, to the whole form. The result sets the placement of every field in the form. Short fields like this one that would fit side by side follow the result too. A form may change placement at a breakpoint. A form never mixes placements at one breakpoint. A form section never gets a separate placement. `recursica-skill-forms` sets this rule.\n\n**Right-align the value.** Right-align every number, whether or not the number is currency. Every number then lines up the same way. Use a different alignment only when the user explicitly asks for a different alignment. On an existing screen that is left-aligned throughout, confirm with the user which alignment the whole screen uses.\n\n**Keep the number of decimal places fixed.**\n\n- Currency always shows two decimal places, as in `0.00`, `0.01`, and `0.99`.\n- Numbers shown together keep the same number of decimal places: `4.5` and `7.0`, never `4.5` and `7`.\n\nWith a fixed number of decimal places, the decimal points of right-aligned numbers line up.\n\n**Read-only values and editable values on the same screen must use the same alignment.** A left-aligned read-only value next to a right-aligned editable value looks like the two values come from two different systems.\n\n**Name the unit or the currency in the label by default, as in \"Weight (kg)\".** Show the unit as an affix only when the user asks for an affix. An affix is text attached to the start or end of the field, such as \"$\" or \"kg\".\n\n- With an affix, put the currency symbol before the value, and the unit after the value.\n- Do not join the currency symbol or unit onto the value.\n- If several amounts appear in one column, put the currency symbol in the column header instead.\n\nSee `recursica-skill-dates-and-currency`.\n\n**State the minimum, the maximum, and the step between allowed values in the help text below the field.** For example: \"Enter 0 to 100, in steps of 5.\" Show the limits before the persona can type a value that breaks the limits. Preventing an error is better than catching the error.\n\n**Zero is a value, and an empty field is not zero.** Do not pre-fill `0` to avoid an empty field. A submitted zero states that the value is zero.\n\n**Do not pre-fill a number the persona would have to think about, look up, or check.** For example, do not pre-fill a tax rate the persona would have to look up. A pre-filled number that the persona cannot check gets submitted without a check. A pre-filled number that nobody checked is worse than an empty field.\n\n**On error, the error message replaces the help text.** Do not show the error message in addition to the help text. Replacing the help text keeps the field the same height, and the form below the field does not move.\n\n**The error message must restate the rule.** Write \"Enter a whole number between 1 and 99\", not \"Invalid number\".\n\n**Pair the error state with a signal that is not color**, either an icon or the error message. `recursica-skill-design-system-conventions` requires a signal that is not color.\n\n**Never quietly correct the value the persona typed, or force the typed value into the allowed range.** For example, when the maximum is 99 and the persona types 150, do not change 150 to 99. Show the error, and let the persona fix the value. Rewriting a value when the field loses focus destroys the persona's input without telling the persona.\n\n**A disabled number input and a read-only field are different components, not two styles of one component.**\n\n- **Use a disabled number input when the persona could make the field usable by taking a different action first.** For example, a quantity field stays disabled until the persona picks a product. A disabled number input is still a field and still clearly an input. The persona cannot use the disabled field right now.\n- **Use a read-only field when the persona viewing the field never edits the value in this place.** A read-only field is a different component, with a label and text and no input.\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 number input component connects the label to the input and shows the focus ring. The application provides the unit, the limits, and every control inside the field.\n\n### Screen readers\n\n- **Give the field a label, not only placeholder text.** Never let the placeholder text be the accessible name (the name a screen reader reads out for a control). A screen reader does not announce placeholder text as a label. The placeholder text also disappears when the persona types. A field with no label has no accessible name.\n- **State the unit in text, in the label or in the help text.** A screen reader may not announce an affix with the value. A currency symbol in a column header is not connected to the field at all. A persona who hears \"1000\" with no unit does not know what the number means.\n- **State the expected format, the minimum, and the maximum in the help text.** Describe in words the thousands separators, the decimal places, and whether negative numbers are allowed. A mask (a pattern that guides what the persona types) tells a screen reader nothing. Right alignment with two decimal places also tells a screen reader nothing.\n- **Give an accessible name to every icon inside the field that the persona can use.** Examples are a control that clears the field, and a stepper button if the theme ever adds a stepper. Hide every decorative icon from screen readers. A screen reader must never announce a decorative icon as an unlabeled graphic.\n- **If the field limits the range, give assistive technology the current value, the minimum, and the maximum.** A persona using a screen reader then knows the maximum.\n- **A screen reader announces the error message.** The error message replaces the help text, and a screen reader reads only the error message. The error message must state the rule and the limits.\n\n### Keyboard and non-mouse navigation\n\n- **Never remove the field from the tab order.** Never make a pointer, such as a mouse, the only way to reach the field.\n- **Typing is always enough to enter the value.** A persona must be able to enter the value by typing alone. A stepper button or any other adjustment control is only a shortcut. A persona never has to press a button forty times.\n- **Every control inside the field is a separate tab stop** (a place the Tab key lands). Every control inside the field works with Enter or Space, not only with a mouse click.\n- **Do not move focus for the persona.** Do not jump focus ahead when the value reaches a set number of digits, such as four digits. Do not jump focus on any keystroke. A focus jump sends the persona's next keystrokes to a different field.\n- **Never let a scroll wheel or an accidental arrow key press change a saved value.** The rule applies while the field has focus and the persona is only reading. Never take over the arrow keys that the persona needs to move the caret.\n- **Keep every part the persona needs to complete the field visible without hover.** The parts include the limits, the unit, and any adjustment control.\n\n## Styling set by tokens\n\n**Never set or override the number input's styling.** The theme sets every visual property of the number input, such as size, spacing, borders, colors and animation. Do not add extra containers or spacers to change the number input's look. If the theme does not give a look the design needs, report the missing look as a design-system gap. See `recursica-skill-design-router`.\n\n**Never set or override the link between the label and the input, or what each key does inside the field.** The number input component sets both.\n\n**Never style a number input without focus to look disabled.** An editable number input must look editable when the persona is not using the number input.\n\n## Related skills\n\n- `recursica-skill-dates-and-currency` — the number-formatting rules:\n  - right alignment\n  - two decimal places for currency\n  - the same precision across values\n  - the currency symbol in the column header\n  - accounting parentheses\n  - ranges\n  - rounding\n  - abbreviation\n- `recursica-skill-forms` — the form rules:\n  - label placement and one placement per form\n  - when validation runs\n  - pre-filled values and defaults\n  - the form's save mode\n  - the rule that no form control goes inside a card\n- `recursica-skill-label` — the label component, the label-placement variant, and required and optional markers.\n- `recursica-skill-assistive-element` — the help text and error text below the field, and why the error text replaces the help text.\n- `recursica-skill-design-system-conventions` — showing every meaning in more than one way.\n\n### Only if used on the same screen\n\n- `recursica-skill-slider` — the control for an approximate value across a range.\n- `recursica-skill-text-field` — the control for digits that are not quantities.\n\n## Open questions\n\n- **Increase and decrease controls.** Only the design-system website shows increase and decrease controls. The user must decide whether the number input ever gets a stepper, and what the stepper's step would be. Do not rely on a stepper without confirming with the user. Confirm with the user only when the theme has no stepper.\n- **Collapsed and expanded states.** Only the design-system website shows a `collapsed` state and an `expanded` state. The two states seem to describe whether a stepper is visible. Do not build either state, and do not rely on either state without confirming with the user. Confirm with the user only when the theme has no collapsed and expanded states.\n- **A content variant.** Only the design-system website shows a content variant, with the options `unvalued`, `unvalued with placeholder`, and `valued`. No rule says whether a number input should show a placeholder at all. Do not rely on the content variant without confirming with the user. Confirm with the user only when the theme has no content variant.\n- **Formatting while the persona types.** No rule says whether the field formats the value while the persona types, or only when the field loses focus. Adding thousands separators is one example of formatting.\n- **Negative values.** No rule says whether a number input ever uses the accounting parentheses from `recursica-skill-dates-and-currency`. The other choice is to use the parentheses only for a value shown outside an input.\n- **Choosing the unit.** No pattern exists for a value whose unit the persona can switch, such as kg or lb.\n\n## Pre-flight checklist\n\n- [ ] The value is a quantity, not an identifier, a length of time, or a position on a range.\n- [ ] The field has a visible label. The label names the object, and names the unit when the object does not make the unit obvious.\n- [ ] Label placement is side by side, unless the container is too narrow.\n- [ ] Label placement is set explicitly on every field, to side by side unless the form's container is too narrow. The setting uses the names the code uses, looked up with `component_api`. A field with no setting gets the label above the field (`stacked`), not the house rule.\n- [ ] Label placement matches every other field in the same form. Each form has one placement at each breakpoint, with no mixing between fields or form sections.\n- [ ] The value is right-aligned, and the alignment matches the read-only values on the same screen.\n- [ ] Precision is fixed, and the same across every value shown together. Currency has two decimal places.\n- [ ] The label names the unit or the currency, unless the user asked for an affix.\n- [ ] An affix unit or currency is also stated in the label or the help text.\n- [ ] The help text states the minimum, the maximum, the step, and the expected format.\n- [ ] The field is not pre-filled with `0` to avoid an empty field. The field holds no default the persona would have to understand to check.\n- [ ] Help text and error text are set through the number input component. The error text replaces the help text, and restates the rule and the limits.\n- [ ] The error state has a signal that is not color, and no value is quietly forced into range or rewritten.\n- [ ] Every icon inside the field that the persona can use has an accessible name. Every decorative icon is hidden from screen readers.\n- [ ] Typing alone can enter any valid value. Any adjustment control is only a shortcut, and is a separate tab stop.\n- [ ] The arrow keys and the scroll wheel do not change the value unexpectedly.\n- [ ] Every variant, size, and state is one the knowledge MCP server lists for the theme. No variant or option is invented. No stepper is built unless the knowledge MCP server lists a stepper for the theme.\n- [ ] No styling is set or overridden on the number input. No container or spacer is added to change the number input's look.\n- [ ] A number input without focus looks editable.\n- [ ] Numbers that are not editable here use the read-only field, not a disabled number input.\n- [ ] Open questions were asked about, not decided: increase and decrease controls, the `collapsed` and `expanded` states, a content variant, formatting as the persona types, negative values, and choosing the unit.\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-number-input",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-number-input",{"tool":41,"command":42},"bunx","bunx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-number-input",{"tool":44,"command":45},"pnpm","pnpm dlx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-number-input","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fcomponents\u002Frecursica-skill-number-input\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",[],[]]