Who this is for
Developers who keep re-solving the same problems and want a searchable log of their own hard-won lessons.
The moment this saves you
I spend two hours figuring out some obscure config, get it working, move on, and a month later hit the identical problem with zero memory of how I solved it the first time.
See it work
Messy spoken thought in. A clean, structured artifact out.
Learning log. Just figured out something annoying, our Docker builds were super slow and it turns out it's because the COPY of the whole directory was busting the layer cache on every build, even for tiny changes. The fix is to copy just the package files first, run the install, then copy the rest, so the dependency layer stays cached unless dependencies actually change. This is a general principle, order your Dockerfile from least to most frequently changing. The context was our CI was taking 12 minutes and this got it to like 4. I always forget this exact thing so I want it saved.
Learning log, June 5, 2026
- What I learned: In a Dockerfile, copying the whole directory before installing busts the layer cache on every build.
- The fix: Copy just the package files first, run install, then copy the rest, so the dependency layer stays cached unless dependencies change.
- General principle: Order a Dockerfile from least to most frequently changing.
- Context / impact: CI went from ~12 min to ~4 min.
- Tags: #docker #ci #caching
The workflow
Record a voice note
Hit the hotkey and talk, no formatting, no typing.
Tag it with this context
Contextli shapes your words into the structured output above.
Find it later
Everything's searchable and organised by context.
Pull it into Claude or ChatGPT
Bring your contexts straight into your AI tools with the Contextli MCP.
Your raw recording and transcription stay on your device, so you can always go back to the original.
The prompt behind this context
I'm going to capture something I just learned (often technical). Turn it into a dated learning log: a bold "Learning log, [today's date]" heading, then labeled lines: What I learned (the lesson, stated as a fact), The fix (the solution, if it was a problem), General principle (the transferable rule, if I name one), Context / impact (the situation and any measurable effect), and a Tags line of hashtags ONLY from topics I mentioned. Keep my technical specifics exactly. Don't invent details or tags I didn't say. Output only the log.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Use this context
One tap adds it to your clipboard. Open Contextli and paste to add it.
Next, open Contextli, Contexts, Import, paste.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Your raw recording and transcription stay on your device, so you can always go back to the original.
Related contexts
Code Decision Log
Right after you make the call, while the tradeoffs are still fresh, talk through why you went this way and what you rejected. Three months from now when someone asks 'why a queue here?', the answer is already written down.
Debugging Session Log
Two hours deep in a nasty bug and you can't remember which theories you already ruled out. Narrate the hunt as you go, what you tried, what you saw. You get a running log that stops you re-testing the same dead end and captures the fix when it lands.
Second Brain Capture
The good thought arrives when you're nowhere near your notes app. Say it out loud and get a clean atomic note, title, the idea in your words, and a few tags, ready to drop straight into Obsidian, Notion, or wherever your second brain lives.