> For the complete documentation index, see [llms.txt](https://faq.growsensor.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.growsensor.co/the-grow-app/how-do-i-set-limits-and-alerts-for-graphs/can-i-create-limit-templates-or-recipes.md).

# Can I create limit templates or recipes?

**Not yet - but soon!**

We’re working on a feature that will allow you to select, preview, and apply tested and proven grow recipes to your grow.

This means you’ll be able to set ideal limits effortlessly and simply focus on keeping your environment within the recommended range. Easy, repeatable, and optimised for success

You’ll be able to choose from:

* **Veg & flower stage recipes** – Pre-set environmental conditions tailored for each growth phase.
* High & low EC feeding recipes – Optimise nutrient levels for different feeding strategies.
* **Specialty recipes** – Designed for inducing colour, achieving top-shelf quality, or even saving energy while maintaining great results.

{% hint style="info" %}
**Stay** **tuned** - this feature is coming soon!
{% endhint %}


---

# 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://faq.growsensor.co/the-grow-app/how-do-i-set-limits-and-alerts-for-graphs/can-i-create-limit-templates-or-recipes.md?ask=<question>&goal=<endgoal>
```

`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.