> 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/overview/inpstepper/inpstepper-pieces.md).

# Φ InputStepperPieces

Primative: The pieces that go into the input stepper to step a numeric value up or down by a set amount.

[Styleguide Link](https://zpl.io/a7pK0qj)

* Parent: [InputStepperCtrl](/core/overview/inpstepper.md)
* Child: [Label](/core/overview/label.md)

## Properties

### Type

**Arrow** - Left/Right and Up/Down arrow icons on the buttons to increment the input stepper.

**Plus-Minus** - Plus and Minus icons on the buttons to increment the input stepper.

**Value** - For the center section of the input stepper which is where the current value is displayed.

### Style

**Primary** - The buttons in the primary color

**Secondary** - The buttons in the secondary color

**Light** - The buttons in a light color

**Neutral** - The buttons in a grey color

**Dark** - The buttons in a dark color

### Location

The location of the piece of the input stepper in relation to the whole.

* Left
* Right
* Top
* Bottom
* Center - The value is always at the center

### State

* Enabled
* Disabled
* Hover
* Pressed
* Focus

### Metaphors

We use the metaphors (aka Icon Library) to standardize on the meaning of icons used in the application. In the Input Stepper element we have six metaphors.

**Arrow Left**: Icon-Library > Base > Primitives > Prim - InpStep Left

**Arrow Right**: Icon-Library > Base > Primitives > Prim - InpStep Right

**Arrow Up**: Icon-Library > Base > Primitives > Prim - InpStep Up

**Arrow Down**: Icon-Library > Base > Primitives > Prim - InpStep Down

**Plus**: Icon-Library > Base > Primitives > Prim - InpStep Add

**Minus**: Icon-Library > Base > Primitives > Prim - InpStep Minus


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://able.bucca.com/core/overview/inpstepper/inpstepper-pieces.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.