> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/investing/market-structure-and-rotation/trend-heatmap-matrix/features.md).

# Features

Trend Heatmap Matrix Features

The Trend Heatmap Matrix is heavily customizable, allowing you to tailor its aggregated signals to your specific trading style and preferred technical components.

* **10-Component Aggregation Engine**: Synthesizes data from Directional Strength, MACD, RSI, Stochastic, CCI, Velocity, Supertrend, VWAP, MFI, and TSI.
* **Trading Profiles**: Quickly configure the internal timeframes of all components by selecting a preset profile (Scalping, Day Trade, Swing, Investment).
* **Toggleable Components**: Individually enable or disable any of the 10 core components. If you don't care about CCI or VWAP, turn them off and the matrix will recalculate its bias without them.
* **Dynamic Bias Dashboard**: An on-chart UI that displays the current aggregated trend state (e.g., "STRONG LONG", "LEAN SHORT", "NEUTRAL") and the bullish/bearish percentage breakdown.
* **Bar Coloring**: Optionally color your main chart's price candles based on the aggregated trend state, giving you instant visual feedback on momentum.
* **Comprehensive Theming**: Includes 12 beautiful built-in color themes (plus a custom option) to seamlessly integrate into your personal chart aesthetic.


---

# 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://docs.candelacharts.com/investing/market-structure-and-rotation/trend-heatmap-matrix/features.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.
