> For the complete documentation index, see [llms.txt](https://docs.liminalvillage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liminalvillage.com/protocols/kitchen/cooking.md).

# Cooking

Guests are expected to help in the food shopping, preparation & cleanup. One responsible person can take on the Kitchen cluster for all lunation duration with the support of the kitchen- cooking team. He/she will organize and coordinate the activities. Please if you take on the kitchen-cooking cluster ask at the beginning of the lunation for relevant information to the place steward.&#x20;

Every time food is prepared the kitchen needs to be cleaned, including the floors (wiped and cleaned with water if dirty) and the tiles around the sink over the fire plates. One deep cleaning of the kitchen must be organized once a month.&#x20;

Once a week the responsible person for the kitchen-cooking role needs to organize the review of the food in the fridge and get rid of moldy wasted expired food.&#x20;

Rubish needs to be removed daily from the kitchen and put into the 60LT bins placed in the yard near the main entrance gate.&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.liminalvillage.com/protocols/kitchen/cooking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
