- Use individual folders with CLAUDE.md files for task sets, versioned separately in Git, to manage sysadmin tasks with Claude Code.
- Structure folders by project and task group (e.g., app maintenance, DBA) including server info, project context, and common tasks for progressive disclosure.
- Enhance security by using SSH keys, bastion hosts, and ~/.ssh/config aliases to avoid storing credentials in repos.
- Pair rigorously with Claude Code: research each step, ask for plans and verification, and review every SSH command before execution.
- Document processes in CLAUDE.md after tasks (e.g., backups) to create self-documenting playbooks with verification steps and known issues.
- Extend the approach to cloud-first environments using CLI tools (e.g., gcloud, aws) with proper access management.
- Separate sysadmin CLAUDE.md from code repos to avoid context confusion and allow overarching infrastructure views.
- Update CLAUDE.md regularly to accumulate resolved issues and reflections, improving future resolution time and documentation.
- Make CLAUDE.md human-readable—summarize or convert to HTML for team sharing and cross-server queries.