From platform-skills
Hands-on guidance for platform and DevOps engineers working with Kubernetes, Terraform, GitOps, GitHub Actions, AWS, Azure, Linkerd, Linux, networking, and compliance. Use when designing or troubleshooting Kubernetes workloads and RBAC, writing Terraform modules, configuring Flux or Argo CD, setting up CI/CD pipelines, managing cloud identity and IAM, handling secrets, diagnosing DNS or VPC connectivity, operating a service mesh, applying product thinking to developer experience, or implementing SOC 2 compliance controls in Terraform — at any scale, for any team size.
npx claudepluginhub nitinjain999/platform-skills --plugin platform-skillsThis skill uses the workspace's default tool permissions.
Use this skill for hands-on help with Kubernetes, GitOps, cloud infrastructure, CI/CD, secrets management, service mesh, Linux administration, networking, and platform product thinking — whether you are a solo developer or part of a large platform team.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Use this skill for hands-on help with Kubernetes, GitOps, cloud infrastructure, CI/CD, secrets management, service mesh, Linux administration, networking, and platform product thinking — whether you are a solo developer or part of a large platform team.
Match the task to the right layer:
Terraform: Provision cloud primitives, cluster bootstrap, shared services, identity, networking, and policy foundations.Kubernetes: Define workload, namespace, RBAC, service, policy, and platform baseline patterns that apply across distributions.OpenShift: Adapt Kubernetes patterns to OpenShift-native routing, security, operator, and tenancy constraints.Flux or Argo CD: Reconcile in-cluster desired state after bootstrap and manage promotion of workloads or platform add-ons.GitHub Actions: Validate, package, test, and promote changes. Keep workflows declarative and reusable.AWS or Azure: Apply provider-specific account, subscription, identity, and governance patterns.Linkerd: Apply service mesh for automatic mTLS, golden-signal observability, and traffic management between workloads.Linux & Networking: Diagnose Linux systems and network problems — DNS resolution, load balancer routing, VPC/VNet design, kernel tuning, and connectivity troubleshooting.Platform Mindset: Treat developers as customers. Apply product thinking, friction audits, DevEx metrics, RFC/ADR processes, incident communication, and blameless post-mortems.Cross-platform: Design repo boundaries, ownership, promotion flows, and security controls first.Compliance: Implement SOC 2 Trust Services Criteria controls in Terraform — IAM least privilege, encryption, audit logging, network security, and change management. Run Checkov for continuous enforcement and collect evidence for auditors.If a task spans multiple areas, decide which layer owns the source of truth and keep the other layers consumers of that state.
ss -tulnp), then L3 reachability (ping), L4 connectivity (nc -zv), L7 response (curl -v), and security group / NACL rules last. Do not skip layers.terraform fmt -check -recursive, terraform validate, tflint --recursive, security scan (tfsec or checkov), then plan. Do not let format or lint failures reach the plan step.default_tags (provider level) or Azure merge(local.common_tags, {...}) (module local) so the baseline is applied once, not repeated per resource. Back it with AWS Tag Policies or Azure Policy so resources created outside Terraform are also covered.For design or implementation work, provide output in this order:
When asked to generate code, start from the thinnest useful slice that proves the pattern and note which layer remains intentionally out of scope.
Load only the files needed for the current request.
For explicit, repeatable workflows use these commands:
/platform-skills:debug — structured troubleshooting for any platform symptom/platform-skills:review — production-readiness review of any manifest, Terraform, or workflow/platform-skills:terraform — full fmt/validate/tflint/security pipeline + blast radius review/platform-skills:gitops — Flux CD and Argo CD reconciliation troubleshooting/platform-skills:linkerd — Linkerd mTLS, injection, policy, and multi-cluster diagnostics/platform-skills:linux — Linux administration, DNS, load balancing, VPC/VNet, and connectivity troubleshooting/platform-skills:product — product thinking, friction audits, DevEx, RFC/ADR, incident updates, post-mortems/platform-skills:compliance — SOC 2 gap analysis, control implementation, evidence collection, and Checkov remediation for Terraform