> For the complete documentation index, see [llms.txt](https://docs.omlet.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omlet.dev/cli-and-dashboard/components/props-tracking.md).
# Props tracking
Omlet helps you track the usage numbers for each prop of a component and what values are being sent to those props.
The Props tracking gives your team insights to make decisions on what to add, remove, or adjust in your design system. Let's say you have some unused props or props with low usage — great candidates to deprecate. You can also catch unusual values used in a prop to uncover unmet use cases.
## View prop usages
To list a component's props, click the "Props" tab from the "Component Detail" page. You can click on a prop to drill down its variables and select the "List usages" button. This will show you where and how the variables of that prop are used in your codebase.
To list the usage details for a specific variable, you can directly click on that variable.
### \[not set] values
`[not set]` values refer to the component usages where the specified value is not set. If you open the details, Omlet will list the component usages that this value is not set.
### Dynamic values
Variables and values with non-primitive types are listed as "dynamic". From the Prop details, you can still see where they're used in your codebase.
## Unused component props
Under the Popular Charts page, Omlet displays unused component props that can be removed to simplify code and reduce maintenance overhead. Learn more: [Popular charts](/cli-and-dashboard/analytics/popular-charts.md)
---
# 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://docs.omlet.dev/cli-and-dashboard/components/props-tracking.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.