> For the complete documentation index, see [llms.txt](https://atomico.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atomico.gitbook.io/doc/guides/component/naming.md).

# Naming

Simple but useful

If you are a React user, it is common for you to make component declarations like these:

```tsx
export function MyComponent(){
    return <>My component in react</>
}
```

Thanks to the previous code in React we can:

1. Instantiate your component through its function, example `<MyComponent>`
2. Friendly export component as module

In Atomico there are some small differences [👇](https://emojipedia.org/emoji/%F0%9F%91%87/)

## we recommend in Atomico

Export the return of the c function, since it is instantiable at the JSX level or when using the new operator, example:

{% tabs %}
{% tab title="my-component.tsx" %}

```tsx
export const MyComponent = c(() => <host>My component in Atomico</host>);

customElements.define("my-component", MyComponent);
```

{% endtab %}

{% tab title="Instance in JSX" %}

```tsx
import { MyComponent } from "./my-component";

function app(){
    return <host>    
        <MyComponent/>
    </host>
}
```

{% endtab %}

{% tab title="Instance in JS" %}
**Instance with operator new**: The new operator allows the instance to associate at the TS level the types declared using Atomico

```javascript
import { MyComponent } from "./my-component";

const component = new MyComponen; 
```

**Instance with document.createElement**&#x20;

<pre class="language-javascript"><code class="lang-javascript"><strong>import "./my-component";
</strong>
const component = document.createElement("my-component");
</code></pre>

{% endtab %}

{% tab title="Instance in HTML" %}

```markup
<my-component></my-component>
```

{% endtab %}
{% endtabs %}

Gracias a lo anterior podemos:

1. Instantiate your component with TS-level type validation either by using JSX or the new operator with, **but remember that to get this type of instances you must first have registered your customElement in the same file or another.**
2. Export the useful component to instantiate.

{% hint style="warning" %}
Prefer this export format because tools like @atomico/exports take advantage of this format to automatically create wrappers for React, Preact, and Vue.
{% 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 following URL with the `ask` and `goal` query parameters:

```
GET https://atomico.gitbook.io/doc/guides/component/naming.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 `build a script that syncs our docs to a CMS` 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.