Skip to content

nWave-ai/nWave / nWave/skills/nw-production-readiness

nw-production-readiness

Verified

Monitoring, observability, operational procedures, CI/CD lessons learned, and quality gate definitions. Load when assessing production readiness or validating operational excellence.

Production Readiness

Monitoring and Observability

Application Monitoring

  • Performance: response time | throughput | latency percentiles (P50, P95, P99)
  • Resources: CPU | memory | database connections | cache hit rates
  • Errors: exception tracking | error rate trends | integration failure detection
  • Business: KPI tracking | conversion funnels | feature usage | revenue impact

Infrastructure Monitoring

Server/container health and resource utilization | Network performance and connectivity | Storage capacity and I/O performance | Security event detection.

Alerting Tiers

TierConditionResponse
PageService down, data loss risk, security breachImmediate response
UrgentError rate >2x baseline, latency SLA breachResponse within 15 min
WarningCapacity >80%, error rate trending upResponse within 1 hour
InfoDeployment complete, metric threshold crossedReview next business day

Operational Procedures

Incident Response

  1. Detect: automated alerting identifies issue
  2. Triage: classify severity, assign responder
  3. Communicate: notify stakeholders per severity level
  4. Resolve: apply fix or rollback
  5. Review: post-incident review within 48 hours
  6. Improve: update runbooks and monitoring based on findings

Maintenance Procedures

Regular update and patching schedule | Backup verification (test restores quarterly) | Security vulnerability scanning (automated, weekly) | Performance baseline recalibration (after major changes).

Knowledge Transfer

Operational runbooks for common procedures | Architecture documentation with system diagrams | Deployment procedures and configuration management | Troubleshooting guides for known failure modes.

Quality Gates for Production Readiness

Before declaring production-ready, all must pass:

  • All acceptance tests passing
  • Unit coverage meets project standard (default: >= 80%)
  • Integration tests validated
  • Performance validated under realistic load
  • Security scan completed (0 critical, 0 high)
  • Monitoring and alerting configured
  • Logging structured and searchable
  • Rollback procedure documented and tested
  • Runbook created for operational procedures
  • On-call team trained on new feature

For CI/CD architecture lessons and measurement coupling pitfalls, see cicd-and-deployment skill.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall