> For the complete documentation index, see [llms.txt](https://zendius-jsc.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zendius-jsc.gitbook.io/docs/collaborating/how-we-work-together.md).

# How we Work Together

At **Zendius Studio**, we believe great games are built through **strong collaboration**, **open communication**, and **mutual respect**. We work together as one team, sharing ideas freely, supporting each other, and celebrating our wins. Whether it’s brainstorming creative concepts, solving challenges, or polishing the final product, we value every voice and contribution.

{% hint style="info" %}
When reading about “How We Work Together,” focus on the principles and spirit of our teamwork, without getting into individual roles, detailed processes, or specific project workflows.
{% endhint %}

### Collaboration First

We break down silos and encourage teamwork across all disciplines.

### Clear Communication

We keep discussions transparent, timely, and constructive.

### Trust & Respect

We honor diverse perspectives and build a safe space for honest feedback.

### Ownership & Initiative

We empower each other to take responsibility and drive progress.

### Continuous Improvement

We reflect, learn, and find ways to work smarter together.


---

# 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://zendius-jsc.gitbook.io/docs/collaborating/how-we-work-together.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.