Laura Rosenberger

Category: AI Use Cases

  • AI Memory Across Sessions

    One of the reasons OpenClaw has captured everyone's imagination is the memory. It remembers you. Every other AI conversation starts from zero – close the window, lose everything, re-explain yourself next time.

    I've been working a lot in Claude Code, and have built myself a little skill to recreate this.

    How It Works

    I built a /handoff command that runs a structured wrap-up when I'm done working. It reviews the session and saves what matters to a set of persistent markdown files — a daily note, active threads, behavioural patterns (which it can then pull me up on…), and self-improvement notes.

    These notes are accessible for future sessions. Claude knows what I was working on, what's due, and what patterns to watch for.

    The whole thing is just a text file telling Claude what to do and what to save – but it is making using Claude Code as a general assistant for non-technical work just so much better.

    Why It's Useful

    It turns each session from a one-off into something that compounds. Less time re-explaining, more time working. And it catches things I wouldn't note myself — like when the same blocker keeps showing up or when I'm quietly avoiding something (ahem).

    It's not as seamless as OpenClaw's built-in memory. But I control what gets saved, where it lives, what gets forgotten and what my 'assistant' is able to do with this information.

  • Claude Code Plugin for Obsidian

    Last year I moved all my notes and files out of Notion and into Obsidian. With Notion, you're locked in to whatever tools they give you. I wanted to be file-first rather than software-first, so I could use the latest AI tools on my actual files.

    I was already using Claude Code to work with my files. Then I found a community plugin for Obsidian that adds Claude Code as a sidebar. I now have access to Claude Code and everything it can do right where my notes are.

    The Solution

    I installed the Claude Code plugin from Obsidian's community plugins. It adds a sidebar where I can have conversations with Claude Code whilst viewing my files. There's a button to link specific files into the conversation, so Claude has context on exactly what I'm working with.

    This isn't just having a conversation with Claude, this is Claude Code, which means it can take actions, plan, and has all the power that Claude Code has rather than just Claude, which has been way more useful.

    How I Use It

    As a practical example, I keep Markdown files for potential clients in my CRM folder. After a sales call, I use the sidebar to automatically pull in transcripts and add my personal notes and thoughts to create really high-quality notes about each client. It updates the metadata properties at the top of the file. That's how I track what needs to happen next – things like 'awaiting proposal' or 'follow up in two weeks'.

    I can also ask it, 'Who do I need to follow up with?' and it'll search my CRM notes and draft emails for each person.

    The whole thing takes a fraction of the time it used to, and to be honest, this kind of thing I often used to not be super on top of because it felt like a chore. Now I actually do it, or rather, now it gets done for me.

    Why This Has Impact

    Better follow-ups, less prep time before meetings, and I can easily search my notes to find who might be a good fit for something.

    The bigger win is flexibility. I'm not locked into any specific tool. My notes are just Markdown files. If a better AI tool comes out tomorrow, I can use it on the same files. File-first means I control my data and what I can do with it, instead of being locked in.

  • Voice for Email

    I don’t like the idea of AI connecting directly to my Gmail. My entire life is in there.

    I don’t want it messing with my tone of voice or making people think I’m using fake AI responses. Often there’s not enough context for AI to write accurate emails anyway.

    But there is another way I use AI to save time in my inbox.

    The Solution

    I use a voice-to-text app with a custom AI prompt to format emails as I like them.

    Tools like Monologue, WhisperFlow, or SuperWhisper let you speak your email reply. The prompt structures it the way I like, removes filler words, and cleans up stumbles. It doesn’t transcribe word-for-word – it turns spoken thoughts into clean, natural-sounding emails.

    And I don’t have to give access to my inbox to any AI tool.

    How I Use It

    I use Monologue (https://www.monologue.to/). When I need to reply to an email, I hit the option key twice on my keyboard and just talk as if I’m on the phone. The AI processes the audio, cleans it up, and pastes it straight into Gmail for me to review and send.

    The prompt handles the polish whilst keeping my voice. No risk of AI accidentally sending something. Full control over what gets sent.

    Why This Has Impact

    I fly through my inbox now. The barrier to replying is much lower.

    It’s not just that speaking is faster than typing. It’s that replying to an email suddenly feels like talking to someone in the room instead of sitting down to “write an email.” That psychological shift has had the biggest difference.

    The friction disappears and the risky automation stays out.

  • Software Engineering Tutor

    I was blindly accepting everything Claude Code suggested. Commands would run, code would get written, and I’d just click “yes” without understanding what was happening. I wanted to actually learn what I was accepting.

    The Solution

    I created a project in the Claude desktop app to act as my software engineering tutor. The prompt is simple:

    You are my software engineering tutor. Explain code, tools, and technical concepts in plain language, breaking down unfamiliar ideas step by step. Check my understanding with questions.

    The key part is “check my understanding with questions.” This forces me to actually verify I understand what I’m learning.

    How I Use It

    I keep two windows open:

    1. Claude Code in Terminal – building the actual project
    2. Claude Desktop App – Project: Software Engineering Tutor – my learning companion

    When Claude Code does something I don’t understand, I copy the code or command into the tutor project and ask for an explanation. The tutor breaks it down step by step, then asks me questions to verify my understanding.

    That’s when I realise I didn’t understand as much as I thought.

    Why This Has Impact

    I’m learning instead of just blindly clicking “accept”. I don’t need to write production-grade code, but I want to be able to read a bash command and know whether it’s about to delete my files or create a backup.

    The tutor approach works because it’s active learning. Having something explained and then being tested on it? That actually sticks and I’m learning 10x faster.