platform-engineering

Design and implement Internal Developer Platforms with golden paths, GitOps, and self-service infrastructure.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/masermediagroup-stack/maser-media --skill platform-engineering-masermediagroup-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-engineering
Source: https://github.com/masermediagroup-stack/maser-media/tree/main/.cursor/skills/community/ai-design-components/skills/platform-engineering
Command: npx skills add https://github.com/masermediagroup-stack/maser-media --skill platform-engineering-masermediagroup-stack

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 implementation of Internal Developer Platforms (IDPs) that provide self-service infrastructure, reduce cognitive load, and accelerate developer productivity through golden paths and platform-as-product thinking. ## 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), with build-vs-buy decision frameworks. - Golden Path Templates: Create opinionated software templates for web apps, data pipelines, ML services, event-driven microservices, and scheduled jobs with security, observability, and CI/CD baked in. - Adoption & Maturity Planning: Assess platform maturity across five levels, structure platform teams (centralized, federated, hub-and-spoke), and drive adoption with phased rollout strategies and DORA/SPACE metrics. - Use Case: A 300-engineer company deploys Backstage with three golden paths and Argo CD, cutting onboarding from 2 days to 2 hours and increasing deployment frequency from 2x/week to 10x/day. ## Quick Start Help me bootstrap an internal developer platform with Backstage, one golden path template for a Node.js web app, 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 with Backstage?▼

Start with a foundation phase: form a 3-5 person platform team, interview developers about pain points, deploy Backstage with SSO, and create one golden path template. Then pilot with 2-3 teams, iterate on feedback, and expand to 20-50% of teams over 6-12 months.

Should I build on Backstage or buy a commercial IDP like Port?▼

Choose Backstage for large organizations (1000+ engineers) with dedicated platform teams needing deep customization. Choose commercial IDPs like Port or Humanitec for mid-size organizations (100-1000 engineers) needing faster time-to-value (3-6 months) with limited platform engineering resources.

What is a golden path template in platform engineering?▼

A golden path is an opinionated software template covering 80% of use cases, including repository structure, infrastructure as code, CI/CD pipelines, observability instrumentation, and security configurations. Templates provide escape hatches for the remaining 20% of advanced use cases.

How do I measure developer platform success?▼

Track DORA metrics (deployment frequency, lead time, MTTR, change failure rate), SPACE framework dimensions (satisfaction, performance, activity, communication, efficiency), and platform-specific metrics like adoption rate, self-service rate, and onboarding time.

What is the difference between Argo CD and Flux for GitOps?▼

Argo CD provides declarative GitOps for Kubernetes with multi-cluster management, ApplicationSets, and a strong UI, holding the highest trust score among GitOps tools. Flux offers a composable toolkit approach with image automation and is suited for GitOps-native operations.

When should a platform team use a federated model instead of centralized?▼

Use a federated model for organizations with 500-2000+ engineers across multiple business units with differing needs. A central team of 5-10 engineers owns the core platform while 1-2 embedded engineers per business unit handle domain-specific integrations and support.