'infrastructure' 검색 결과

Create Dockerfiles, automated build and deployment pipelines, Kubernetes configurations, and infrastructure templates. The skill also prepares deployment checks, rollback procedures, and incident response runbooks to support application releases and production operations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up automated build and deployment pipelines
• Packaging applications with Docker
• Managing Kubernetes and cloud infrastructure as code

Cross-framework infrastructure security audit across cloud, network, and CI/CD. Use for infrastructure and cloud security audits, security posture assessment, and validating technical controls for SOC 2, ISO 27001, and NIST CSF.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Translates performance test results into infrastructure scaling recommendations with cost estimates. Use when someone has load test data and needs to know what infrastructure changes are required to handle target traffic. Trigger words: capacity planning, scaling plan, infrastructure sizing, how many pods, RDS sizing, handle more traffic, scale for launch.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DevOps 与站点可靠性工程 (SRE) — 平台 / 基础设施 / 可靠性工程师的认知操作系统, 覆盖软件交付 + 运维全生命周期 (CI/CD 与发布工程 trunk-based + 渐进式发布 canary/blue-green/feature flag + GitOps Argo CD/Flux / 基础设施即代码 Terraform/OpenTofu/Pulumi/Ansible + policy-as-code OPA / 容器与编排 Docker/Kubernetes + Helm/Kustomize + service mesh Istio/Linkerd / 可观测性 Prometheus + Loki + OpenTelemetry + Honeycomb + eBPF + RED/USE / SLO-SLI-error budget 与可靠性工程 Google SRE 学科 + 容量规划 + 优雅降级 / 事件管理与 on-call 事件指挥 + PagerDuty + runbook + 无指责复盘 + MTTR / 云平台与 FinOps AWS/GCP/Azure + 成本优化 + 弹性伸缩 / 平台工程与开发者体验 IDP + Backstage + golden path + Team Topologies / DevSecOps 与供应链安全 shift-left + SBOM + SLSA + sigstore + Vault / 韧性与混沌工程 fault injection + game day + 安全科学 / DORA 指标与工程效能 部署频率 + 变更前置时间 + 变更失败率 + Accelerate 研究 / 数据库与有状态运维 schema 迁移 + 备份容灾) — 不含 通用应用开发 / 纯云销售认证速成 / 'DevOps = 跑 Jenkins 的岗位' 窄化误解 / ITIL 工单文化传统运维 (旧范式仅做边界) / 把手工运维 ClickOps 当稳态 (是 toil, 本 skill 核心反模式) (DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, Helm / Kustomize, service mesh Istio / Linkerd), (d) observability (the three pillars + beyond — metrics Prometheus / VictoriaMetrics, logs Loki / ELK, traces OpenTelemetry / Jaeger / Tempo, high-cardinality observability Honeycomb, eBPF, RED / USE methods, SLO-based alerting), (e) SLO / SLI / error budgets & reliability engineering (Google SRE discipline — service level objectives, error budget policy, toil budgets, capacity planning, load shedding, graceful degradation), (f) incident management & on-call (incident command, PagerDuty / Opsgenie, runbooks, blameless postmortems, MTTR / MTTD, error budget burn), (g) cloud platforms & FinOps (AWS / GCP / Azure well-architected, multi-region, cost optimization, autoscaling), (h) platform engineering & developer experience (internal developer platforms, Backstage, golden paths, self-service, Team Topologies), (i) DevSecOps & supply-chain security (shift-left, SAST / DAST, SBOM, SLSA, sigstore / cosign, secrets management Vault), (j) resilience & chaos engineering (chaos experiments, fault injection, game days, resilience engineering / safety science), (k) DORA metrics & engineering effectiveness (deployment frequency, lead time, change failure rate, MTTR, the Accelerate research), (l) databases & stateful operations (schema migrations, backups / DR, replication); NOT generic software development / app feature coding (是 平行学科, DevOps/SRE 关注 delivery + operability 不是 product feature), NOT pure cloud sales / certification cram without operational depth, NOT 'DevOps = a job title that runs Jenkins' 的窄化误解 (DevOps 是 文化 + 实践, SRE 是 Google 对 reliability 的工程化具体实现), NOT ITIL-heavy 传统运维 工单文化 (是 被 DevOps 取代的旧范式, 仅做边界标注), NOT manual ops / ClickOps as a steady state (是 toil, 本 skill 的核心反模式).) Master OS — automated mastery of DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, He

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides Infrastructure as Code best practices for Terraform, Pulumi, CloudFormation, and OpenTofu. Use when provisioning infrastructure, writing IaC modules, managing cloud resources, scanning for misconfigurations, or when user mentions 'terraform', 'pulumi', 'cloudformation', 'IaC', 'opentofu', 'infrastructure', 'tfsec', 'checkov', 'drift'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assesses energy transition investments with battery storage, grid modernization, EV charging, and hydrogen infrastructure analysis. Use when modeling energy transition assets, evaluating storage economics, or analyzing grid infrastructure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tracks infrastructure asset performance with maintenance planning, capital expenditure optimization, and end-of-life valuation. Use when managing infrastructure portfolios, planning capex, or evaluating asset condition.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluates social infrastructure including healthcare, education, and government facilities with availability-based revenue structures. Use when analyzing social infrastructure, evaluating availability payments, or assessing government-backed projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Values infrastructure assets with DCF, regulated asset base, and comparable transaction methodologies adjusted for regulatory and contractual frameworks. Use when valuing infrastructure assets, analyzing regulated utilities, or benchmarking infra transactions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scaffolds Pulumi TypeScript infrastructure-as-code projects, writes IaC code with proper resource configuration, manages Pulumi ESC environments for centralized secrets and configuration, configures OIDC authentication for cloud providers, and builds multi-language component resources. Use when the user asks to create Pulumi TypeScript projects, write Pulumi infrastructure code, set up ESC environments, configure OIDC for Pulumi, implement infrastructure automation with Node.js/TypeScript, create reusable Pulumi components, or work with stack references. Also use when the user mentions Pulumi with TypeScript, AWS/Azure/GCP infrastructure in TypeScript, or PulumiPlugin.yaml for multi-language components.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates Pulumi infrastructure-as-code projects in Go, configures OIDC authentication, integrates with Pulumi ESC for centralized secrets and configuration management, and builds multi-language component resources. Use when setting up Pulumi Go projects, writing infrastructure code with Go, configuring OIDC for Pulumi, using Pulumi ESC with Go, automating cloud infrastructure with Golang, creating reusable Pulumi components in Go, or working with pulumi-go-provider. Also use when the user mentions Pulumi with Go/Golang, AWS/Azure/GCP infrastructure in Go, or Go-based ComponentResource patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates Pulumi infrastructure-as-code projects in Python, defines cloud resources (AWS, Azure, GCP), configures ESC environments for secrets management, sets up OIDC authentication for secure deployments, and builds multi-language component resources. Use when creating Pulumi Python projects, writing infrastructure code, configuring cloud providers, managing secrets with Pulumi ESC, setting up OIDC for Pulumi, automating infrastructure deployments with Python, creating reusable Pulumi components in Python, or configuring Python toolchains (pip, poetry, uv) for Pulumi. Also use when the user mentions pyproject.toml with Pulumi, component_provider_host, or Python virtual environments for infrastructure code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan, evaluate, and adopt agent infrastructure for a named workload. Use for agent runtime/framework selection, agent evaluation or observability plans, memory and tool boundaries, infrastructure cost controls, and organizational adoption. Covers workload-first comparison, risk and recovery planning, held-out evaluation, cost accounting, and staged rollout. Not a vendor ranking or a production certification. NOT for implementing a specific agent behavior (agentic-patterns), building a specific agent (ai-engineer), prompt optimization (prompt-engineer), or conventional ETL workflow design (jury_rig-architect).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a standard folder layout for a DDD bounded context, a module organized around one business area. Generate TypeScript export files, keep infrastructure outside the public exports, and record the context in a domain model graph.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Starting a module for a new business area
• Splitting a monolith into bounded contexts
• Listing existing contexts

Manage AWS infrastructure as TypeScript code with SST v4 and Pulumi. Guides resource creation, connections between services, infrastructure tests, deployment checks, troubleshooting, and resource migrations while accounting for existing project conventions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding AWS resources to an SST v4 application
• Connecting resources and reviewing access permissions
• Adding infrastructure tests and reviewing deployment changes

Plan AWS infrastructure changes by checking application requirements and existing configuration, then selecting guidance from an external skill collection. Produces a reviewable plan covering access permissions, networking, cost assumptions, validation, and rollback.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing an AWS architecture for an existing application
• Reviewing an infrastructure plan before deployment
• Planning changes with minimal access permissions

Build and refactor AWS infrastructure with TypeScript or Python using AWS CDK, a toolkit for defining cloud resources in code. Get guidance on resource selection, Lambda packaging, stack organization, and checks before deployment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating AWS CDK stacks and reusable components
• Refactoring existing infrastructure code
• Adding Lambda functions to a CDK application

Investigate failed Agent QA runs using logs, recorded artifacts, and local source code. Make a focused code or test-definition repair, then verify the affected behavior while keeping product and infrastructure defects visible.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Repair a failed staging test from recorded evidence
• Update an outdated Agent QA YAML definition
• Distinguish test failures from product or infrastructure defects

Review code and infrastructure for security risks, map potential threats, and plan stronger defenses. The skill covers OWASP checks, attack and defense exercises, and incident response, with validation required for each environment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing code and infrastructure security
• Mapping threats with STRIDE or PASTA
• Planning stronger security settings

Turn feature requests, refactoring work, package upgrades, or infrastructure changes into structured Markdown implementation plans. Each plan defines concrete tasks, dependencies, affected files, and validation criteria for execution by AI agents or people.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan the implementation of a new feature
• Break refactoring work into concrete tasks
• Prepare a package upgrade plan

Review AWS infrastructure code and deployed resources against the six Well-Architected pillars. Produce risk-ranked findings, remediation examples, and an architecture diagram, then create GitHub issues for tracking improvements after user confirmation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review AWS infrastructure code and deployed resources
• Prioritize findings by risk
• Prepare infrastructure code remediation examples

Assess authorized networks through host discovery, service checks, vulnerability identification, and controlled exploitation. Follow a structured testing process to document attack paths, demonstrate business impact, clean up test artifacts, and prioritize remediation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing internal or external network security
• Validating firewall rules and network segmentation
• Verifying whether service vulnerabilities are exploitable

Plan authorized spearphishing simulations, personalized phishing tests aimed at specific people. Prepare scenarios and email infrastructure, track delivery and participant responses, and document findings to assess email security controls and improve security awareness.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing authorized phishing simulations for specific personnel
• Preparing test email delivery infrastructure
• Measuring delivery, opens, clicks, and reporting behavior