> For the complete documentation index, see [llms.txt](https://docs.brainboard.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brainboard.co/cloud-design/right-panel/resources-list/best-practices-and-sortcuts.md).

# Best Practices and Sortcuts

## Best Practices

### Navigation

* **Use the search** for architectures with more than 10 resources.
* **Use File-Grouped View** when working with organized, multi-file architectures.
* **Click references** to quickly navigate between related resources.

### Resource Management

* **Review parameters regularly** to ensure configurations are correct.
* **Check for unset required parameters** (indicated with warning icons).
* **Use the minimize feature** to focus on specific resources while keeping others visible.

### Performance

For very large architectures (100+ resources), the interface automatically optimizes by:

* Switching to **File-Grouped** View.
* Virtualizing the card list (only rendering visible cards).
* Limiting expanded parameter displays.

***

## Keyboard Shortcuts

* <mark style="color:$primary;">`SHIFT+CMD+R`</mark> / <mark style="color:$primary;">`SHIFT+CTRL+R`</mark> : Toggle between the **`Resources`** and **`Code`** tabs.
* <mark style="color:$primary;">`CMD+F`</mark> / <mark style="color:$primary;">`CTRL+F`</mark> : Focus search input (when **`Resources`** tab is active).
* <mark style="color:$primary;">`Escape`</mark> : Clears search.
* <mark style="color:$primary;">`Enter`</mark> : When hovering a card, opens **Resource Configuration.**


---

# 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.brainboard.co/cloud-design/right-panel/resources-list/best-practices-and-sortcuts.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.