> ## Documentation Index
> Fetch the complete documentation index at: https://docs.indent.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quick Start

> The fastest path to a useful first rollout.

This is the fastest way to make Indent feel real for your team. Start with one repository, one shared place to use it, and the extra context that makes the first workflow click.

<Steps titleSize="h3">
  <Step title="Connect GitHub and set up one repository">
    Open [Settings > GitHub](https://app.indent.com/settings/github), connect the Indent GitHub App, then click `Setup Environment` on the first repository you want Indent to work in. This is the step that lets Indent run commands, validate changes, and open pull requests in a real environment.

    Continue with [Environment Setup](/repo-setup).
  </Step>

  <Step title="Bring Indent into Slack">
    Open [Settings > Integrations](https://app.indent.com/settings/services) and connect Slack. This is usually the moment Indent starts to feel shared across the team instead of useful to just one person.

    Continue with [Connect Slack](/connect-slack).
  </Step>

  <Step title="Add the rest of the context you want Indent to use">
    From [Settings > Integrations](https://app.indent.com/settings/services), connect the systems that make your first real workflow better—usually [Datadog](/datadog), [Sentry](/sentry), [Databases](/databases), or [Custom MCPs](/custom-mcps).

    Continue with [Add Integrations](/add-integrations).
  </Step>
</Steps>

## Next steps

* **[AGENTS.md](/agents-md)** — add repository-level instructions so Indent knows your setup, conventions, and architecture.
* **[Skills](/skills)** — package reusable workflows like deploy steps or debugging checklists so Indent can pull them in when relevant.