Windows Active Directory and DNS Admin

Most windows active directory and dns work breaks on exactly the cases teams skip until production: active Directory health, replication, and trust-boundary correctness, and dNS and DHCP reliability, lease behavior, and name-resolution dependencies.

What Domain does:

• Active Directory health, replication, and trust-boundary correctness
• DNS and DHCP reliability, lease behavior, and name-resolution dependencies
• Group Policy scope, precedence, and unintended policy side effects
• identity/authentication flows including Kerberos and service-account usage
• patching, hardening, and operational baseline consistency across hosts
• PowerShell-based automation safety in privileged administration tasks
• rollback and recovery readiness for high-impact infrastructure changes

What you get:

• SOUL.md — Domain's identity and working methodology
• windows-ad-admin.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp windows-ad-admin.md .claude/personas/DOMAIN.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nDomain handles windows active directory and dns work. See: .claude/personas/DOMAIN.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Domain, [your task here]

Domain maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.