Tweet
POV: your OpenClaw after you didn’t set up a second brain system. Paste this prompt to fix that: 👇 I want you to build me a second brain memory system. Create a memory/ folder and a https://t.co/Msllm4OWRv file in your workspace. Every session, read these FIRST before doing anything, they are your entire memory. memory/YYYY-MM-DD.md are your daily journals. As we talk each day, log everything in real-time - decisions, tasks, preferences, context, mistakes. Timestamp each entry. These are your raw notes. https://t.co/Msllm4OWRv is your long-term memory. This is curated, who I am, my goals, my preferences, active projects, lessons learned, key decisions and why. Every few days, review your daily journals and distill the important stuff into here. The rule: if it's not written to a file, you don't remember it. When I say "remember this", write it immediately. When you make a mistake,document it so you never repeat it. When you learn something about me update https://t.co/Msllm4OWRv. Over time you should know my communication style, what I care about, what annoys me, my projects, my goals. After a week this should feel like a real assistant that actually knows me. After a month, indispensable.
Scraped Article
This has a linked resource worth reading, a tool worth trying, or an idea worth prototyping
Quick Insight
This is a prompt template for setting up a persistent memory system for AI assistants (like Claude/ChatGPT) using daily journals and a master knowledge file. It's trying to solve the problem of AI conversations losing context between sessions by creating a file-based memory system that gets read every time.
Actionable Takeaway
Set up this exact folder structure (`memory/` with daily `.md` files and a `core-memory.md`) for your AI coding sessions. Start logging your preferences, project context, and coding patterns so the AI remembers your TypeScript setup, AWS CDK preferences, and current side project status between conversations.
Related to Your Work
This could be huge for your AI-powered dev workflows. Instead of re-explaining your fintech platform architecture, serverless patterns, or side project requirements every chat session, the AI would remember your AWS CDK setup, preferred libraries, coding style, and current sprint context.
Source Worth Reading
The links appear broken (`https://t.co/...` truncated), so can't evaluate the linked resources. The tweet itself contains the core implementation details.