Building a Second Brain with Sparki

A second brain is a personal library of the things you want to remember, reflect on and reuse. It is one flavour of personal knowledge management, and it is what Sparki is designed for.

The product's core distinction: a spark is a piece of saved content (a link, some text, an image). A Sparki is your reflection on it — one or two sentences of your own thinking that live next to the source. Keeping the two side by side is what makes retrieval work months later.

You save sparks from the web app: paste a link, type a note, or attach an image. Sparki adds the title and a preview automatically for most links. This is the moment to add a one-line reason too — "I might use this when planning next sprint" is enough. For a decision test on when to save, see what should you save in a second brain.

Every spark has a dedicated reflection field — the Sparki. It is deliberately short: a couple of sentences. Sparki does not push you to write more than that. For prompts and a copyable template, see how to reflect on an article, book, video or podcast.

Sparki gives you two organisation primitives.

• • Projects — things with a finish line (a launch, a report, a trip).
• • Labels — long-running interests you would still recognise in a year.

A spark can belong to a project and carry a couple of labels. Keep both small — a handful of each. Details in organise saved content without overcomplicating it.

For Later is a dedicated view for time-sensitive things: an article you want to read after lunch, a video for the train. It is not another organisation category — it is a queue that is meant to empty. Keeping it short is the point.

The Review view surfaces the sparks that need attention: unlabelled, without a reflection, or not attached to any project. Ten minutes on Sunday evening is enough to triage the week. Anything that has not earned a home after three review passes is usually worth deleting.

When you share a spark, you can choose whether to include your reflection alongside it using the "Share my reflection" toggle. The toggle is off by default, so sharing a reflection is a deliberate opt-in. If the recipient is not signed in yet, the preview page shows only the spark title with sign-in and sign-up options — the source, content and reflection stay private until they authenticate, and the reflection only becomes visible if you enabled the toggle. For the framing and five message templates, see how to share useful content with context.

What a realistic day with Sparki looks like.

1. Morning — read an article in the browser, paste the link into Sparki, add 'useful for the pricing conversation on Thursday' as the one-line reason.
2. Lunch — open For Later, read the shorter of the two saved items, add a two-sentence Sparki, apply the 'product' label.
3. Afternoon — a colleague asks about onboarding. Search 'onboarding' in Sparki, find a save from six weeks ago, share it with one sentence of context.
4. Evening — five sparks accumulated over the day. Two get labels, one gets a reflection, two get deleted.
5. Sunday — Review view. Ten minutes triaging the untriaged, one older spark gets a fuller Sparki because it turned out to matter.

None of this asks you to run a whole system. It is one small action per moment, spread across the week.