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

# Quickstart

> Build your first feature with SuperAntigravity in 5 steps

# Quickstart

After [installing SuperAntigravity](/installation), your Antigravity IDE has access to the full workflow pipeline. Here's how to use it to build a feature from scratch.

<Note>
  Skills fire automatically — you don't need to invoke them. Just use the slash commands and the right skills load based on your context.
</Note>

## The 5-stage workflow

<Steps>
  <Step title="Brainstorm the feature">
    Type `/brainstorm` followed by a brief description of what you want to build.

    ```
    /brainstorm add user authentication with email and password
    ```

    **Switch to Planning Mode** in Antigravity conversation settings before starting.

    Antigravity will ask you 4–5 clarifying questions, then propose 2–3 design approaches. Review the options and approve one. A design document is saved to `docs/plans/`.

    <Warning>
      Don't skip this step. If you type "just build it," SuperAntigravity will refuse and explain why the design phase saves time.
    </Warning>
  </Step>

  <Step title="Write the implementation plan">
    Once the design is approved, type:

    ```
    /plan
    ```

    Antigravity reads the design document and breaks it into bite-sized tasks — each with a specific file path, failing test to write, and expected outcome. The plan is saved to `docs/plans/`.

    Stay in **Planning Mode** for this step.
  </Step>

  <Step title="Implement the feature">
    Switch to **Fast Mode**, then type:

    ```
    /implement
    ```

    Antigravity works through the plan task by task:

    * Runs a confidence check before each task (score must reach 27/30 to proceed)
    * Writes a failing test first (RED phase)
    * Writes minimal code to make it pass (GREEN phase)
    * Commits after every GREEN test
    * Requests a code review after each task

    If a test fails unexpectedly, the systematic-debugging skill loads automatically.
  </Step>

  <Step title="Review the implementation">
    When all tasks are complete, type:

    ```
    /review
    ```

    The `code-reviewer` agent checks the implementation against the plan across 6 areas: plan alignment, code quality, architecture, documentation, issue identification, and communication.

    You'll receive one of three verdicts:

    * **APPROVED** — ready to ship
    * **APPROVED WITH SUGGESTIONS** — ship, then address suggestions
    * **CHANGES REQUIRED** — fix before shipping
  </Step>

  <Step title="Commit and push">
    Once approved, type:

    ```
    /git
    ```

    Antigravity runs a final verification check, formats commit messages following Conventional Commits (`feat:`, `fix:`, `test:`), and handles the push or PR creation.
  </Step>
</Steps>

## Conversation modes

Using the right mode for each phase makes a significant difference in response quality.

| Mode              | Use for                               | Commands                                             |
| ----------------- | ------------------------------------- | ---------------------------------------------------- |
| **Planning Mode** | Design, research, analysis, debugging | `/brainstorm`, `/plan`, `/research`, `/troubleshoot` |
| **Fast Mode**     | Implementation, testing, execution    | `/implement`, `/test`, `/build`                      |

Switch modes in the **conversation settings** panel in Antigravity.

<Tip>
  If you're in the wrong mode, SuperAntigravity will prompt you: "I am starting a Planning phase. Please switch to Planning Mode in the conversation settings for optimal performance."
</Tip>

## Skills fire automatically

You don't need to load skills manually. When your context matches a skill's trigger description, Antigravity loads it automatically. For example:

* Starting a new feature → `brainstorming` skill loads
* A test fails → `systematic-debugging` skill loads
* About to mark something done → `verification-before-completion` skill loads
* Code touches authentication → `security-review` skill loads

## Next steps

<CardGroup cols={2}>
  <Card title="The workflow" icon="arrow-right" href="/workflow/overview">
    Deep dive into each pipeline stage, gates, and interrupt protocols
  </Card>

  <Card title="Skills reference" icon="bolt" href="/skills/overview">
    All 19 auto-triggered skills explained with trigger conditions
  </Card>

  <Card title="Commands reference" icon="terminal" href="/commands/overview">
    Every slash command with prerequisites and examples
  </Card>

  <Card title="Agents reference" icon="robot" href="/agents/overview">
    The 8 specialist agents and when to use them
  </Card>
</CardGroup>