platform_engineering

Design Internal Developer Platforms with golden paths, self-service portals, and GitOps delivery.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill platform-engineering-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform_engineering
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/platform_engineering
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill platform-engineering-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineering teams lose 30-40% of their time to infrastructure and tooling instead of shipping features. This Skill guides the design and rollout of Internal Developer Platforms (IDPs) that provide self-service infrastructure, reduce cognitive load, and treat the platform as a product. ## Core Features & Use Cases - IDP Architecture & Tooling: Design three-layer platforms with developer portals (Backstage, Port, Cortex), orchestration backends (Crossplane, Humanitec), and GitOps delivery (Argo CD, Flux). - Golden Paths & Templates: Create opinionated scaffolding templates with CI/CD, observability, and security baked in, plus policy-as-code guardrails (OPA, Kyverno). - Maturity & Adoption: Assess platform maturity across five levels, measure success with DORA and SPACE metrics, and drive adoption through phased rollout plans. - Use Case: A 300-engineer company replaces manual provisioning with a Backstage portal and three golden path templates, cutting onboarding from two days to two hours. ## Quick Start Help me design an internal developer platform with a Backstage portal, one golden path template, and Argo CD for GitOps deployments.

Frequently Asked Questions about platform_engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an internal developer platform?

Start with a platform team of 3-5 engineers, interview developers to find pain points, deploy a portal like Backstage, and create one golden path template. Pilot with 2-3 teams, iterate on feedback, then expand templates and integrations over 6-12 months.

Backstage vs Port: which developer portal should I choose?

Choose Backstage for large enterprises (1000+ engineers) with a dedicated platform team needing deep customization. Choose Port for mid-size organizations (100-1000 engineers) wanting faster time-to-value with a managed solution and fewer platform engineers.

What is a golden path in platform engineering?

A golden path is an opinionated project template covering repository structure, infrastructure as code, CI/CD pipelines, observability, and security configurations. It handles roughly 80% of use cases while providing documented escape hatches for the remaining 20%.

How do I measure developer platform success?

Track DORA metrics (deployment frequency, lead time, MTTR, change failure rate), SPACE framework dimensions, and platform-specific metrics like adoption rate, self-service rate, and onboarding time. Combine quantitative metrics with developer satisfaction surveys.

When should I not build a custom developer platform?

Avoid heavy platform investment in very small teams where PaaS solutions suffice, or when you lack dedicated platform engineers. A lightweight setup with two golden paths and managed infrastructure can support 50 developers with just two engineers.