Why daily rituals matter
Your local copy of the system drifts every day. Mark commits something in the morning. The setup scanner gets a new check. A skill gets refined. If you don't sync, you'll be working against a stale copy and your code will conflict with theirs. Five minutes a day prevents an afternoon of merge headaches.
The morning ritual (5 minutes)
Before any feature work. First thing.
1. Sync the repo
Every morning, first thing
Pull every change Mark, John, or Ewing pushed overnight. The skills folder is part of this repo (symlinked into Claude Code), so syncing the repo also syncs every skill.
cd ~/Github/next-chapter-os && git pull --rebase --autostash
2. Update dependencies if package.json changed
Whenever you see package.json in the diff
Someone added a new package. Your
node_modules is now out of sync.npm install
3. Type check
Right after syncing
If TypeScript fails right after pulling, something broke. Slack
#intern-help immediately. Don't try to fix it yourself.npx tsc --noEmit
4. Re-run the setup scanner
Once a week, or any time something feels off
The scanner catches drift. Doppler tokens expire. Skills folder permissions change. Dependencies go stale. Every Monday, run it.
curl -fsSL https://os.chapter.guide/setup.sh | bash
The all-in-one morning script
Save this as ~/bin/nc-morning and run nc-morning daily.
#!/usr/bin/env bash
# Save as ~/bin/nc-morning, then chmod +x ~/bin/nc-morning
# Run every morning. Aborts on first failure so you fix things in order.
set -e
REPO="$HOME/Github/next-chapter-os"
echo "→ Syncing repo..."
cd "$REPO" && git pull --rebase --autostash
echo "→ Checking if dependencies changed..."
if git diff HEAD@{1} HEAD --name-only | grep -q "^package.json$"; then
echo " package.json changed, running npm install"
npm install
fi
echo "→ Type check..."
npx tsc --noEmit
echo "→ Recent commits since you last looked:"
git log --oneline @{1}..HEAD 2>/dev/null || git log --oneline -5
echo "✓ Ready to build."
Install:
mkdir -p ~/bin && curl -fsSL https://os.chapter.guide/scripts/nc-morning.sh -o ~/bin/nc-morning && chmod +x ~/bin/nc-morning
The end-of-day ritual (3 minutes)
Before you close the laptop.
1. Commit what you have
Before standing up
Even if it's not done. A WIP commit on a branch beats lost work. Commit messages can be terse: "wip: classify dropdown half done."
git add -A && git commit -m "wip: <what you did>" && git push
2. Check your activity
5 minutes before sign-off
Look at what the system thinks you did today. If it disagrees with your memory, something is off.
open https://os.chapter.guide/admin/interns
3. Note one thing for tomorrow
Last 60 seconds
Future-you needs a starting point. Write one sentence about what you're picking up tomorrow morning. Stick it in the commit message or your notes app.
The Friday ritual (15 minutes)
Once a week. Don't skip.
Re-run the setup scanner
Doppler tokens expire. Symlinks break. Stuff drifts. Friday is the day you catch it before Monday morning bites you.
curl -fsSL https://os.chapter.guide/setup.sh | bash
Write a 3-line week summary
What you shipped. What you learned. One question for next week. Drop it in
#intern-checkins on Slack so Ewing can see the arc of your work.Hand off to your partner
Charlie tells Bear what classifications he should expect to see Monday. Bear tells Charlie what warm leads need attention. The handoff contract is your shared language. Use it explicitly on Friday.
What can go wrong if you skip rituals
| Skipped ritual | What breaks | How long to fix |
|---|---|---|
| Morning sync | Your code conflicts with main. Merge hell. | 30 - 90 minutes |
| npm install | Cryptic build errors. Imports that don't resolve. | 15 - 45 minutes |
| Type check | You ship a broken build. Vercel rejects it. Whole team blocked. | 1 - 3 hours |
| End-of-day commit | Lose work. Mac sleeps wrong. Branch reverts. | Hours of redo |
| Friday scanner | Doppler token expires. Monday morning you can't run anything. | 30 - 60 minutes |
Reminders the system will send you
You don't have to remember any of this. The system will nudge.
- If the repo hasn't pulled in 24 hours the next Claude Code session will warn you.
- If your last setup scan is older than 7 days you'll see a yellow banner on every onboarding page.
- If your Doppler token expired any script that needs credentials will tell you to run
doppler login. - If you've been silent for 2+ hours during work time the stuck detector pings Ewing. He'll Slack you.
The reminders are help signals, not surveillance. If you see one, it means the system is trying to make sure you're not stuck. Reply to Ewing's Slack with the specific thing you're working on, not "I'm fine." We want to unblock you fast.