u/Longjumping-Store434

A couple of days ago I posted about my 3 layer system I built to address Claude memory issues and how I set it up.

https://www.reddit.com/r/claude/s/jloGQbiMZO

I got quite a few DMs asking for a simpler breakdown. Here is a one pager that breaks everything down.

For the people who called me a bot, you're wrong.

My system isn't a single prompt and it's not static. It's 20+ files that reference each other. There's a live database that changes every day from real meetings as well as slash commands that run multi-step workflows against actual API endpoints. It took me about two weeks to build.

A bot would've gotten it right the first time.

One pager includes:

- Every file in the project and what it does

- How the database and dashboard fit in

- The slash command pattern (/morning, /debrief, /close, /weekly)

- Data flow from meeting transcript to database

- The mistakes I made so you don't have to

- Daily routine

- Total cost ($100/mo Claude Max, everything else is free tier)

- Step-by-step if you want to build your own

TL;DR: Claude forgets between chats. I gave it permanent context with markdown files, a database for live data, and slash commands that run like scripts. Nothing writes without my approval.

One pager: https://ballyhofam-bot.github.io/claude-project-os/blueprint.html

GitHub repo with templates: https://github.com/ballyhofam-bot/claude-project-os

Credit to u/Available-Spend2443 for his Claude Code OS post — same problem, similar thinking, different platform. I built mine on Claude Projects instead of Claude Code, and added a real database layer.

I'm an EHS manager at a manufacturing plant. ~1,200 employees, think fabrication shop, I'm taking over for someone who's transitioning out. That means every conversation we have contains institutional knowledge that doesn't exist anywhere in writing. If I don't capture it, it's gone.

Claude's great at processing all of this. The problem is it forgets. Conversations compact, sessions start cold, and you're back to re-explaining your entire situation. I got tired of that after about three days and built a system around it.

Layer 1 — .md files in the project

These are project files Claude reads at session start. My role, key people, relationship dynamics, institutional knowledge captures, a running decision log, session history. Project files don't get compacted — they're always there. I have about a dozen covering context, tribal knowledge, people intel, and logs.

The decision log alone has saved me hours. When something comes up that was already discussed and decided, Claude has the date, the reasoning, and the outcome. No re-litigating.

Layer 2 — Cloudflare D1 + Worker API + artifacts

This is where structured data lives. Task tracking with ownership, priority, due dates, who's blocking what tasks. People directory (Golden information). Leadership moves log. All accessible through a Cloudflare Worker API, with a Netlify dashboard on top.

I also built interactive artifacts — a mobile inspection form I use on the manufacturing floor, a meeting prep tool. These are React components that run inside Claude's artifact system.

Layer 1 tells Claude why something matters.

Layer 2 tells Claude what the current state is. Different jobs.

Layer 3 — Skill files

Markdown files in the project that act as executable commands. I type /morning and Claude reads the skill file, pulls live data from D1, checks Otter.ai for unprocessed meeting transcripts, and builds a brief. /debrief after a meeting extracts tasks, captures people intel, and runs a strategic analysis. /close at end of day reconciles everything and updates the .md files.

The cadence is what holds it together. Without Layer 3, Layers 1 and 2 drift apart. The skills force synchronization — debriefs push structured data into D1 and narrative context back to the .md files. Morning briefs read both. Close-of-day reconciles both.

What it looks like in practice

I walk in at 7:30, type /morning, and get a brief that already knows what's overdue, what meetings I haven't processed, and what I should focus on. After a meeting with my boss, or any meeting that I've used otter.ai with, I type /debrief and it pulls the transcript, extracts my action items, flags political dynamics I should pay attention to, and tells me what to go check on the floor. At the end of the day I type /close and everything gets logged.

Two weeks in, Claude knew my facility better than my own notes did. I've hit the ground running, people are already impressed with how much I am aware of historical and tribal knowledge and the best thing is I'm actually performing more efficiently. This isnt perfect and as I fine tune it for efficiency and to my job, I'll post a v2 in a few months.

GitHub repo with genericized templates so you can build your own: https://github.com/ballyhofam-bot/claude-project-os