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

# Slash Commands

> Trigger Parsaa's Modernize flow directly from the composer

## Overview

Type `/` in the Parsaa composer to trigger a command on the **focused Xcode file**. A suggestion menu appears as you type and filters to matching commands.

## Available Commands

| Command      | Title        | What it does                                        |
| ------------ | ------------ | --------------------------------------------------- |
| `/modernize` | Modernize    | Modernize deprecated Apple APIs in the focused file |
| `/analyze`   | Analyze APIs | Detect deprecated Apple APIs — free, no rewrite     |

Both are intercepted by the composer and routed to the [Modernize](/features/modernize) flow.

## Generators (@-mentions)

Test and documentation generation are no longer slash commands — they're built-in agents you summon with an **@-mention**:

| Mention       | What it does                                                                                               |
| ------------- | ---------------------------------------------------------------------------------------------------------- |
| `@tester`     | Generate unit tests for the focused file — see [Test Generation](/features/test-generation)                |
| `@documenter` | Write doc comments for the focused file — see [Documentation Generator](/features/documentation-generator) |

<Info>
  `@tester` and `@documenter` are built-in sub-agents. Their per-run settings (framework, naming, format, scope) come from **Settings → Automation**. See [Sub-agents](/features/subagents).
</Info>

## How It Works

<Steps>
  <Step title="Focus a file">
    Open the file you want to act on in Xcode so it becomes the focused file.
  </Step>

  <Step title="Type the command or mention">
    In the composer, type `/` for a command (e.g. `/modernize`) or `@` for a generator (e.g. `@tester`). You can add extra instructions after it.
  </Step>

  <Step title="Review the result">
    Parsaa runs the flow and presents the output — a diff, generated tests, or docs — for you to review and apply.
  </Step>
</Steps>

<Tip>
  A trigger only fires at the very start of your message. Path-like text such as `src/modernize` won't be mistaken for a command.
</Tip>

## Related

<CardGroup cols={2}>
  <Card title="Modernize APIs" icon="wand-magic-sparkles" href="/features/modernize">
    Detect and rewrite deprecated Apple APIs.
  </Card>

  <Card title="Test Generation" icon="flask-vial" href="/features/test-generation">
    Generate tests with @tester.
  </Card>

  <Card title="Documentation Generator" icon="book" href="/features/documentation-generator">
    Generate docs with @documenter.
  </Card>

  <Card title="Sub-agents" icon="robot" href="/features/subagents">
    How built-in and custom agents work.
  </Card>
</CardGroup>
