> For the complete documentation index, see [llms.txt](https://shiro.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://shiro.gitbook.io/docs/shiro-gameplay/levels-and-challenges.md). # Levels and Challenges ### Purr-fectly Crafted Stages The levels in Shiro will range from the serene Sakura Fields to the perilous peaks of Mount Dōmyō. Each stage is crafted to offer a balanced blend of fun, frustration, and fulfillment. Hidden areas and Easter eggs reward the explorative spirit of players and provide nods to the lore of the crypto-world and meme culture. ### Mastering the Challenge To navigate the levels, players must leap from platform to platform, dodge obstacles, and avoid or outsmart the game's villains—all in pursuit of the elusive sardines. Some levels may introduce unique mechanics, like gravity shifts or speed zones, to keep players on their paws. Boss battles conclude each world, demanding a combination of the character's abilities and player ingenuity. Defeating these gatekeepers not only progresses the game but also results in a sardine bonanza, contributing to the player's $SHIRO earnings. --- # 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://shiro.gitbook.io/docs/shiro-gameplay/levels-and-challenges.md?ask=&goal= ``` `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.