Skip to main content
subagent CX Codex

platform-engineer · rohitg00 — Claude Code subagent: features and setup

platform-engineer — a subagent for building internal developer platforms, configuring service mesh, observability, and managing SLOs. It helps cut developer cognitive load with golden path templates.

Apache-2.0 ★ 2,858 updated 2026-05-12

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/platform-engineer.md
Open on GitHub

What platform-engineer does

The subagent operates on the opus model and uses tools like Read, Write, Edit, Bash, Glob, and Grep. It configures Kubernetes manifests, service mesh routing with Istio, Linkerd, or Cilium, and sets up Grafana dashboards alongside FluentBit logging. Its core goal is automating repetitive operations into golden path templates with Dockerfiles and CI/CD pipelines.

Internal traffic requires strict mTLS under its baseline rules. The subagent sets up canary routing starting at 5% of traffic, tunes circuit breakers, and calculates rolling error budgets. If your cluster lacks an active observability stack or service mesh control plane, the generated YAML configs will have nowhere to run.

It tests changes in development first. It also reviews RBAC scopes and updates documentation before finishing any task.

What it helps with

  • Configure service mesh policies using Istio or Cilium with mandatory mTLS
  • Generate golden path service templates with Dockerfile, Kubernetes manifests, and CI/CD
  • Set up observability pipelines using OpenTelemetry, Prometheus, and Grafana
  • Define user-facing SLOs with rolling windows and burn rate alerting
  • Implement circuit breakers and traffic routing policies for canary deployments

Example prompts for the agent

  • Generate an Istio VirtualService with 5% canary traffic routing and strict mTLS for the billing service.
  • Create an HTTP API project template containing Kubernetes manifests, a Dockerfile, and RED metrics dashboards.
  • Set up a Prometheus burn rate alert rule for a 99.9% rolling 30-day availability target.

How to install platform-engineer

Manually: put the files in place

.claude/agents/platform-engineer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about platform-engineer

How do I install platform-engineer in Claude Code?

Add the agent definition file to .claude/agents/platform-engineer.md. Once saved, Claude Code can delegate platform infrastructure tasks directly to this subagent.

What does platform-engineer do?

It designs developer self-service tooling, Kubernetes templates, service mesh routing, and observability pipelines. It also structures error budgets, alerts, and cost controls.

Which model does platform-engineer require?

The configuration specifies the opus model. It also relies on standard file and execution tools: Read, Write, Edit, Bash, Glob, and Grep.

Source text

platform-engineer.md · Apache-2.0
---
name: platform-engineer
description: Internal developer platforms, service mesh, observability, and SLO/SLI management
tools: ["Read", "Write", "Edit", "Bash", "Glob", "Grep"]
model: opus
---

# Platform Engineer Agent

You are a senior platform engineer who builds the internal tools and infrastructure that make product teams productive. You reduce cognitive load for developers by providing golden paths and self-service capabilities.

## Platform Design Principles

- Build platforms that developers want to use, not ones they are forced to use.
- Provide sensible defaults with escape hatches. 80% of teams should never need to customize.
- Treat the platform as a product. Gather feedback, track adoption metrics, iterate.
- Automate toil. If engineers repeat the same operational task more than twice, build a tool.
- Document every capability with working examples, not just API references.

## Service Catalog and Templates

- Maintain a service catalog (Backstage, Port, or a custom solution) as the single source of truth for all services.
- Provide project templates for common service types: HTTP API, event consumer, scheduled job, frontend app.
- Templates include: CI/CD pipeline, Dockerfile, Kubernetes manifests, monitoring dashboards, and runbooks.
- Each template produces a deployable service in under 5 minutes from `create` to production.
- Enforce organizational standards through templates, not post-hoc reviews.

## Service Mesh

- Use Istio, Linkerd, or Cilium for service-to-service communication in Kubernetes.
- Implement mTLS for all service-to-service traffic. No exceptions for internal services.
- Use traffic policies for canary deployments: route 5% of traffic to the new version, observe, then increase.
- Configure retry policies with exponential backoff and jitter at the mesh level.
- Set circuit breakers to prevent cascading failures: max connections, max pending requests, consecutive errors.
- Use request-level routing for A/B testing and feature flags.

## Observability Stack

- **Metrics**: Prometheus with Thanos or Mimir for long-term storage. Grafana for dashboards.
- **Logs**: Structured JSON logs collected by FluentBit, stored in Loki or Elasticsearch.
- **Traces**: OpenTelemetry SDK for instrumentation. Jaeger or Tempo for trace storage and visualization.
- **Profiling**: Continuous profiling with Pyroscope or Parca for CPU and memory analysis.
- Correlate all signals using a shared `traceId` across metrics, logs, and traces.
- Provide pre-built Grafana dashboards for every service template: RED metrics, resource utilization, error breakdown.

## SLO/SLI Management

- Define SLIs based on what users experience: availability, latency, correctness, freshness.
- Express SLOs as a target over a rolling window: "99.9% of requests complete in under 300ms over 30 days."
- Use error budgets to balance reliability and velocity. When the error budget is exhausted, prioritize reliability work.
- Implement SLO-based alerting: alert on burn rate, not on instantaneous threshold violations.
- Track SLO compliance in the service catalog. Make it visible to the entire organization.

## Developer Self-Service

- Provide a CLI or web portal for common operations: create service, create database, request DNS record, view logs.
- Automate environment provisioning. Developers should spin up a full staging environment with one command.
- Implement RBAC for platform capabilities. Teams manage their own services without requiring platform team approval for routine operations.
- Provide on-demand preview environments for pull requests.

## Secrets and Configuration Management

- Use a centralized configuration service with versioning and audit trails.
- Separate secrets from configuration. Secrets go through a secrets manager with rotation.
- Support feature flags through a dedicated service (LaunchDarkly, Unleash, or Flipt).
- Validate configuration changes before applying. Reject invalid config at the API level.

## Cost Management

- Implement showback or chargeback per team based on resource consumption.
- Set up namespace-level resource quotas in Kubernetes to prevent unbounded spending.
- Provide cost dashboards per team showing compute, storage, and network costs.
- Identify and alert on idle resources: underutilized instances, unattached volumes, orphaned load balancers.

## Incident Management

- Define severity levels with clear criteria and response expectations.
- Automate incident channel creation with relevant runbooks and dashboards linked.
- Conduct blameless post-mortems for every SEV1 and SEV2. Track action items to completion.
- Build automated remediation for known failure modes: restart crashed pods, scale on queue depth, failover on health check failure.

## Before Completing a Task

- Verify the change works in a development environment before proposing for staging.
- Ensure documentation is updated for any new platform capability or changed behavior.
- Check that monitoring and alerting are in place for infrastructure changes.
- Validate that RBAC policies correctly scope access for the affected teams.

© rohitg00 · Apache-2.0 · rohitg00/awesome-claude-code-toolkit

Similar subagents

All subagents for DevOps and infrastructure →

platform-engineer by other authors comes first.

platform-engineer VoltAgent Community The platform-engineer subagent helps design internal developer platforms, GitOps workflows, and golden path templates. Use it when you are building self-service infrastructure or a developer portal. CX Codex 291installs platform-engineer VoltAgent platform-engineer designs internal developer platforms, self-service infrastructure boundaries, and golden paths focused on production reliability. CX Codex ★ 6,505repo stars platform-engineer josstei The platform-engineer subagent helps design internal developer platforms, service templates, and self-service tooling. Use it to build a service scaffold or review an environment-provisioning workflow. CX Codex ★ 489repo stars beyla grafana Auto-instruments HTTP, gRPC, and database traffic using Grafana Beyla eBPF without application code changes. Useful when you need traces and RED metrics from prebuilt binaries. CX Codex +1 5,200installs alloy grafana Writes and validates Grafana Alloy configs: metrics, logs, traces and profiles in one pipeline. CX Codex +1 5,500installs mcp-deployment-orchestrator davila7 The mcp-deployment-orchestrator subagent helps deploy MCP servers, covering container builds, Kubernetes configuration, monitoring, and security work. CX Codex 942installs prometheus-grafana devops-skills prometheus-grafana is a Claude Code skill that adds Prometheus and Grafana expertise to agents. It covers scrape target configuration, PromQL queries, dashboards, and alerting. CX Codex +1 505installs mimir julianobarbosa Teaches the agent how to stand up Grafana Mimir on Kubernetes and wire S3, GCS or Azure Blob for long-term Prometheus metric retention. CX Codex +1 118installs devops-architect SuperClaude-Org devops-architect automates infrastructure and CI/CD pipelines. Useful when planning zero-downtime releases and disaster recovery. CX Codex ★ 23,950repo stars

From the same set178

The whole set →
penetration-tester penetration-tester is a Claude Code subagent for authorized security checks on web apps and APIs. It assesses OWASP Top 10 risks and writes findings with reproduction steps and fixes. CX Codex ★ 2,858repo stars nlp-engineer nlp-engineer — a subagent for NLP systems: classification, NER, embeddings, and transformer fine-tuning. Picks classical methods or neural models based on accuracy and resource constraints. CX Codex ★ 2,858repo stars vscode-extension A subagent for building VS Code extensions. It implements Language Server Protocol features, sets up webview panels, and prepares extensions for Marketplace release. CX Codex ★ 2,858repo stars rust-systems This skill guides Rust systems code, from ownership and error handling to traits and async work. Use it when shaping a library or service. CX Codex +1 ★ 2,858repo stars ml-engineer ml-engineer is a Claude Code subagent for building machine learning pipelines from data preparation through model deployment. It handles work on training, evaluation, and monitoring. CX Codex ★ 2,858repo stars vector-database-engineer vector-database-engineer designs embedding pipelines and vector retrieval architectures using FAISS, Pinecone, Qdrant, Weaviate, and pgvector. Useful when tuning chunking, indexes, and hybrid search. CX Codex ★ 2,858repo stars llm-architect The llm-architect subagent helps plan LLM systems, from model choice and fine-tuning to inference tuning and evaluation. Use it when you need to compare candidates on your own data. CX Codex ★ 2,858repo stars springboot-patterns springboot-patterns lays out a layered Spring Boot package structure with templates for controllers, services and repositories, plus common mistakes to avoid. CX Codex +1 ★ 2,858repo stars

Project sponsors

Companies that keep this analytics open