> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/components/form/inputstepper.md).
# Input Stepper
Component: A locked height form component for the collection of a three-segment (Input Stepper - Control) used to incrementally increase or decrease a numeric value. NN/g has a great definition of the control [here](https://www.nngroup.com/articles/input-steppers/#:~:text=Definition%3A%20An%20input%20stepper%20is,interfaces%20can%20also%20have%20steppers.). Inner element spacing is used for dynamic resizing along with a background surface.
[Styleguide Link](https://zpl.io/a8DZ6yX)
* Parent: Form (Container)
* Child: [Input Stepper - Ctrl](/core/overview/inpstepper.md), [Label](/core/overview/label.md)
## Properties
### Label
The component can be presented with a label to give context to the form control. This label can be positioned to the left, right, above (top), below (bottom).
### Helper Text
To provide additional context for the component a sentence can be added to the component for examples, how the input will be used, or as further clarification to the label.
### Control Qty
The input stepper can have either a single control per row (component) or multiple (side-by-side) input steppers on the same row. Multiple input steppers on the same row provide the ability to input multiple properties for the same parent object. For example, alignment of an object on an X,Y axis with two steppers, one for the X value and another for the Y value.
**Note:** Each of the nested elements and primitives of this form component have properties that can be adjusted to customize the component.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://able.bucca.com/core/components/form/inputstepper.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.