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

# fallow list

> CLI reference for fallow list. Inspect discovered files, entry points, active plugins, and architecture boundary zones to debug configuration and verify project setup.

Inspect what fallow discovered in your project. Use this command to debug configuration issues or verify that the right files, entry points, plugins, and boundary zones are being picked up.

<Tip>
  Use `fallow list --plugins` to verify which of the 95 built-in plugins are active for your project.
</Tip>

```bash theme={null}
fallow list
```

## Options

| Flag                    | Description                                                       |
| :---------------------- | :---------------------------------------------------------------- |
| `--files`               | Show all discovered files                                         |
| `--entry-points`        | Show entry point files                                            |
| `--plugins`             | Show active plugins                                               |
| `--boundaries`          | Show architecture boundary zones, rules, and per-zone file counts |
| `-f, --format <FORMAT>` | Output format: `human` (default), `json`                          |

## Examples

<CodeGroup>
  ```bash Inspect plugins theme={null}
  # Show active plugins
  fallow list --plugins

  # JSON output for scripting
  fallow list --plugins --format json
  ```

  ```bash Inspect files theme={null}
  # Show all discovered files
  fallow list --files

  # Show entry points
  fallow list --entry-points
  ```

  ```bash Inspect boundaries theme={null}
  # Show boundary zones and rules (requires boundaries config)
  fallow list --boundaries

  # JSON output with zone file counts
  fallow list --boundaries --format json
  ```
</CodeGroup>

## Example output

```bash title="$ fallow list --boundaries" theme={null}
Boundaries: 4 zones, 4 rules

Zones:
  app                  3 files  src/app/**
  features             12 files src/features/**
  shared               8 files  src/components/**, src/hooks/**, src/lib/**, ...
  server               4 files  src/server/**

Rules:
  app                  → features, shared, server
  features             → shared, server
  server               → shared
  shared               (isolated — no imports allowed)
```

```bash title="$ fallow list --plugins" theme={null}
Active plugins:
  - nextjs
  - vite
  - vitest
  - playwright
  - storybook
  - eslint
  - typescript
  - tailwind
  - drizzle
  - commitlint
  - sentry
```

```bash title="$ fallow list --entry-points" theme={null}
Found 42 entry points
src/app/layout.tsx                   (Plugin: nextjs)
src/app/page.tsx                     (Plugin: nextjs)
src/instrumentation.ts               (Plugin: nextjs)
src/proxy.ts                         (Plugin: nextjs)
src/lib/utils.test.ts                (Plugin: vitest)
e2e/auth.setup.ts                    (Plugin: playwright)
.storybook/main.ts                   (Plugin: storybook)
drizzle.config.ts                    (Plugin: drizzle)
scripts/db-migrate.ts                (PackageJsonScript)
scripts/db-seed.ts                   (PackageJsonScript)
...
```

Each entry point shows how it was discovered. The plugin name tells you which framework detected it.

## See also

<CardGroup cols={2}>
  <Card title="Built-in plugins" icon="puzzle-piece" href="/frameworks/built-in">
    Full list of fallow's 95 built-in framework plugins.
  </Card>

  <Card title="Custom plugins" icon="plug" href="/frameworks/custom-plugins">
    Create plugins for frameworks fallow doesn't cover yet.
  </Card>
</CardGroup>