> 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/chip/chip-modal.md).
# Φ ChipModal
Primitive Collection: The modal that opens in front of a chip when it is selected to provide additional details about the subject matter.
[Styleguide Link](https://zpl.io/boAY9QZ)
* Parent: [Chip](/core/overview/chip.md)
* Child: [Label](/core/overview/label.md), [Icon](/core/overview/icon.md), [Avatar](/core/overview/avatar.md), [Rating](/core/overview/rating.md)
## Properties
### Subject
* Person
* Place
* Thing
### Type
**Name** - A modal box with an Avatar/Graphic and the subject matter name with a right close icon.
**Name & Detail** - The subject matter name with additional details below
**Name & Rating** - The subject matter name with a rating below
### Interaction
You can see the general interaction of how this modal appears, where it appears and how it is dismissed [here, down in the MD Expandable section](https://material.io/components/chips#input-chips). Note: When active all other app functionality is disabled until the modal is dismissed or the action is taken on the modal.
### Metaphor
We use the metaphors (aka Icon Library) to standardize on the meaning of icons used in the application. In the ChipModal we have a metaphors.
**Close**: Icon-Library > Base > Act - Clear
---
# 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/chip/chip-modal.md?ask=&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.
