feather components - Feather

feather components reads macro arguments from the macros themselves, so it stays accurate as they change.

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 sharing a filename with a framework component is marked as overriding it, which is how the template loader resolves it at runtime.

Point an AI assistant at this command before it writes a template. The component reference covers the framework macros, but this covers yours as well.

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.

feather components --markdown -o docs/components.md