# Trading Approach

Our trading approach consists of three main components (A,B,C) and one optional component (x) which is used to increase the efficiency of trading system and trading accuracy.

## 🔶 (\[x]) \[A] + \[B] + \[C]

**\[x] HTF Direction** – Higher timeframe directional bias, overlay for trading

**\[A] Context** – Price levels and areas where we look to enter the market

**\[B] Setup formation** – Forming our trading plan and setting potential targets

**\[C] Trading technique** – Refining our entries and exits

🔶 **Favorable \[A] + \[B] trading combinations:**

A1 with B1 or B3 or B4

A2 with B1 or B3

A3 with B1 or B2 or B3 or B4

A4 with B1 or B2 or B3 or B4

A5 with B1 or B2 or B3 or B4

A6 with B4 or B2

A7 with B1 or B3

<figure><img src="/files/gzuJf8a71f1CIgLRE1Ue" alt=""><figcaption></figcaption></figure>

We are combining this components into profitable trading systems which are used for different day-types and situations. There are seven different \[A]’s and four different \[B]’s which can construct 21 different trading combinations for ground stones of a trading system. All this combinations can be traded in various ways with different techniques, we have nine\[C] of them. Without combining multiple trading techniques into trading system (which can also be done), we’re already at 189 trading systems that can further be improved with addition of five different higher timeframe overlays \[x], bringing that number up close to a thousand.


---

# 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.forexanalysis.com/fxan-education/trading-approach.md?ask=<question>
```

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.
