> 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/archives/tips.md).

# Tips

Here are some tips you can take into account when creating webcomponents with Atomico

### Component name as function

Write the functional component using the first lowercase character, since the functional declaration is not instantiable as a constructor in JSX.

```jsx
function component() {
  return <host />;
}
```

This prevents confusion when identifying the constructor of the component instance.[ ](https://atomico.gitbook.io/doc/v/espanol/api/virtualdom/avanzado#constructor-con-custom-element)[Atomico if it supports instances as Constructors, see cases.​](https://atomico.gitbook.io/doc/api/virtualdom/advanced#constructor-with-custom-element)

### useProp <a href="#useprop" id="useprop"></a>

preferably use useProp in the following cases:

* By modifying the prop from inside the component.

```jsx
function useCounter(prop) {
  const [value, setValue] = useProp(prop);
  return {
    value,
    increment() {
      setValue(value + 1);
    },
  };
}
```

* By isolating the logic of the prop in a customHook.

```jsx
function useCounter(prop) {
  const [value, setValue] = useProp(prop);
  return {
    value,
    increment() {
      setValue(value + 1);
    },
  };
}
```

In most cases downloading the prop from the first argument of the function is simpler and more declarative, example:

```jsx
function component({ value }) {
  return <host>{value}</host>;
}

component.props = {
  value: Number,
};
```

[Atomico has type support in both JSDOC and Typescript by inferring the types of the props.​](https://atomico.gitbook.io/doc/guides/typescript#props-less-than-typeof-component.props-greater-than)

### Prefers the use of static styles

```jsx
function component() {
  return <host shadowDom />;
}

component.styles = css`
  :host {
    display: block;
  }
`;
```

This does not rule out the use within the style tag, since it is sometimes the solution to the definition of conditional styles or variables to the logic and outside the scope of the custom properties.


---

# 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://atomico.gitbook.io/doc/guides/archives/tips.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.