> For the complete documentation index, see [llms.txt](https://appcraftman1.gitbook.io/car-rental-app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://appcraftman1.gitbook.io/car-rental-app/file-structure.md).

# File Structure

## Understanding File Structure

Starting with a good folder structure, especially when working on large applications is very important for the developer experience,

### Top-Level Directory Dtructure

```
.
├── api           # Contains the fake backend Api mock data and config
├── assets        # Contains app assets (images, icons and custom fonts file)
├── config        # Dev tools configuration
├── docs          # application documentation
└── src           # Application main Source Code directory
```

### Application File Structure

The starterKit use a pattern that group files by domain where all files corresponding to a business domain are in the same directory. Here is the example of SignIn page file structure:

```
.
├── ...
├── SignIn             # Contains all files related to SignIn page UI and logic
│   ├── __tests__      # Unit tests and integration of the display the screen, its components and behavior
│   ├── behavior.js    # Screen behavior (actions and action creators ans reducers)
│   ├── index.js       # Export default screen component
│   ├── SignIn.js      # Main screen UI component
│   ├── selectors.js   # Selectors from Redux State
│   └── styles         # Styles used for displaying this scree
└── ...
```

### Test File Structure

The automated tests are placed in the **tests** directory of each screen / component.

Unit and integration tests are placed directly in the **tests** folder

Snapshots Jest tests (rendering tests of a screen / component against a snapshot) are placed in the **snapshots** subfolder


---

# 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://appcraftman1.gitbook.io/car-rental-app/file-structure.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.