×
×
Setup guides, the monthly maintenance routine, where the Brain lives, and how to send feedback. Bookmark this page — it's your home base.
The Brain is your team's shared, AI-readable memory. It lives in one GitHub repository, gets rebuilt once a month from your source documents, and flows automatically to everyone's machine. Three things to know:
The Brain (CLAUDE.md, the synthesized content, the skills) lives in a single GitHub repository. That's the source of truth.
Source docs are linked in a tracker. On the 25th they're synthesized; on the 1st every machine pulls the update. It's a static reference, rebuilt monthly — not a live library.
Once a teammate is set up, updates arrive automatically each session. No re-downloading, no manual syncing.
This is the whole path from a fresh machine to a working Brain. Do them top to bottom.
Install Claude Code and connect the Brain. Follow the guide for your operating system — jump to the setup guides ↓
Link your shared team skills folder so your living skills load every session. Team Skill Suite setup guide
Understand the resync so you know how and when the Brain refreshes. See Run & maintain ↓
Send feedback, suggest a skill, or book time with the LBL team. See Need help? ↓
Each guide walks you through installing Claude Code and connecting the Brain, step by step.
Step-by-step setup on a Mac — install, connect the repo, and confirm the Brain is loading.
Open the Mac guideThe Windows version of the same walkthrough, with the PC-specific steps called out.
Open the PC guideThe Brain rebuilds on a monthly rhythm. Here's how it refreshes and how your team's living skills stay connected.
Your monthly resync process and how to review it. You can also run the resync manually anytime by asking Claude.
Open the maintenance guideHow the Brain actually updates, plus how to connect your shared team skills folder so your living skills load every session.
Open the Team Skill Suite guideGood to know: the Brain is a static reference rebuilt monthly, not a live library. For anything generated in real time, the skill queries the source directly — the Brain doesn't hold it.
These automations run on a schedule (or on request) and handle the recurring work for you. Here's what's live today.
Pulls the action items from a recorded meeting and posts them to Slack for the team.
Each end of day, pulls residents in a given HubSpot status and posts a review summary to Slack.
Drafts your weekly status email from your Monday and HubSpot activity over the last 7 days. Drafts only, never sends.
Rebuilds the Brain each month, opens a pull request, and emails Molly to review and merge.
Reads the two feedback forms, stages any submitted skills, and emails Molly a plain summary.
Say "update my context" and Claude saves a snapshot of your priorities and active threads to your private memory.
Adds notes to a resident company in HubSpot from your input or a Fathom transcript, after you review them.
The Brain itself lives in one GitHub repository. Source documents are registered as rows in the tracker, then synthesized into the Brain each month.
CLAUDE.md, the synthesized content, and the skills. Updates flow from here to everyone's machine automatically.
Open the repositoryWhere source documents are linked so the monthly resync can pick them up. Add a row to feed something new into the Brain.
Open the source trackerAnyone on the team can send feedback or suggest a new skill. Two quick forms — that's it.
Have an idea for a new skill the team could use? Submit it here.
Open the skill submission formNo inbox to watch: a weekly digest skill reads both forms and emails a plain summary for review. Just submit and move on.
Editing the forms later: both Google Forms were created by ai@engine.xyz. To change questions or settings, sign in to that account (or ask its owner to share edit access).
The decks from your sessions, in the order they were delivered.
Your intro to working with Claude: Chat, Co-work, and Code, plus how to use it with precision. Open the deck →
The leadership install: what the Brain is, what's inside it, and how it's governed. Open the deck →
How skills and routines work, and how they connect to the Brain. Open the deck →
The June 15 team workshop: what's live, how to use it well, and how to bring discernment to the work. Open the deck →