> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/welcome-to-pancakeswap/about-us/team/the-kitchen-team.md).

# The Kitchen Team

![](https://2908774936-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MHREX7DHcljbY5IkjgJ-1972196547%2Fuploads%2FF52XcZKijWBBbPebZo5L%2Fthe-kitchen-team-header.png?alt=media\&token=440b126c-daa5-4245-b4ca-d0bfef0ff02d)

### The Chefs

🐰 Chef Kids - Head Chef ([X/Twitter](https://x.com/Headchef_pcs))

🐰 Chef Miso - Product

🐰 Chef Kocha - Product

🐰 Chef Mustard - Ops ([X/Twitter](https://twitter.com/chef_mustard))

🐰 Chef Pau - Ops

🐰 Chef Leo - Business Development Lead ([X/Twitter](https://x.com/DYOR_WAGMI))

🐰 Chef Olive - Business Development 

🐰 Chef Cocoa - Marketing Lead ([X/Twitter](https://x.com/chef_cocoa_pcs))

🐰 Chef Alina - Partnership Marketing ([X/Twitter](https://x.com/0xalinatyng))

🐰 Chef Sake - Community ([X/Twitter](https://x.com/KayraMeow))

🐰 Chef Marcus - Social Media  

🐰 Chef Boba - Community  

🐰 Chef Salade - Design Lead

🐰 Chef Waffles - Designer

🐰 Chef Noodles - Designer

🐰 Chef Cyrus - Data

🐰 Chef Mist - Dev Lead 

🐰 Chef Ryan - Frontend Dev Lead

🐰 Chef Philip - AI Dev

🐰 Chef Eric - Frontend Dev

🐰 Chef Jerry - Frontend Dev

🐰 Chef Penguin - Frontend Dev

🐰 Chef Taco - Backend Dev Lead

🐰 Chef Sanji - Backend Dev

🐰 Chef Curry - Backend Dev

🐰 Chef Kiwi - Backend Dev

🐰 Chef Bob - Backend Dev

🐰 Chef Toast - Backend Dev

🐕 Chef Snoopy - Smart Contract Dev Lead

🐰 Chef Omelette - Smart Contract Dev

🐰 Chef Shiba - Smart Contract Dev

🐰 Chef Carb - Smart Contract Dev

🐰 Chef Ramen - Smart Contract Dev

🐰 Chef Ruby - QA

🐰 Chef Liam - QA

🐰 Chef Rei - Security

🐰 Chef Cola - HR


---

# 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.pancakeswap.finance/welcome-to-pancakeswap/about-us/team/the-kitchen-team.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.