> For the complete documentation index, see [llms.txt](https://jabe.gitbook.io/jabe-rig-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jabe.gitbook.io/jabe-rig-wiki/documentation/features/fingers.md).

# Fingers

Steve, Alex and Slim hands, finger IK and FK, and the Fingers Master control.

Each hand has five fingers: **Index**, **Mid**, **Ring**, **Pinky** and **Thumb**.

## Arm Type

**Arm Type** (under **Customize > Definitions**) sets the hand and arm style. It is a dropdown, so it can be keyframed.

| Arm Type            | Style                        | Size |
| ------------------- | ---------------------------- | ---- |
| **Steve** (default) | Steve-style arms and fingers | 4x4  |
| **Alex**            | Alex-style arms and fingers  | 4x3  |
| **Slim**            | Slim-style arms and fingers  | 3x3  |

The finger bone collections follow the Arm Type, so the controls you see match the style you chose.

## Turning the fingers on

**Left Fingers** and **Right Fingers** are off by default. They appear in **Controls > Arm Settings** and again in **Customize > Definitions**.

## IK and FK

Fingers have their own IK slider (**Left Fingers IK**, **Right Fingers IK**) and their own **Convert to IK** and **Convert to FK** buttons in **Arm Settings**. See [IK and FK](/jabe-rig-wiki/documentation/features/ik-and-fk.md).

## Fingers Master

The **Fingers Master Control** bone controls the whole hand's fingers together. Its visibility is a toggle in the [Bones](/jabe-rig-wiki/documentation/features/bones.md) section, and what it follows is set with its own parent selector in the [IK Parent Tree](/jabe-rig-wiki/documentation/features/ik-parent-tree.md).

## Showing finger bones

In **Bones**, each arm has a **Fingers** toggle, and each hand has separate **IK** and **FK** toggles for its finger bones. All are off by default.


---

# 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://jabe.gitbook.io/jabe-rig-wiki/documentation/features/fingers.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.