> 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/toolkits/weekly-profiles-tm.md). # Weekly Profiles™ ICT weekly profiles are structured conceptual frameworks designed to outline typical patterns of price behavior over the course of a trading week. These profiles serve as analytical tools, offering traders insights into recurring market tendencies and helping them identify potential opportunities and risks. Each ICT weekly profile has distinctive characteristics that provide valuable clues for anticipating potential market movements, such as directional biases, consolidation phases, or volatility spikes. It is crucial to emphasize, however, that these profiles are not fixed or guaranteed predictions. Instead, they act as flexible guides for understanding broader market tendencies. Traders should apply these frameworks in conjunction with other technical and fundamental analysis tools, as well as sound risk management strategies, to make informed decisions in dynamic market conditions. --- # 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://docs.candelacharts.com/toolkits/weekly-profiles-tm.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.