# Custom component properties
Omlet provides built-in component properties in analysis, such as file path, component name, and package name. Along with these properties, you can also add your custom properties to components.
This helps you **define and track custom usage metrics** and **automatically apply tags** based on different rules and attributes — giving you a more accurate view of how components are being used across your entire organization.
By adding custom properties, you can:
* Automatically tag and track components based on their category, such as Icons or Pages
* Automatically tag and track components that are, or should be, deprecated
* Identify all the components created by a particular product team or user
* Find components that have missing documentation or tests
* Differentiate visual vs. non-visual components
* Track package versions used across your projects
Continue with learning more about CLI hooks to add custom properties to components:
{% content-ref url="/pages/mwWbj53tKA27FMtoAIdM" %}
[CLI hooks](/cli-and-dashboard/learn-omlet-cli/custom-component-properties/cli-hooks.md)
{% endcontent-ref %}
---
# Agent Instructions: 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:
```
GET https://docs.omlet.dev/cli-and-dashboard/learn-omlet-cli/custom-component-properties.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.