fred/homelab-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
homelab-docs/.claude-context.md

8.2 KiB
Raw Permalink Blame History

Fred's Projects - Claude Code Context

Source of Truth: C:\Users\Fred\projects

This file provides context to Claude Code about all of Fred's active projects. When Fred starts a Claude Code session in VS Code Insiders, Claude should be aware of this ecosystem.

Active Projects

1. claude-workflows

Path: C:\Users\Fred\projects\claude-workflows Purpose: Shared slash commands and ADHD-friendly productivity tools for Claude Code Status: Active development Key Features:

  • /push - Quick commit and push
  • /eod - End of day workflow
  • ADHD assistant system with proactive interventions
  • Auto-discovery scripts for cross-project setup
  • Personality-driven assistant behavior (personality.md)

Context Files:

  • .assistant/personality.md - Defines ADHD-friendly behavior rules
  • .assistant/state.json.template - Session state tracking template

2. VA-Strategy

Path: C:\Users\Fred\projects\VA-Strategy Purpose: Personal VA disability claims management system Status: Active - in progress Goal: 100% VA disability rating via TDIU Current Rating: 60% combined, 30% highest single (PTSD)

Context Files:

  • CLAUDE.md - Project-specific guidance for Claude Code
  • Gemini.md - Master strategic roadmap
  • tracking/master-tracking.md - Claim status tracker
  • tracking/immediate-action-checklist.md - Priority to-do list

Key Workflows:

  • Headache tracking for migraine claim (50% target)
  • PTSD statement preparation (70% target)
  • Sleep apnea evidence collection (50% target)
  • Git-based document versioning

3. infrastructure

Path: C:\Users\Fred\projects\infrastructure Purpose: Home network, Home Assistant, smart home automation Status: Active maintenance + active projects

Active Subprojects:

  • Voice Assistant: Local GPU-accelerated voice system (Gaming PC + Surface Go)
  • Furnace Control: ESP32-based smart furnace controller (planning phase)
  • Home Assistant: Main HA configuration
  • ESPHome: Device configurations (garage controller, planned furnace)

Context Files:

  • README.md - Infrastructure overview
  • docs/FURNACE-PROJECT.md - ESP32 furnace project
  • voice-assistant/CLAUDE.md - Voice system context

Tech Stack: Home Assistant, ESPHome, MQTT, Docker, Ollama, Whisper, Piper TTS

4. claude-code-history

Path: C:\Users\Fred\projects\claude-code-history Purpose: Session history and state persistence for Claude Code Status: Background system

Contains:

  • Session transcripts
  • State files
  • Project history
  • Stats cache

5. config

Path: C:\Users\Fred\projects\config Purpose: Shared configuration files Status: Minimal/placeholder

ADHD Assistant Behavior

Claude Code should operate with ADHD-friendly principles when working with Fred:

Core Principles

  1. Proactive, Not Reactive - Notice patterns and intervene
  2. Gentle Nudging - Suggest, don't command
  3. Celebrate Wins - Acknowledge all completions
  4. Context Preservation - Remember across sessions
  5. No Judgment - Side quests are valid exploration

Side Quest Detection

When Fred starts working on something unrelated to the current project, Claude should:

🤔 I notice we've shifted focus:

   Current project: [X]
   New work: [Y]

   This looks like a side quest. Would you like to:
   1. Continue (I'll track it)
   2. Switch to the [Y] project
   3. Make this a new project
   4. Park it and return to [X]

Project-Specific Context Loading

When Fred opens a project in VS Code, Claude should:

  1. Check for project-specific CLAUDE.md file
  2. Load project context and current status
  3. Greet with relevant session info
  4. Track scope drift across project boundaries

Shared Resources

Claude Shared Directory

Path: C:\Users\Fred\claude-shared\ (symlinked from claude-workflows) Contains:

  • Shared slash commands
  • ADHD assistant state file (~/.claude-assistant/state.json)
  • Setup scripts for auto-discovery

Slash Commands (Available Everywhere)

  • /push - Auto-commit and push
  • /eod - End of day workflow
  • /focus - Check current goals (in development)
  • /sidequest - Log tangents (in development)
  • /stuck - Get unstuck (in development)
  • /reflect - Session review (in development)

Cross-Project Workflows

When Fred Starts a Side Quest

Example: Working on VA-Strategy, starts researching ESPHome for furnace

Claude should:

  1. Detect context shift (VA → infrastructure)
  2. Offer to switch projects
  3. If continuing, track as side quest in state file
  4. Set timer for check-in (30 min default)
  5. Preserve VA-Strategy context for return

When Fred Opens VS Code in a Project

Claude should:

  1. Read .claude-context.md (this file) for ecosystem awareness
  2. Read project-specific CLAUDE.md if exists
  3. Check state file for active session
  4. Greet with context: 
    📋 Welcome back, Fred!

Project: [name]
Last session: [time ago]
Status: [brief summary]

Ready to continue?

State Management

Session State File

Location: ~/.claude-assistant/state.json (Windows: C:\Users\Fred\.claude-assistant\state.json)

Tracks:

  • Current project and goal
  • Active side quests
  • Stuck signals
  • Session history
  • Cross-project context

State File Schema

{
  "current_session": {
    "project": "VA-Strategy",
    "started_at": "2025-12-13T10:00:00Z",
    "primary_goal": "Complete headache log entries",
    "side_quests": [
      {
        "topic": "Research ESP32 temperature sensors",
        "original_project": "VA-Strategy",
        "target_project": "infrastructure",
        "started_at": "2025-12-13T10:30:00Z",
        "status": "in_progress"
      }
    ]
  }
}

VS Code Insiders Setup

Recommended Settings

To enable full context awareness in VS Code Insiders:

  1. Multi-root Workspace - Open all projects simultaneously
  2. Workspace-Specific Settings - Per-project .vscode/settings.json
  3. Claude Context Files - This file + project-specific CLAUDE.md files

Creating Multi-Root Workspace

{
  "folders": [
    {
      "path": "C:\\Users\\Fred\\projects\\claude-workflows",
      "name": "🎯 Claude Workflows"
    },
    {
      "path": "C:\\Users\\Fred\\projects\\VA-Strategy",
      "name": "🏥 VA Strategy"
    },
    {
      "path": "C:\\Users\\Fred\\projects\\infrastructure",
      "name": "🏠 Infrastructure"
    }
  ],
  "settings": {
    "claude.contextFiles": [
      "C:\\Users\\Fred\\projects\\.claude-context.md"
    ]
  }
}

Save as: C:\Users\Fred\projects\fred-workspace.code-workspace

Quick Reference

Project Quick IDs

  • claude-workflows: Productivity tools, ADHD assistant
  • VA-Strategy: VA claims, documentation, tracking
  • infrastructure: Home automation, voice assistant, ESPHome
  • claude-code-history: Session history (background)
  • config: Shared configs (minimal)

When to Switch Projects

You're Talking About... Project Action
Slash commands, ADHD features claude-workflows Switch or side quest
VA claims, medical evidence VA-Strategy Switch or side quest
Home Assistant, ESP32, voice assistant infrastructure Switch or side quest
New idea unrelated to current work TBD Offer to create new project

For Claude Code: Session Start Checklist

When Fred starts VS Code Insiders:

  • Read .claude-context.md (this file)
  • Identify current project from workspace/folder
  • Read project-specific CLAUDE.md if exists
  • Check ~/.claude-assistant/state.json for active session
  • Greet with relevant context
  • Be ready to detect and manage side quests
  • Apply ADHD-friendly behavior from personality.md

Last Updated: 2025-12-13 Maintained By: Fred with Claude Code assistance Purpose: Provide ecosystem-level context for intelligent, ADHD-friendly Claude Code sessions

Reference in New Issue View Git Blame Copy Permalink