> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/shopify/developer-tools/next-js/quick-start.md).

# Quick Start

This guide assumes you already have Node.js and Git installed on your machine.

### Configure access to Chord's private Github repositories

Share your Github username with the Chord team to gain access to Chord's Github repositories. You'll need to do two things:

1. Make sure you have access to the [starter repository](https://github.com/chordcommerce/nextjs-starter-performance). [Reach out to Chord for access](mailto:help@chord.co) with your Github username if you do not.
2. Configure your local npm to install Chord's packages from GitHub Packages:

* Go to <https://github.com/settings/tokens> and click `Generate new token`. Make sure you select the `read:packages` scope. Copy the token.
* If you don't already have one, create a `.npmrc` file in your home directory (`touch ~/.npmrc`).
* Append the following to `~/.npmrc`, replacing the `<YOUR PERSONAL ACCESS TOKEN>` with the Github token you just created:

{% code title="\~/.npmrc" %}

```shell
//npm.pkg.github.com/:_authToken=<YOUR PERSONAL ACCESS TOKEN>
@chordcommerce:registry=https://npm.pkg.github.com
```

{% endcode %}

This means that any npm packages with the `@chordcommerce` scope will be installed from Github Packages instead of the npm public registry. If you have any trouble on this step, see Github's documentation on [configuring npm for use with Github Packages](https://docs.github.com/en/free-pro-team@latest/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages).

### Create a new site

Click the "Use this template" button on the starter Github repository to create a new Github repository in your account with the same files and folders, or fork the repo. Then clone your new repo onto your local machine:

```shell
# with git
git clone git@github.com:<YOUR ACCOUNT>/nextjs-starter-performance.git
# or with the GitHub CLI
gh repo clone <YOUR ACCOUNT>/nextjs-starter-performance
```

### Configure your site's environment

```shell
cp .env.example .env
```

You'll need to populate this `.env` file with some environment variables, including your Chord account and CMS credentials. Talk to the Chord team to get these.

### Start your development server

Install project dependencies:

{% tabs %}
{% tab title="yarn" %}

```shell
yarn install
```

{% endtab %}

{% tab title="npm" %}

```shell
npm install
```

{% endtab %}
{% endtabs %}

After installation is complete, start the development server:

{% tabs %}
{% tab title="yarn" %}

```shell
yarn dev        # starts site at http://localhost:3000
```

{% endtab %}

{% tab title="npm" %}

```shell
npm run dev     # starts site at http://localhost:3000
```

{% endtab %}
{% endtabs %}

You can see your new site at <http://localhost:3000>. Hot reload is enabled by default.

**That's it! You're off and running. ✨**


---

# 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.chord.co/chord-oms/shopify/developer-tools/next-js/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.