# Naming conventions for application elements

In projects carried out in Eximee Designer, using consistent naming conventions for application elements is key to maintaining order, clarity, and effective team collaboration.

Well-chosen names make it easier to:

* quickly search and filter components in the repository,
* identify the function and purpose of a given element without having to open it,
* avoid name conflicts and accidental overwriting of artifacts,
* manage large sets of forms, processes, scripts, etc., especially in environments with many applications and teams.

The table below presents the recommended naming conventions for all main types of application elements in Eximee. They are consistent with best practices used in production projects and help maintain order in scalable solutions.

{% hint style="info" %}
All names are given in English - in the case of top-down agreements regarding the form name, Polish is used.
{% endhint %}

#### Eximee application element naming conventions table

<table><thead><tr><th width="138.272705078125">Element type</th><th width="195.818115234375">Name format</th><th>Example</th></tr></thead><tbody><tr><td><strong>Application</strong></td><td><mark style="background-color:orange;">prefix</mark>_app</td><td><code>kontoJunior_app</code>, <code>800plus_app</code></td></tr><tr><td><strong>Form</strong></td><td><mark style="background-color:orange;">prefixName</mark></td><td><code>kontoJuniorStart</code>, <code>kontoJuniorForm</code>, <code>kontoJuniorAcceptance</code></td></tr><tr><td><strong>Other elements (e.g. scripts)</strong></td><td><mark style="background-color:orange;">prefixName</mark></td><td><code>kontoJuniorCheckAmount</code></td></tr><tr><td><strong>Processes</strong></td><td><mark style="background-color:orange;">prefixNameProcess</mark></td><td><code>kontoJuniorProcess</code>, <code>kontoJuniorSendNotificationProcess</code></td></tr></tbody></table>

General rules

* <mark style="background-color:orange;">prefix</mark> - the business name of a given project, placed at the beginning of each application element in camelCase format
* <mark style="background-color:purple;">Name</mark> - the name of the given element in camelCase format

{% hint style="warning" %}
In the case of forms and applications, it should be taken into account that the name of the form/application later appears, among other places, in the URL address.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/elementy-aplikacji-artefakty/konwencje-nazewnicze-elementow-aplikacji.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.