> For the complete documentation index, see [llms.txt](https://docs.empirica.ly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empirica.ly/getting-started/quick-start.md).

# Creating your experiment

Once you have finished setting up Node and Meteor, [as per our setup guide](/getting-started/setup.md), you can use `empirica create` to create your experiment.

Simply run the following command, where `my-experiment` is your experiment name (no spaces or uppercase letters):

```bash
empirica create my-experiment
```

It will create a directory called `my-experiment` inside the current folder. Inside that directory, it will generate the initial [structure](https://github.com/empiricaly/docsv2/blob/main/getting-started/broken-reference/README.md) and install the transitive dependencies.

Once the installation is done, open your project folder:

```bash
cd my-experiment
```

You can now read more about the running your experiment, the structure of an Empirica experiment, and you can try our tutorial:

{% content-ref url="/pages/-MTtiX7H8rZS8QB\_1vq\_" %}
[Running your experiment](/getting-started/quick-test.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.empirica.ly/getting-started/quick-start.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.