operations
This skill should be used when the user asks to "review for production", "check production readiness", "evaluate resilience", "assess observability", "review ops", "run chaos experiments", or discusses deployment, monitoring, incident response, failure modes, or chaos engineering.
What this skill does
# Operations Production readiness evaluation focused on resilience, observability, and incident response. ## Resilience ### Failure Modes - What can fail? List all external dependencies - Blast radius: If X fails, what else breaks? - Graceful degradation: Partial failure ≠ total failure? ### Patterns | Pattern | Purpose | Check | |---------|---------|-------| | **Timeouts** | Prevent hung connections | Every external call has one? | | **Circuit Breaker** | Stop cascading failures | On critical paths? | | **Bulkhead** | Isolate failures | Separate thread pools? | | **Retry** | Handle transient failures | With backoff? Bounded? | ## Observability ### The RED Method | Metric | What | Why | |--------|------|-----| | **R**ate | Requests per second | Traffic understanding | | **E**rrors | Failed requests | Problem detection | | **D**uration | Latency distribution | Performance tracking | ### Logging - Structured (JSON, not free text) - Correlation IDs across services - Appropriate levels (not everything is ERROR) - PII redaction ### Tracing - Distributed tracing enabled? - Spans for all external calls? - Context propagation working? ## Capacity - **Scaling**: Horizontal preferred, auto-scaling configured? - **Limits**: Memory, CPU, connections all bounded? - **Backpressure**: What happens at 2x load? 10x? - **Rate Limiting**: Per-tenant/client quotas? ## Security Posture - **Secrets**: In vault, not env vars or code - **Network**: Least privilege, mTLS where possible - **Dependencies**: Vulnerability scanning in CI - **Access**: Audit logging for sensitive operations ## Incident Readiness - **Runbooks**: Documented recovery procedures - **On-call**: Rotation defined, escalation clear - **Rollback**: One-click, tested regularly - **Communication**: Status page, stakeholder notification ## Checklist ``` □ All external calls have timeouts □ Circuit breakers on critical paths □ Structured logging with correlation IDs □ RED metrics exposed □ Alerts are actionable (not noisy) □ Auto-scaling configured with limits □ Graceful shutdown implemented □ Health checks (liveness + readiness) □ Secrets in vault □ Runbook exists □ Rollback tested ``` ## Guild Members for Operations Primary: **Taleb** (resilience), **Erlang** (capacity), **Vector** (security) Secondary: **Lamport** (distributed failure), **Ixian** (metrics/validation) ## Additional Resources - **`references/chaos-patterns.md`** — Chaos engineering patterns and failure injection
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.