> For the complete documentation index, see [llms.txt](https://docs-en.coderblock.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.coderblock.com/coderblock-studio/builder-tool-advanced-guide/working-environment/design-tools/asset-packs/graphic-components.md).

# Graphic components

Some objects can be graphically customized.

The different nature and shape of these objects requires a precise creation of the graphic or photographic elements we want to integrate, since certain design specifications must be met in order to avoid possible deformations.

There are just three basic rules:

* All graphic components must be inscribed in a **square format**.
* The dimensions of the square must always be to the **power of 2**. The recommended formats in pixels are **512x512** and **1024x1024**.
* The file should be in **JPG** format (recommended), or **PNG** (if you want it to be transparent).

{% embed url="<https://airtable.com/appA7Wxlihl8Hiv7T/shrFcZ5kEnDXlxJ0B>" %}

{% hint style="info" %}
Regardless of the software used for production (Photoshop, Illustrator, Gimp, Canva, etc.), it is recommended to create the graphic based on the dimensions shown in the diagram, and later stretch the canvas to the square format, adding vertical or horizontal space depending on the object created, without stretching the final image.
{% endhint %}

{% hint style="info" %}
Objects such as "Logo Plane" or "Sticker" do not have a solid component as a frame and are primarily created to maintain transparency where needed. The use of PNG files is recommended in such cases.
{% endhint %}


---

# 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-en.coderblock.com/coderblock-studio/builder-tool-advanced-guide/working-environment/design-tools/asset-packs/graphic-components.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.