> 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/support-and-resistence/support-and-resistence-description.md). # Support and Resistence description **Support & Resistance systems** are designed for sideways or directionless markets, and they typically have the following attributes: * They buy low and sell high in an attempt to take advantage of the sideways price movement characterizing directionless markets. * They have a high number of winning trades, with small profits on each trade. They sell as the market goes higher and take small losses until the market finally turns down and results in a profitable trade. * They are easier to trade emotionally. * By design, these systems miss the big move * They usually have small profits and larger losses as markets trend. The system keeps shorting a market that is in an uptrend or buying a market that is in a downtrend. Therefore, when traders use Support & Resistance systems, they use them within a group of systems that also includes trending systems and perhaps one or more volatility systems. --- # 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/support-and-resistence/support-and-resistence-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.