# Step 3: Get Familiarized

Once you've [downloaded the latest Monogatari release](/documentation/develop/getting-started/getting-monogatari.md), take some time to get familiar with the files and directories inside it.

{% hint style="info" %}
You can take a look at a more visual representation of the Monogatari project structure [in this simple mind map](https://www.mindmeister.com/1136161346/monogatari-project-structure).
{% endhint %}

### Directories

You'll find some directories, here is what you should use them for.

| Directory | Contains                                                                                                       |
| --------- | -------------------------------------------------------------------------------------------------------------- |
| `assets`  | This is where all your assets such as images, audio files, font files etc. should go                           |
| `engine`  | The core engine files that make everything work. Updating Monogatari is as simple as replacing this directory. |
| `js`      | This is where you'll set your game configuration and create your game script.                                  |
| `style`   | CSS files for your project (CSS defines the look and style of your game).                                      |

## **Root Directory**

![](/files/-MH3Bv87Urh52RkLvrCC)

Inside the main directory you'll find some pretty useful files.

| File                | Contains                                                                                          |
| ------------------- | ------------------------------------------------------------------------------------------------- |
| `index.html`        | This is your main file, open this file in a browser and there's your game!                        |
| `manifest.json`     |                                                                                                   |
| `robots.txt`        | This file asks crawlers and other bots to keep your assets directory unindexed from web searches. |
| `service-worker.js` | This file defines your service worker, used for asset preloading and caching                      |
| `.htaccess`         | This file provides a basic Apache configuration in case you are using that web server.            |

More about what to do and how to use this specific files will come later as you read the documentation.

**JS Directory**

![](/files/-MH3JfVJRwx-LNl4wKYX)

JavaScript is the programming language you'll be using in Monogatari, it is what makes all your game work.

| File           | Contains                                                                                     |
| -------------- | -------------------------------------------------------------------------------------------- |
| **main.js**    | If you want to add more javascript, this is the file to do it!                               |
| **options.js** | Initial settings of your game and engine settings.                                           |
| **script.js**  | The main script of your game. (Here's where your story, characters, images etc are declared) |
| **storage.js** | This is where you'll declare your custom variables that you want to save in your games.      |

**Style Directory**

![](/files/-MH3JiyBpwckdRf32cFJ)

CSS is the markup language used to style your game, from setting colors to improving the appearance, CSS is what will allow you do them all. 

| File         | Contains                       |
| ------------ | ------------------------------ |
| **main.css** | Add your styling in this file. |


---

# Agent Instructions: 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:

```
GET https://developers.monogatari.io/documentation/develop/getting-started/step-3-get-familiarized.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.