bipinks/ghost-office - Page 2

cicd-patterns

Use when designing CI/CD pipeline architecture. Covers stage ordering (lint→test→build→deploy), quality gates, artifact management, multi-environment promotion, canary/blue-green deployments, rollback strategies, and pipeline-as-code patterns.

cloud-cost-optimization

Use when analyzing or reducing cloud spend. Covers FinOps practices, right-sizing recommendations, reserved instance/savings plan analysis, cost allocation tagging, unused resource cleanup, spot instance strategies, and budget alerting.

database-ops

Use when performing database administration, migrations, or performance tuning. Covers PostgreSQL, MySQL, Redis, and MongoDB operations including replication setup, backup/restore, index optimization, connection pooling, and maintenance windows.

docker-patterns

Use when creating Dockerfiles, docker-compose configs, or optimizing container images. Covers multi-stage builds, layer caching, security scanning with Trivy, non-root users, health checks, and Compose service orchestration.

github-workflows

Use when creating or modifying GitHub Actions CI/CD pipelines. Covers reusable workflows, matrix builds, OIDC authentication for cloud deploys, caching strategies, and deployment automation with environment protection rules.

kubernetes-patterns

Use when deploying to Kubernetes, writing manifests, or designing K8s architecture. Covers Deployments, Services, Ingress, HPA autoscaling, RBAC, network policies, security contexts, resource limits, and Helm chart patterns.

log-management

Use when setting up centralized logging, log parsing, or log-based alerting. Covers ELK/OpenSearch stack, CloudWatch Logs, Grafana Loki, structured logging formats (JSON), log rotation, retention policies, and correlation patterns.

monitoring-patterns

Use when setting up observability, alerting, or dashboards. Covers Prometheus scrape configs, Grafana dashboards, Datadog integration, SLO/SLI definition, error budgets, alerting rules, on-call rotation, and the four golden signals.

networking-patterns

Use when designing cloud networking architecture. Covers VPC CIDR planning, subnet strategies, DNS management with Route53/CloudFlare, CDN configuration, ALB/NLB load balancing, VPN tunnels, VPC peering, and private link patterns.

nginx-patterns

Use when configuring Nginx as a reverse proxy, load balancer, or web server. Covers upstream blocks, SSL termination, caching directives, rate limiting, security headers, gzip compression, and location block patterns.

secrets-management

Use when storing, rotating, or accessing secrets and credentials. Covers HashiCorp Vault setup, AWS Secrets Manager, environment variable best practices, secret injection in CI/CD, rotation policies, and zero-trust secret access patterns.

security-hardening

Use when hardening servers or cloud environments. Covers CIS benchmark implementation, OS-level hardening (SSH, firewall, fail2ban), cloud security posture, audit logging, compliance checks, and vulnerability scanning workflows.

ssl-tls-management

Use when setting up or renewing SSL/TLS certificates. Covers Let's Encrypt automation with certbot, ACM certificate requests, HSTS headers, OCSP stapling, mTLS for service-to-service auth, and certificate monitoring/rotation.

terraform-patterns

Use when writing, reviewing, or planning Terraform infrastructure code. Covers module design, state management (S3+DynamoDB), workspace strategy, variable validation, drift detection, and CI/CD integration with GitHub Actions.