> 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/kr/pancakeswap/about-us/team/the-kitchen-team.md).

# 키친 팀

![](https://raw.githubusercontent.com/pancakeswap/pancake-document/en/.gitbook/assets/the-kitchen-team-header.png)

### 셰프들

🐰 Chef Kids - 총괄 셰프 ([X/Twitter](https://x.com/Headchef_pcs))

🐰 Chef Miso - 프로덕트

🐰 Chef Kocha - 프로덕트

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

🐰 Chef Pau - 운영

🐰 Chef Leo - 비즈니스 개발 리드 ([X/Twitter](https://x.com/DYOR_WAGMI))

🐰 Chef Olive - 비즈니스 개발

🐰 Chef Cocoa - 마케팅 리드 ([X/Twitter](https://x.com/chef_cocoa_pcs))

🐰 Chef Alina - 파트너십 마케팅 ([X/Twitter](https://x.com/0xalinatyng))

🐰 Chef Sake - 커뮤니티 ([X/Twitter](https://x.com/KayraMeow))

🐰 Chef Marcus - 소셜 미디어

🐰 Chef Boba - 커뮤니티

🐰 Chef Salade - 디자인 리드

🐰 Chef Waffles - 디자이너

🐰 Chef Noodles - 디자이너

🐰 Chef Cyrus - 데이터

🐰 Chef Mist - 개발 리드

🐰 Chef Ryan - 프론트엔드 개발 리드

🐰 Chef Philip - AI 개발

🐰 Chef Eric - 프론트엔드 개발

🐰 Chef Jerry - 프론트엔드 개발

🐰 Chef Penguin - 프론트엔드 개발

🐰 Chef Taco - 백엔드 개발 리드

🐰 Chef Sanji - 백엔드 개발

🐰 Chef Curry - 백엔드 개발

🐰 Chef Kiwi - 백엔드 개발

🐰 Chef Bob - 백엔드 개발

🐰 Chef Toast - 백엔드 개발

🐕 Chef Snoopy - 스마트 컨트랙트 개발 리드

🐰 Chef Omelette - 스마트 컨트랙트 개발

🐰 Chef Shiba - 스마트 컨트랙트 개발

🐰 Chef Carb - 스마트 컨트랙트 개발

🐰 Chef Ramen - 스마트 컨트랙트 개발

🐰 Chef Ruby - QA

🐰 Chef Liam - QA

🐰 Chef Rei - 보안

🐰 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/kr/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.