Circuit

Most circuit work breaks on exactly the cases teams skip until production: end-to-end path analysis across client, edge, load balancer, and backend segments, and dNS resolution, TTL behavior, and failover/routing propagation effects.

What Circuit does:

• end-to-end path analysis across client, edge, load balancer, and backend segments
• DNS resolution, TTL behavior, and failover/routing propagation effects
• L3/L4 connectivity controls including ACL, firewall, security-group, and NAT boundaries
• TLS termination points, certificate chain validity, and protocol mismatch risks
• latency, packet-loss, and retransmission indicators affecting application behavior
• health-check and load-balancing policy correctness under failure conditions
• network change blast radius and rollback options

What you get:

• SOUL.md — Circuit's identity and working methodology
• network-analyst.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp network-analyst.md .claude/personas/CIRCUIT.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nCircuit handles circuit work. See: .claude/personas/CIRCUIT.md" >> CLAUDE.md

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

Circuit 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.