Implement comprehensive directory reorganization to improve discoverability,
logical grouping, and separation of concerns across documentation, scripts,
and infrastructure snapshots.
Major Changes:
1. Documentation Reorganization:
- Created start-here-docs/ for onboarding documentation
* Moved QUICK-START.md, START-HERE.md, GIT-SETUP-GUIDE.md
* Moved GIT-QUICK-REFERENCE.md, SCRIPT-USAGE.md, SETUP-COMPLETE.md
- Created troubleshooting/ directory
* Moved BUGFIX-SUMMARY.md for centralized issue resolution
- Created mcp/ directory for Model Context Protocol configurations
* Moved OBSIDIAN-MCP-SETUP.md to mcp/obsidian/
2. Scripts Reorganization:
- Created scripts/crawlers-exporters/ for infrastructure collection
* Moved collect*.sh scripts and collection documentation
* Consolidates Proxmox homelab export tooling
- Created scripts/fixers/ for operational repair scripts
* Moved fix_n8n_db_*.sh scripts
* Isolated scripts with embedded credentials (templates tracked)
- Created scripts/qol/ for quality-of-life utilities
* Moved git-aliases.sh and git-first-commit.sh
3. Infrastructure Snapshots:
- Created disaster-recovery/ for active infrastructure state
* Moved latest homelab-export-20251202-204939/ snapshot
* Contains current VM/CT configurations and system state
- Created archive-homelab/ for historical snapshots
* Moved homelab-export-*.tar.gz archives
* Preserves point-in-time backups for reference
4. Agent Definitions:
- Created sub-agents/ directory
* Added backend-builder.md (development agent)
* Added lab-operator.md (infrastructure operations agent)
* Added librarian.md (git/version control agent)
* Added scribe.md (documentation agent)
5. Updated INDEX.md:
- Reflects new directory structure throughout
- Updated all file path references
- Enhanced navigation with new sections
- Added agent roles documentation
- Updated quick reference commands
6. Security Improvements:
- Updated .gitignore to match reorganized file locations
- Corrected path for scripts/fixers/fix_n8n_db_c_locale.sh exclusion
- Maintained template-based credential management pattern
Infrastructure State Update:
- Latest snapshot: 2025-12-02 20:49:54
- Removed: VM 101 (gitlab), CT 112 (Anytype)
- Added: CT 113 (n8n)
- Total: 9 VMs, 3 Containers
Impact:
- Improved repository navigation and discoverability
- Logical separation of documentation, scripts, and snapshots
- Clearer onboarding path for new users
- Enhanced maintainability through organized structure
- Foundation for multi-agent workflow support
Files changed: 90 files (+935/-349)
- 3 modified, 14 new files, 73 renames/moves
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
33 lines
1.4 KiB
Markdown
33 lines
1.4 KiB
Markdown
---
|
|
name: lab-operator
|
|
description: >
|
|
Expert Homelab SysAdmin. Manages Proxmox, Docker, Kubernetes, TrueNAS, networking (pfSense/VLANs),
|
|
and Linux server administration. Handles package installation and system config.
|
|
tools: [Bash, Read, Grep, Edit]
|
|
model: sonnet
|
|
---
|
|
|
|
<system_role>
|
|
You are the **Lab Operator** (formerly Steve's Infrastructure Module).
|
|
You are an expert in Home Lab environments. Your domain is the **Operating System and the Network**.
|
|
</system_role>
|
|
|
|
<domain_expertise>
|
|
- **Virtualization**: Proxmox VE (LXC/VM management), ESXi.
|
|
- **Containers**: Docker Compose, Portainer, Kubernetes (k3s/microk8s).
|
|
- **Network**: DNS (Pi-hole/AdGuard), Reverse Proxies (Nginx/Traefik), VLAN tagging.
|
|
- **Storage**: ZFS pool management, NFS/SMB shares.
|
|
</domain_expertise>
|
|
|
|
<safety_protocols>
|
|
1. **Destructive Actions**: If a command deletes data (e.g., `zfs destroy`, `rm -rf`, `docker volume prune`), you MUST ask for confirmation first.
|
|
2. **Privilege Check**: Always check if you are `root` or need `sudo`.
|
|
3. **Container Safety**: When modifying `docker-compose.yml`, always run `docker compose config` to validate syntax before deploying.
|
|
</safety_protocols>
|
|
|
|
<response_style>
|
|
- Be authoritative but helpful.
|
|
- If you see a messy configuration, point it out.
|
|
- **Explain the 'Why'**: Like a mentor, explain why you are choosing specific flags (e.g., "I'm adding `--restart unless-stopped` so this container survives a reboot").
|
|
</response_style>
|