> For the complete documentation index, see [llms.txt](https://anthonyyoo.gitbook.io/atlas-grid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anthonyyoo.gitbook.io/atlas-grid/atlasgrid-prototype-features.md).

# AtlasGrid Prototype Features

The prototype includes two sample apps and uses demo data.

## Try these features first

1. Choose **Cal AI** or **Finch** from the app selector.
2. Search for a screen or visible transition.
3. Drag a screen to rearrange the graph.
4. Right-click a screen to open its selection menu.
5. Select a branch, then drag one selected screen to move the complete selection.
6. Use **Fit graph to view** to return to the complete map.

## Navigate the graph

### Pan and zoom

* Drag an empty part of the canvas to move around the graph.
* Scroll or use the **Zoom in** and **Zoom out** controls.
* Select **Fit graph to view** to frame the complete graph without moving any screens.
* Use the minimap to understand and change which part of the graph is visible.

### Search

Search finds screens and visible transitions. Choosing a result moves the canvas to the relevant screen or connection without changing the graph.

### Switch sample apps

Use the app selector to move between the Cal AI and Finch examples. Each app has its own graph and browser-saved arrangement.

## Select screens and branches

### Select individual screens

Select a screen to work with it. Hold **Shift** while selecting to create a multi-screen selection. Dragging any selected screen moves the complete selection together.

### Open the screen context menu

Right-click a screen to open its selection commands. The available commands depend on where that screen sits in the graph:

* **Select downstream** selects the screens that follow the chosen screen.
* **Select entire branch** selects the complete branch containing that screen.
* **All branches** selects every branch leaving a split.
* A named branch command selects the branch leading to a specific destination.

Hovering or focusing a command previews the screens it will select. After choosing a command, drag any selected screen to move that group together.

### Use the context menu with a keyboard

1. Press **Tab** until the desired screen is focused.
2. Press **Shift+F10** or the keyboard's **Context Menu** key. On Mac keyboards, use **Fn+Shift+F10**.
3. Use the arrow keys to move between commands.
4. Press **Enter** or **Space** to choose a command, or **Escape** to close the menu.

## Rearrange the graph

### Drag screens

Drag a screen to change its position. AtlasGrid recalculates its visible connections while it moves.

You can move:

* one screen;
* a manual multi-screen selection; or
* a branch selected from the context menu.

### Undo, redo, and restore

* **Undo** reverses the last graph movement.
* **Redo** reapplies an undone movement.
* **Restore original layout** returns the active app to its approved starting arrangement.

## Continue reading

For the product and technical decisions behind the prototype, see [**How I Built AtlasGrid**](/atlas-grid/how-i-built-atlasgrid.md).


---

# 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://anthonyyoo.gitbook.io/atlas-grid/atlasgrid-prototype-features.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.