> For the complete documentation index, see [llms.txt](https://blog.atraderlife.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.atraderlife.com/strategies/chart-patterns/chart-patterns-description.md).
# Chart patterns description
**What is chart pattern?**
In the world of technical analysis, right next to support/resistance and trendlines, **chart patterns** are a core building block. Some outsiders to technical analysis consider this realm of technical analysis to be so esoteric and "mystical" that it turns them off. This is very unfortunate, because the
principles at work in the formation of these chart patterns are simply a reflection of good.
**Patterns indicate the psychology of a market.**
• **Patterns** also determine the behavior of a market.
Perhaps it is the names that are attached to these patterns that give cause to the skeptical eye. If the Head & Shoulders pattern was renamed to something "academic" sounding like the "Demand/Supply Transition" pattern, it may be more acceptable.
One of the tenets of technical analysis is that markets trend. It has been observed that during the course of trend formation and trend reversal, prices often move in a repeatable, predictable fashion.
These observed price movements that occur during trend formation and during trend reversals have been labeled and given names. These are what we call chart patterns.
Goals of **Chart Pattern Analysis**
1\. Identify the most predictable patterns.
2\. Define rules for trading patterns which result in winning trades.
3\. We should have more winners than losers, and the losses should be smaller than the gains.
• Chart Patterns are Predictive.
• However, identifying Chart Patterns that “work” 100% of the time is difficult (or impossible).
---
# 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://blog.atraderlife.com/strategies/chart-patterns/chart-patterns-description.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.