Matthew Lang

I’ve tried a lot of different systems for note-taking and task management over the years, but one downside of each has been the time needed to maintain its organisation to a level that keeps it useful. I have lost track of how many different systems and methods I have tried, but I always ended up with a small collection of notes until I settled on the Bear notes app a few years ago. Even using the Bear notes app, though, I was still not 100% settled on using it and wanted something more from my notes. And that’s where the LLM wiki pattern came in.

The LLM wiki pattern, described here as a GitHub Gist, has been an absolute game-changer since I started using it last week. The gist on GitHub explains the system and how the LLM can help maintain your wiki over time.

The migration

It hasn’t taken me long to migrate my Bear notes and Instapaper queue to Obsidian, and, coupled with the ability to automate parts of the schema and for the LLM to handle management of concepts, entities, and summaries, I have managed to get my current notes in Bear to a better shape than I have ever had them in before. Migrating my Bear notes and Instapaper queue to this new system was quite expensive in terms of LLM usage, but I managed to spread it out over a few days.

What I am left with after this initial migration is a list of 150+ articles from my Instapaper queue that I need to vet and decide whether to keep in my notes. I’ll be doing these in batches of five or six each morning to avoid burning through my Claude Pro subscription. I found out early on that this process of fetching and summarising articles can be quite expensive in terms of token usage.

The benefits

My notes are now plain text Markdown files once again. Many note-taking apps use Markdown, but not many of them allow you to access your notes as files and update them outside of the app. Having plain-text files means I am not tied exclusively to Obsidian, and I can use other tools with them if I want to. They might not always be in the right format or syntax for linking between notes, but they are in a fairly common format that is easy to update and migrate.

I am also choosing not to sync these notes to my phone. The intended outcome is that anything I need to do with my notes should be done on my laptop during a dedicated time slot for that task. This should also reduce the amount of time I spend on the phone, which is never a bad thing.

I am migrating my tasks from Things to a separate section of the wiki, still within the same vault in Obsidian. The structure of these files is based on Nicholas Bate’s six compass points, and is a mixture of projects, notes and next actions. The six compass points allow me to allocate a project or task to a specific compass point and make organising such items much easier. The big benefit of this system is that, while I can allocate tasks across different compass points, I can bring all of them together into a single view in Obsidian using the Dataview plug-in.

So far, so good

The LLM wiki pattern is great because it does most of the work for you. It maintains the index, summaries, fetches and breaks down sources for you. I’m quite happy to review additions as they come into the system, but the self-organisation of the information is what makes this a quite powerful tool.

There are other benefits to this, but the big one for me is that the information across my wiki is back to plain text again. I’m happy to have a collection of files I can maintain myself if needed.

I admit it’s early days with the LLM wiki pattern, but the gains from it over the first week have been impressive. In a few months, I’ll touch back on its usage, what I have changed with it, and whether I will continue using it.