feat: Enhanced Claude Code configuration with comprehensive best practices

- Updated project CLAUDE.md with detailed commands, workflows, and guidelines
- Added environment configuration and performance monitoring commands
- Enhanced security guidelines and commit message conventions
- Created 5 custom slash commands for common MEV bot development tasks:
  * /analyze-performance - Comprehensive performance analysis
  * /debug-issue - Structured debugging workflow
  * /implement-feature - Feature implementation framework
  * /security-audit - Security audit checklist
  * /optimize-performance - Performance optimization strategy
- Updated global CLAUDE.md with universal best practices
- Improved file organization and development standards

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/commands/debug-issue.md

@@ -0,0 +1,43 @@
+# Debug MEV Bot Issue
+
+Debug the following MEV bot issue: $ARGUMENTS
+
+## Debugging Protocol:
+1. **Issue Understanding**: Analyze the problem description and expected vs actual behavior
+2. **Log Analysis**: Examine relevant log files in `logs/` directory
+3. **Code Investigation**: Review related source code and recent changes
+4. **Reproduction**: Attempt to reproduce the issue in a controlled environment
+5. **Root Cause**: Identify the underlying cause and contributing factors
+
+## Debugging Commands:
+```bash
+# Check logs
+tail -f logs/mev-bot.log
+
+# Run with debug logging
+LOG_LEVEL=debug ./mev-bot start
+
+# Check system resources
+htop
+iostat -x 1 5
+
+# Network connectivity
+nc -zv arbitrum-mainnet.core.chainstack.com 443
+
+# Go runtime stats
+curl http://localhost:9090/debug/vars | jq
+```
+
+## Investigation Areas:
+- **Connection Issues**: RPC endpoint connectivity and WebSocket stability
+- **Parsing Errors**: Transaction and event parsing failures
+- **Performance**: High CPU/memory usage or processing delays  
+- **Concurrency**: Race conditions or deadlocks
+- **Configuration**: Environment variables and configuration issues
+
+## Output Requirements:
+- Clear problem identification
+- Step-by-step reproduction instructions
+- Root cause analysis
+- Proposed solution with implementation steps
+- Test plan to verify the fix