feather components - Feather

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

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.

This is the command to point an AI assistant at before it writes a template. The component reference in these docs lists the framework macros, but feather components also knows about yours.

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

⌘I