# Create Frigg App

Use `npx` to use the latest generator code, and just pass it whatever you want to name your Frigg application.

{% hint style="info" %}
**Note on naming:** we recommend thinking of your Frigg app as a microservice that powers integrations; naming it something like "my-app-integrations" is a good fit
{% endhint %}

```
npx create-frigg-app [my-app-integrations]
cd [my-app-integrations]
```

Congrats! You've just successfully scaffolded and installed your Frigg application.

## Configuration

### Frontend

You will have to set up your own config files for the frontend of your application with:

```
cd frontend
cp .env.example .env
```

### Backend

Currently, configuration is managed in two places for the backend. You can see the backend configuration here: `backend/src/configs/*.json` but you will also need a `.env` file in `/backend`.

```
cd backend
cp .env.example .env
```

## Start Your Application

Let's spin it up to explore more:

```
npm run start
```

Your browser should open to `http://localhost:3000`, and the backend should spin up an API route at `http://localhost:3001/dev/api`


---

# 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://docs.friggframework.org/0.2/develop/tutorials/quick-start/create-frigg-app.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.