10
LLM Assistant for Markdown Documents
(quokk.au)
what volume of markdown files are we talking?
also, just so i understand this right:
you are looking fir a markdown editor which has a chat window on the side which can look at other files to assist in writing.
is that correct?
which editor do you use right now for editing the files? does it need to support vim-movements? (if u dont know what that is, it doesnt matter)
what exactly would the LM be assisting in? should it be to just read files and respond, or edit them itself aswell, or suggest edits?
suggestion for under 200 files
depending on the amount of files, a simple index and read-tool functionality might be enough. Here is how you would create such an index:
- LM looks at each md file
- Then generates a one-liner about the content, like:
Static functions and variables in Godot, using autoload scripts and scenes (e.g. loading screens, overlays, save systems, anything permanently loaded)
- store that into a file alongside each files path, perhaps like this:
~/Documents/
file.md (one-liner here)
another_file.md (one-liner here)
topic/
file_about_topic.md (one-liner here)
[...]
These three steps can be done using any coding agent you got lying around using this prompt
Goal: FILE_INDEX.txt which contains all files in <folder with the documents> in tree form (reduce redundant dir paths) with a concise and keyword-heavy one-liner about the files content.
FILE_INDEX.md format:
~/SomeDir/SomeDirBelowIt/
a_file_in_that_dir.md (description)
another_file.md (description)
dir_inside_it/
file_in_that_dir.md (description)
How: First use `tree` to see the directories contents, then use subagents to delegate the generation of the descriptions. They should out them into files themselves. An agent can summarize 5 files at mist in one go. Tell each agent exactly what name the output file should have. Finally, after having received all descriptions with their file names, combine the files all into one final FILE_INDEX.txt
This index can then be did into any agent to let it find files quicker, without having to hope for good chunking settings in a RAG pipeline.
all this was written by a human, even if it might not seem as such.