ContextliContextli

Developers Β· Learning Log

Capture what you just learned so it sticks.

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.

What you said

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-dev.md

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

1

Record a voice note

Hit the hotkey and talk, no formatting, no typing.

2

Tag it with this context

Contextli shapes your words into the structured output above.

3

Find it later

Everything's searchable and organised by context.

4

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

system prompt

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 click copies it and shows you exactly how to drop it into Contextli.

Next, open Contextli, go to the Contexts page, click Import, choose From JSON, paste, then Import Context. It is ready to use.

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

Questions people ask

Questions developers ask about Learning Log

What should a structured note include?

A good structured note includes a clear title, steps to reproduce the issue, the expected behavior, the actual behavior observed, the severity or priority, and the environment details such as OS, browser, and app version. The Learning Log context structures your spoken description into these fields automatically, so nothing gets left out when you are in the middle of debugging.

How do I write a structured note in under a minute?

Speak what you found: describe the issue, what you expected, what actually happened, and how bad it is. The Learning Log context structures your words into a complete structured note you can paste directly into Jira, Linear, or GitHub Issues. Most take under 60 seconds to dictate, so you capture them without breaking your flow.

How do developers capture issues without interrupting their flow?

The key is to capture the issue immediately without switching context mentally. Contextli lets you speak a quick voice note describing it and produces a structured note from it. You can dictate while the issue is still on screen, then paste the formatted output into Jira, Linear, or GitHub Issues when you come up for air. No typing is required during the capture step.

Can I write a structured note by talking instead of typing?

Yes. The Learning Log context lets you speak a description in plain language and converts it into a structured structured note with all the required fields filled. You speak the way you would explain it to a colleague, and the context handles the formatting.

How do I add this context to Contextli?

Copy the context on this page, then open Contextli and go to the Contexts page. Click Import, choose From JSON, paste it into the Import from Clipboard window, and click Import Context. It is ready to use in under 30 seconds. If you do not have Contextli yet, you can download it for free first.

Is my voice recording private? Does Contextli send it anywhere?

Your voice recording and the transcription are stored on your device only. Contextli processes your audio locally and does not send your recordings or transcription text to any server. The structured output it produces is text you control, and you decide where it goes.

Can I change what the output looks like?

Yes. Every context in Contextli is a starting point you can edit. Open the context in the app, change the instructions to adjust the structure, tone, or fields, and save. The next time you use it, the output reflects your changes. You are not locked into the default format.

Do I need to install an app to use this context?

Yes. Contextli is a free app. Download it, then copy this context and paste it into the Import from Clipboard window on the Contexts page. The whole process takes about 30 seconds.

Browse more

Learning Log