> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/art-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/art-guide/2d.md).

# 2D

General 2D guidelines.

This document is a set of rules and guidelines for designing and contributing 2D assets for SS3D. It covers the UI elements, textures, decals, particles and so on. Nothing is set in stone, but for reasons of “consistency of style” these things should be kept in mind.

#### General Info: 

* In most cases, .png file format is to be used as it is easy to edit and supports transparency.
* For consistency it’s best to use the colors from the 3D pallet when possible.
* In case the image or it’s fragment needs to change color, an image should be made white, as Unity programmed coloring works by adding color to the image.

#### Software:

{% embed url="<https://www.gimp.org/>" %}

#### Tasks:

* 2D tasks can be found here: <https://trello.com/b/XVZ95Hjq/ss3d-2d>


---

# 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://ss3d.gitbook.io/art-guide/2d.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.