Skip to content

Thread Context — Context Manager Infrastructure Build

How to Resume This Work

This session built out the full infrastructure for the context-manager skill. If picking up where we left off, here's what matters:

Immediate Next Steps (in priority order)

  1. Check if context.rootphi.net is live — The subdomain was created and the first deploy succeeded, but Dreamhost DNS propagation was still in progress when the session ended. Try visiting https://context.rootphi.net — you should get a password prompt (username: brian). If still showing "Site Not Found", just wait longer.

  2. Rotate API keys — Earlier in this session (during triangulator work), OpenAI and Google API keys were visible in a terminal screenshot. They should be rotated:

  3. OpenAI: https://platform.openai.com/api-keys
  4. Google: https://aistudio.google.com/apikey

  5. After rotating, update ~/.zshrc and /mnt/.claude/api-keys.json

  6. Brian has more ideas for the skill — He explicitly said "If I have a couple more ideas for this skill, can we wait to install the latest?" The SKILL.md is updated with knowledge base synthesis but has NOT been packaged as a .skill file. Wait for Brian to share his additional ideas before packaging.

  7. Weekly deep synthesis task — Discussed but not yet set up. Should be a scheduled task that runs python3 -m mkdocs build equivalent + deeper cross-conversation analysis. Use the schedule skill when ready.

Critical: Don't Overwrite These Files

The following files are actively in use and should only be appended to or carefully edited:

  • ~/Documents/claude-context/GLOBAL.md — Brian's master profile
  • ~/Documents/claude-context/_index.md — Chat catalog (append new entries, don't restructure)
  • ~/Documents/claude-context/SETUP-GUIDE.md — Disaster recovery doc (just updated this session)
  • ~/Documents/claude-context-mkdocs.yml — MkDocs config (careful: must stay in ~/Documents/, not inside claude-context/)
  • ~/Documents/claude-context-deploy.sh — Deploy script (uses python3 -m mkdocs, not bare mkdocs)
  • ~/Documents/claude-context-backup.sh — Backup script (working, tested)
  • ~/.ssh/claude_backup_key — SSH private key (NEVER touch)

Architecture Notes for Other Skills

  • The context folder is ~/Documents/claude-context/ — In Cowork, it's mounted at whatever path Documents is accessible
  • Backups go to Dreamhost nightly at 10 PM — The backup script uses rsync with --delete, so removed local files WILL be removed from the backup
  • The website is a separate deploy — Running bash ~/Documents/claude-context-deploy.sh builds MkDocs from the markdown files and pushes to context.rootphi.net. It's NOT automatic — must be manually triggered or scheduled
  • MkDocs config quirk — The config file (claude-context-mkdocs.yml) MUST live in ~/Documents/ (parent of claude-context/), not inside it. MkDocs requires docs_dir to be a child of the config file's directory
  • Python path quirk — mkdocs command isn't on PATH. Always use python3 -m mkdocs instead
  • Password for the website is stored in ~/Documents/claude-context/.htpasswd (Apache hash format). Use ~/Documents/claude-context-reset-password.sh to change it

Brian's Working Style (relevant context)

  • Prefers direct recommendations over open-ended choices
  • Wants to understand the "why" before building
  • Self-described as disorganized — proactive naming/structure help is appreciated
  • Asks "is this the best way?" and "what are best practices?" frequently
  • Values systems that stay current and self-maintaining
  • Uses multiple Chrome profiles (rootphi, diamond mma, possibly others)