luther works by:
1. beginning at the code level, documenting the "what" and "how" of individual functions, recursing up to files and directories;
2. describing the purpose (the "why") of these elements, starting with a description of the application and recursing downwards;
3. asking itself questions about the codebase ("how can I start quickly using this", "how can I build this from source", etc.)
Read more in our
documentation, generated entirely by luther itself.