> For the complete documentation index, see [llms.txt](https://docs.pixels.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixels.online/gameplay.md).

# Gameplay

Pixels is a metaverse and MMORPG for the NFTs you already own. Taking a lot of inspiration from some of our childhood favorites like Stardew Valley and Runescape, Pixels allows you to take your existing NFTs into a play-to-earn game!

## The Vertical Slice Model

We're developing our game using the vertical slice model in order to keep scope in check. The long-term vision of Pixels is to build a game with many interconnected skills, quests, and content to unlock. But in order to keep development timelines realistic and to prove to our stakeholders that we can build and deliver what we're promising, we're fully building out one skill at a time.

Our first skill which we're building out and releasing is Farming!

{% embed url="<https://askagamedev.tumblr.com/post/77406994278/game-development-glossary-the-vertical-slice>" %}


---

# 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://docs.pixels.online/gameplay.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.
