mirror of
https://github.com/wshobson/agents.git
synced 2026-03-18 09:37:15 +00:00
Add network-engineer subagent and update README
- Added network-engineer to Infrastructure & Operations section - Updated count from 34 to 35 subagents - Added to usage examples and workflow patterns - Added to Operations & Maintenance guidance section - Specializes in DNS, SSL/TLS, load balancing, and network debugging
This commit is contained in:
@@ -4,7 +4,7 @@ A comprehensive collection of specialized AI subagents for [Claude Code](https:/
|
||||
|
||||
## Overview
|
||||
|
||||
This repository contains 34 specialized subagents that extend Claude Code's capabilities. Each subagent is an expert in a specific domain, automatically invoked based on context or explicitly called when needed.
|
||||
This repository contains 35 specialized subagents that extend Claude Code's capabilities. Each subagent is an expert in a specific domain, automatically invoked based on context or explicitly called when needed.
|
||||
|
||||
## Available Subagents
|
||||
|
||||
@@ -30,6 +30,7 @@ This repository contains 34 specialized subagents that extend Claude Code's capa
|
||||
- **[database-optimizer](database-optimizer.md)** - Optimize SQL queries, design efficient indexes, and handle database migrations
|
||||
- **[terraform-specialist](terraform-specialist.md)** - Write advanced Terraform modules, manage state files, and implement IaC best practices
|
||||
- **[incident-responder](incident-responder.md)** - Handles production incidents with urgency and precision
|
||||
- **[network-engineer](network-engineer.md)** - Debug network connectivity, configure load balancers, and analyze traffic patterns
|
||||
- **[dx-optimizer](dx-optimizer.md)** - Developer Experience specialist that improves tooling, setup, and workflows
|
||||
|
||||
### Quality & Security
|
||||
@@ -91,6 +92,7 @@ Mention the subagent by name in your request:
|
||||
# Infrastructure and operations
|
||||
"Have devops-troubleshooter analyze these production logs"
|
||||
"Use cloud-architect to design a scalable AWS architecture"
|
||||
"Get network-engineer to debug SSL certificate issues"
|
||||
|
||||
# Data and AI
|
||||
"Get data-scientist to analyze this customer behavior dataset"
|
||||
@@ -110,6 +112,10 @@ Mention the subagent by name in your request:
|
||||
# Production incident workflow
|
||||
"Debug high memory usage in production"
|
||||
# Automatically uses: incident-responder → devops-troubleshooter → error-detective → performance-engineer
|
||||
|
||||
# Network connectivity workflow
|
||||
"Fix intermittent API timeouts"
|
||||
# Automatically uses: network-engineer → devops-troubleshooter → performance-engineer
|
||||
```
|
||||
|
||||
## Subagent Format
|
||||
@@ -182,6 +188,7 @@ payment-integration → security-auditor → Validated implementation
|
||||
- **incident-responder**: Critical outages requiring immediate response
|
||||
- **database-optimizer**: Query performance, indexing strategies
|
||||
- **terraform-specialist**: Infrastructure as Code, Terraform modules, state management
|
||||
- **network-engineer**: Network connectivity, load balancers, SSL/TLS, DNS debugging
|
||||
|
||||
### 📊 Analysis & Optimization
|
||||
- **performance-engineer**: Application bottlenecks, optimization
|
||||
|
||||
31
network-engineer.md
Normal file
31
network-engineer.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: network-engineer
|
||||
description: Debug network connectivity, configure load balancers, and analyze traffic patterns. Handles DNS, SSL/TLS, CDN setup, and network security. Use PROACTIVELY for connectivity issues, network optimization, or protocol debugging.
|
||||
---
|
||||
|
||||
You are a networking engineer specializing in application networking and troubleshooting.
|
||||
|
||||
## Focus Areas
|
||||
- DNS configuration and debugging
|
||||
- Load balancer setup (nginx, HAProxy, ALB)
|
||||
- SSL/TLS certificates and HTTPS issues
|
||||
- Network performance and latency analysis
|
||||
- CDN configuration and cache strategies
|
||||
- Firewall rules and security groups
|
||||
|
||||
## Approach
|
||||
1. Test connectivity at each layer (ping, telnet, curl)
|
||||
2. Check DNS resolution chain completely
|
||||
3. Verify SSL certificates and chain of trust
|
||||
4. Analyze traffic patterns and bottlenecks
|
||||
5. Document network topology clearly
|
||||
|
||||
## Output
|
||||
- Network diagnostic commands and results
|
||||
- Load balancer configuration files
|
||||
- SSL/TLS setup with certificate chains
|
||||
- Traffic flow diagrams (mermaid/ASCII)
|
||||
- Firewall rules with security rationale
|
||||
- Performance metrics and optimization steps
|
||||
|
||||
Include tcpdump/wireshark commands when relevant. Test from multiple vantage points.
|
||||
Reference in New Issue
Block a user