***
### **🧠Leadership**
**SQUIZZY**\
\&#xNAN;*Founder /* Owner *| Developer | Social Media Manager*\
The creative force and founder of Varixcode, Squizzy defines the company’s vision and actively contributes to its technical development. With strong expertise in Lua and JavaScript as well as web technologies like HTML and CSS, he ensures that every project is built with clean structure, functionality, and modern design standards. Additionally, he is responsible for managing Varixcode’s social media presence and public communication across platforms.
***
**KRIS**\
\&#xNAN;*Founder / Owner | Project Management | Partnerships & Marketing*\
A key figure behind Varixcode, Kris is responsible for the overall direction, organization, and growth of the project. He contributes creative ideas for new systems and features, ensures quality and project standards are maintained, and manages areas such as partnerships, marketing, communication, and strategic planning. While not directly involved in development, he plays an important role in shaping the vision and long-term success of Varixcode.
***
**MENURIAN**\
\&#xNAN;*Owner | Developer (partially)*\
An important part of the Varixcode team, Menurian contributes both in the background and through selective development work. While not always in the foreground, he supports the project’s technical foundation and assists in coding tasks when needed, helping maintain stability and progress across key areas of Varixcode.
---
# Agent Instructions: 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:
```
GET https://varixcode.gitbook.io/varixcode/vlrixcode-systems/about-us/team.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.