> For the complete documentation index, see [llms.txt](https://the-sheet.gitbook.io/the-sheet-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://the-sheet.gitbook.io/the-sheet-v2/docs/best-practices.md).

# Best Practices

## Templates

Because the library is an ecosystem of multiple components, it's best to create a reusable template of components and features that you want to use across your app.

This way, you can maintain and update the features much easier. It also creates a consistent experience for your app.

You can check out one template example at `apps/example-expo/components/bottom-sheet-template/bottom-sheet-template.tsx`. This template supports multiple features out of the box, such as:

* Sheet ID for you to override if needed
* Backdrop that animates opacity
* Input focus handling provider (You just need to adjust your input components to use the provided `onFocus` and `onBlur` handlers)
* Snap points / Max height
* Height budget system (You still need to use `HeightClaim` and `HeightFill` in your own children content properly)
* Header left / center / right
* Close button
* Action buttons (Not sticky footer though)


---

# 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://the-sheet.gitbook.io/the-sheet-v2/docs/best-practices.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.