클라우드, CI/CD, 모니터링, 배포 (7.2천건)
Hierarchical memory organization for multi-session context retention. Wings (projects) > Rooms (domains) > Drawers (decisions). Semantic search across all memories with zero cloud dependency.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Web change monitoring - track changes on pages, detect updates, changelog diffs
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cloud Run deployment, BigQuery optimization, Pub/Sub patterns, IAM best practices
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pod design patterns, sidecar containers, init containers, config management, rolling updates, and resource limits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Email delivery infrastructure - DNS authentication (SPF/DKIM/DMARC), subdomain isolation, provider abstraction, template systems, bounce handling, warmup strategy, and deliverability monitoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dockerfile best practices, multi-stage builds, docker-compose, container networking, volume management, and image optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cloud cost optimization, token/API cost tracking, build time optimization, and FinOps patterns
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Completion Check: Verify Infrastructure Is Wired
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reference guide for Agentica multi-agent infrastructure APIs
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Traffic splitting, health checks, automated rollback, progressive delivery, and canary analysis for safe deployments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GitHub Actions workflow patterns, matrix builds, caching strategies, deployment pipelines, artifact management, and rollback procedures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lambda best practices, S3 event patterns, SQS/SNS fanout, and DynamoDB access patterns for serverless AWS architectures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure Functions, Cosmos DB modeling, Service Bus patterns, Bicep templates
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change Control with multiple features migrated together) when the team has agreed on a section-wide restructure plan. Trigger when the user names a specific feature or section to migrate (e.g. "let's migrate profiles", "start the Resource Manager migration", "do the entire Branches & Change Control section"). Each migration is its own branch off `demo/groups-diataxis-example`, its own PR back to that branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writing optimized, secure, multi-stage Dockerfiles with language-specific patterns (Python, Node.js, Go, Rust), BuildKit features, and distroless images. Use when containerizing applications, optimizing existing Dockerfiles, or reducing image sizes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Managing cloud infrastructure using declarative and imperative IaC tools. Use when provisioning cloud resources (Terraform/OpenTofu for multi-cloud, Pulumi for developer-centric workflows, AWS CDK for AWS-native infrastructure), designing reusable modules, implementing state management patterns, or establishing infrastructure deployment workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Managing secrets (API keys, database credentials, certificates) with Vault, cloud providers, and Kubernetes. Use when storing sensitive data, rotating credentials, syncing secrets to Kubernetes, implementing dynamic secrets, or scanning code for leaked secrets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply and enforce cloud resource tagging strategies across AWS, Azure, GCP, and Kubernetes for cost allocation, ownership tracking, compliance, and automation. Use when implementing cloud governance, optimizing costs, or automating infrastructure management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Async communication patterns using message brokers and task queues. Use when building event-driven systems, background job processing, or service decoupling. Covers Kafka (event streaming), RabbitMQ (complex routing), NATS (cloud-native), Redis Streams, Celery (Python), BullMQ (TypeScript), Temporal (workflows), and event sourcing patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and implement Internal Developer Platforms (IDPs) with self-service capabilities, golden paths, and developer experience optimization. Covers platform strategy, IDP architecture (Backstage, Port), infrastructure orchestration (Crossplane), GitOps (Argo CD), and adoption patterns. Use when building developer platforms, improving DevEx, or establishing platform teams.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage DNS records, TTL strategies, and DNS-as-code automation for infrastructure. Use when configuring domain resolution, automating DNS from Kubernetes with external-dns, setting up DNS-based load balancing, or troubleshooting propagation issues across cloud providers (Route53, Cloud DNS, Azure DNS, Cloudflare).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.