claude-home/CLAUDE.md

Home Lab Documentation System

Core Instructions

• Always have permission to run tests
• Check imports when writing code (prevent NameErrors)
• Temp files go in .claude/tmp/, clean up after
• Prefer editing existing files over creating new ones
• After complex tasks, prompt to save learnings to the KB (use /save-doc)
• At session end, ask: "Should I update our documentation?"

Knowledge Base

Use the kb-search MCP tools to find documentation. For code files, also load the relevant dev CONTEXT: .py → development/python-CONTEXT.md, .js/.ts → development/nodejs-CONTEXT.md, .sh → development/bash-CONTEXT.md.

Documentation Maintenance

• New tech without a directory → offer to create /{tech}/ structure
• New error solved → offer to add to {tech}/troubleshooting.md
• New scripts created → offer to update {tech}/scripts/CONTEXT.md

CI/CD

• Docs-only PRs (all .md files) are auto-approved and merged by the auto-merge-docs workflow