> For the complete documentation index, see [llms.txt](https://mightyminion.gitbook.io/mightyminions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mightyminion.gitbook.io/mightyminions/extra/team.md).

# TEAM

**FOUNDER/ARTIST - Emily - @Mastershifu | Mighty Minion**

Description: Emily is an upcoming artist and crypto enthusiast. She's been in the crypto space since 2017, but recently came across the idea of starting her own NFT project when shopping at Target with James. She realized that most NFT projects at that point in time had little to none utility. So she brainstormed and brainstormed and out came Mighty Minions. She used her experience in the crypto space and artistic ability to create the Mighty Minions for the 3 things that people love in this space... good art/pfp \[profile pic], solid utility, and to be able to make money.

**CO-FOUNDER/MARKETING - James -  @Jashkebi | Mighty Minion**&#x20;

Description: James has extensive experience in the digital marketing space and has generated over $60,000,000+ in revenue through Facebook Ads. He's worked with many brands and has helped them scale their campaigns/projects. As an avid NFT collector/enthusiast, he came on this project as a consultant to help guide and best position Mighty Minions to become the first blue chip Solana gaming/gambling NFT collection. In his free time, he wrestles and dominates.<br>

**CO-FOUNDER/DEV - Minato - @Minato -** [**https://minatoportfolio.netlify.app/**](https://minatoportfolio.netlify.app/)

Description: Being a professional blockchain developer with over 4 years of experience, I have developed many NFTs, games on blockchain, DeFi projects I consider myself as a senior-level developer, working with Solidity/Rust on the blockchain and Phaser3/Unity3d/Rust on the game development. Also I specialize and have extensive experience in React/Next to achieve client's goals.\
\
\ <mark style="color:orange;">**ADMIN TEAM**</mark>

**HEAD DISCORD MOD - Luiz - @Torezan | Mighty Minion**

**HEAD OF ORGANIC GROWTH - Samuel - @TheChunkyFtw | Marketing Minion**

**INSTAGRAM MANAGER - Freya - @Freya | Mighty Minion**

**HEAD COLLAB MANAGER - Leyla** - **@Leyla | Mighty Community Minion**

**COMMUNITY MANAGER - @Elocnium | Mighty Minion | NOM NOM**

<mark style="color:blue;">**GAME DEVELOPMENT TEAM**</mark>

**SENIOR UNITY GAME DEV - Deepak - <https://www.linkedin.com/in/deepak-kundra-11a77655/>**

**DATABASE DEV - Lucas - <https://www.linkedin.com/in/lucas-cavalcante-junges/>**

**UNITY GAME DEV -  Dilbag - <https://www.linkedin.com/in/dilbag-thind-494458134/>**

**UNITY GAME DEV - Arthur**

**ARTIST ASSISTANT - Mary - <https://www.behance.net/marinasouza16>**

**ARTIST ASSISTANT - EsGar**

<mark style="color:purple;">**MINION LOVER TEAM**</mark>

**@Liv.Jesse | Mighty Minion Lover**

**@Misa | Mighty Minion | Nomer**

**@MJane | Ms. Minion**

**@OffGridDave | Minion Lover**

**@SSG Wrench | Mighty Minions**


---

# 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://mightyminion.gitbook.io/mightyminions/extra/team.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.
