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

# feather components

> Every macro's real signature, read from the macros themselves.

Never guess a macro's arguments. `feather components` reads them from the macros
themselves, so it is right even when documentation is not.

```bash theme={null}
feather components                                  # signatures and import lines
feather components --json                           # for tooling
feather components --markdown -o docs/components.md
```

## Your components too

Components your app defines under `templates/components/` are listed alongside the
framework's. One that shares a filename with a framework component is marked as
overriding it, which is how the template loader resolves it at runtime.

<Tip>
  This is the command to point an AI assistant at before it writes a template. The
  [component reference](/ui/components) in these docs lists the framework macros, but
  `feather components` also knows about yours.
</Tip>

## In your own docs

The `--markdown` flag writes a catalogue file you can commit, so a reviewer reading a
pull request sees the same signatures without running anything.

```bash theme={null}
feather components --markdown -o docs/components.md
```