Skip to content
Development
Command

/system-behavior-simulator

Simulate system performance under various loads with capacity planning, bottleneck identification, and optimization strategies.

From plugin
claude-command-suite
1.3k199 skills89 agents199 commands
Install
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/system-behavior-simulator

Context preview

What this command does when you run it.

Simulate system performance under various loads with capacity planning, bottleneck identification, and optimization strategies.

Command definition

system-behavior-simulator.md

System Behavior Simulator

Simulate system performance under various loads with capacity planning, bottleneck identification, and optimization strategies.

Instructions

You are tasked with creating comprehensive system behavior simulations to predict performance, identify bottlenecks, and optimize capacity planning. Follow this approach: **$ARGUMENTS**

1. Prerequisites Assessment

**Critical System Context Validation:**

  • **System Architecture**: What type of system are you simulating behavior for?
  • **Performance Goals**: What are the target performance metrics and SLAs?
  • **Load Characteristics**: What are the expected usage patterns and traffic profiles?
  • **Resource Constraints**: What infrastructure and budget limitations apply?
  • **Optimization Objectives**: What aspects of performance are most critical to optimize?

**If context is unclear, guide systematically:**

Missing System Architecture:
"What type of system needs behavior simulation?
- Web Application: User-facing application with HTTP traffic patterns
- API Service: Backend service with programmatic access patterns
- Data Processing: Batch or stream processing with throughput requirements
- Database System: Data storage and query processing optimization
- Microservices: Distributed system with inter-service communication

Please specify system components, technology stack, and deployment architecture."

Missing Performance Goals:
"What performance objectives need to be met?
- Response Time: Target latency for user requests (p50, p95, p99)
- Throughput: Requests per second or transactions per minute
- Availability: Uptime targets and fault tolerance requirements
- Scalability: User growth and load handling capabilities
- Resource Efficiency: CPU, memory, storage, and network optimization"

2. System Architecture Modeling

**Systematically map system components and interactions:**

Component Architecture Framework

System Component Mapping:

Application Layer:
- Frontend Components: User interfaces, single-page applications, mobile apps
- Application Services: Business logic, workflow processing, API endpoints
- Background Services: Scheduled jobs, message processing, batch operations
- Integration Services: External API calls, webhook handling, data synchronization

Data Layer:
- Primary Databases: Transactional data storage and query processing
- Cache Systems: Redis, Memcached, CDN, and application-level caching
- Message Queues: Asynchronous communication and event processing
- Search Systems: Elasticsearch, Solr, or database search capabilities

Infrastructure Layer:
- Load Balancers: Traffic distribution and health checking
- Web Servers: HTTP request handling and static content serving
- Application Servers: Dynamic content generation and business logic
- Network Components: Firewalls, VPNs, and traffic routing

Interaction Pattern Modeling

System Interaction Analysis:

Synchronous Interactions:
- Request-Response: Direct API calls and database queries
- Service Mesh: Inter-service communication with service discovery
- Database Transactions: ACID compliance and locking mechanisms
- External API Calls: Third-party service dependencies and timeouts

Asynchronous Interactions:
- Message Queues: Pub/sub patterns and event-driven processing
- Event Streams: Real-time data processing and analytics
- Background Jobs: Scheduled tasks and delayed processing
- Webhooks: External system notifications and callbacks

Data Flow Patterns:
- Read Patterns: Query optimization and caching strategies
- Write Patterns: Data ingestion and consistency management
- Batch Processing: ETL operations and data pipeline processing
- Real-time Processing: Stream processing and live analytics

3. Load Modeling Framework

**Create realistic traffic and usage pattern simulations:**

Traffic Pattern Analysis

Load Characteristics Modeling:

User Behavior Patterns:
- Daily Patterns: Peak hours, lunch dips, overnight minimums
- Weekly Patterns: Weekday vs weekend usage variations
- Seasonal Patterns: Holiday traffic, business cycle fluctuations
- Event-Driven Spikes: Marketing campaigns, viral content, news events

Request Distribution:
- Geographic Distribution: Multi-region traffic and latency patterns
- Device Distribution: Mobile vs desktop vs API usage patterns
- Feature Distribution: Popular vs niche feature usage ratios
- User Type Distribution: New vs returning vs power user behaviors

Load Volume Scaling:
- Concurrent Users: Simultaneous active sessions and request patterns
- Request Rate: Transactions per second with burst capabilities
- Data Volume: Payload sizes and data transfer requirements
- Connection Patterns: Session duration and connection pooling

Synthetic Load Generation

Load Testing Scenario Framework:

Baseline Load Testing:
- Normal Traffic: Typical daily usage patterns and request volumes
- Sustained Load: Constant traffic over extended periods
- Gradual Ramp: Slow traffic increase to identify scaling points
- Steady State: Stable load for performance baseline establishment

Stress Testing:
- Peak Load: Maximum expected traffic during busy periods
- Capacity Testing: System limits and breaking point identification
- Spike Testing: Sudden traffic increases and recovery behavior
- Volume Testing: Large data sets and high-throughput scenarios

Resilience Testing:
- Failure Scenarios: Component outages and degraded service behavior
- Recovery Testing: System restoration and performance recovery
- Chaos Engineering: Random failure injection and system adaptation
- Disaster Simulation: Major outage scenarios and business continuity

4. Performance Modeling Engine

**Create comprehensive system performance predictions:**

Performance Metric Framework

Multi-Dimensional Performance Analysis:

Response Time Metrics:
- Request Latency: End-to-end response time measurement
- Processing Time: Application logic execution duration
- Database Query Tim
Read more
Ships withclaude-command-suite

A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.

Get the whole plugin