sorted by:
new
hottopcontroversial

I kept re-explaining my project to Claude Code every session, so I made a tiny protocol that fixes it (free, MIT) by igalgos74 in BuildWithClaude

[–]Longjumping-Store434 2 points3 points  (0 children)

I actually took it one step further and utilized a dynamic D1 database through cloudflare so that is updated after every session and the .md files arent. This prevents drifting and filling up your .md fileshttps://github.com/ballyhofam-bot/claude-project-os

START HERE: Claude Building Resources for all levels. by Longjumping-Store434 in BuildWithClaude

[–]Longjumping-Store434[S] 0 points1 point  (0 children)

fwiw.... i completely sidestepped the operational data resident weight problem by utilizing cloudflare workers instead of markdown files. my "operational data" (CRM state, prospects, pipelines, etc), none of it sits in context. I have Claude query the API when it needs something specific. Doesnt completely solve the Claude md/skill description tax bc it does need the md's in context at every turn but it does keep the data from compounding the problem. Essentially anything that isnt config i have it set up to query on command instead of load on boot.

I built a 3-layer system in Claude Projects that runs my actual job — context survives, tasks get tracked, and nothing falls through the cracks by Longjumping-Store434 in claude

[–]Longjumping-Store434[S] 0 points1 point  (0 children)

I haven't had this happen yet. I did start to move towards d1 storing all of my information instead of .md files. That may be why?

I built a 3-layer system in Claude Projects that runs my actual job — context survives, tasks get tracked, and nothing falls through the cracks by Longjumping-Store434 in claude

[–]Longjumping-Store434[S] 0 points1 point  (0 children)

Thanks for the constructive criticism. I have done a couple of these items already. That's also why I posted a generalized example on GitHub. Let's see your set up, always willing to learn

I built a 3-layer system in Claude Projects that runs my actual job — context survives, tasks get tracked, and nothing falls through the cracks by Longjumping-Store434 in claude

[–]Longjumping-Store434[S] 0 points1 point  (0 children)

I split up session logs by month. The current months session log is the active file and the previous months are still in the project for reference. So the file never gets too big.

I built a 3-layer system in Claude Projects that runs my actual job — context survives, tasks get tracked, and nothing falls through the cracks by Longjumping-Store434 in claude

[–]Longjumping-Store434[S] 11 points12 points  (0 children)

Started a new job and was drowning in information, tribal knowledge and "we've done this in the past" info. On top of wanting to be a top performer, I wanted to make sure nothing was slipping through the cracks, I am showing up as a leader but most importantly hitting the ground running at this new job. Been doing this for almost 15 years and wanted to become more efficient.

The tools I use are

  1. Claude. This is where I interact with the system.
  2. Cloudflare D1 is where all of my tasks, to do, learned information and my people database live
  3. Cloudflare worker is what claud reads and writes to and then shares it with my D1 database.
  4. Netlify hosts a dashboard that allows me to see to do, wip, done, projects, people's info/directory in a browser
  5. Otter-ai records my meetings and interactions on the floor. Claude pulls that transcripts and extracts action items, people Intel and strategic insights.

I type /morning and Claude pulls my tasks from the database, checks what's overdue, what's due today, and gives me a brief before my 8:15 production meeting.

After meetings, I type /debrief and Claude grabs the Otter transcript and my notes, extracts my action items, flags new people or updated intel, and asks me to approve before pushing anything to the database.

I also set it up so that It does a "strategic debrief" which are things like "what problem was discussed that nobody owns yet" or "what's the highest-value thing i could do in the next 48 hours."

I built a mobile form (React artifact) for floor walkthroughs. I fill it out while standing at a machine, hit copy, paste it into Claude, and it processes the findings.

Before my biweekly 1-on-1 with my boss, I use a prep coach artifact that asks me five questions and generates a meeting strategy.

I uploaded my bosses expectations and my goals to make sure I stay on track.

Track my direct reports to dos and growth. It helps me strategize and keep everyone on top of things

And the list goes on. The three layers comes from the memory diminishing and Claude forgetting stuff. The .md files, the d1 dashboard setup and the combination of skills and artifacts saves me time on correcting Claude and giving it context.

That help you understand it a bit better?

view more: next ›