> 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/overview/styles/motion.md).

# Ω Motion Library

The component as a whole can also have motion applied to it. An example of this might be the "Flash" of a ListItem when it is selected from a list.

<figure><img src="/files/5EScPM5DMDqEMncyIGjc" alt=""><figcaption></figcaption></figure>

## Resources

These resources are stored in the snippets library as pieces of code that can be used across the application and referenced through the token assigned to it in the snippets library.

<https://pub.dev/packages/flutter_animator>

**Prebuilt Types**: Bounce, Flash, HeartBeat, Pulse, Rubber Band, Shake, Head Shake, Swing, Tada, Wobble, Jello

**Enter/Exit Types**: Bounce, Fade, Flip, Lightspeed, Rotate, Slide, Slit, Zoom, Hinge, Jack-in-the-Box, Roll

<https://pub.dev/packages/animate_do>

<https://pub.dev/packages/animated_text_kit>

<https://pub.dev/packages/motion_widget>

<https://pub.dev/packages/animations>

## Properties

**Name**: \[textField] The human readable way we refer to this "Motion" in the dictionary

**Type**: \[selectList()] The categories we set up for the different types of motions. The initial thought is that we will have at least two types: Productive which demo a sense of efficiency and responsiveness in the app, and Expressive which are more enthusiastic and highly visible to signify an important moment.

**Resource**: \[searchList(motion.Type)] Every motion will have a source file that it references to provide the code for the activity this is the location of that snippet of code needed to preform the desired action

**Metaphor**: \[textField] Every motion response acts as a metaphor for something. Some responses can carry multiple metaphors (i.e. "success" and "win" for a positive result) This allows us to reuse these feedback metaphors as a design token which is referenced throughout our components while all referencing the same file.

**Token**: \[textField] The short-code we use to refer to this metaphor (i.e.. #moWin, #moError, #moWarn, etc.)


---

# 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/overview/styles/motion.md?ask=<question>&goal=<endgoal>
```

`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.