platform-infrastructure

SKILL.md

Design and scale internal platforms by abstracting common capabilities and planning infrastructure before hitting limits.

Focuses on understanding platform purpose, assessing organizational readiness, identifying leverage points, and designing for actual developer adoption rather than theoretical needs

Emphasizes invisible infrastructure qualities like reliability, performance, and privacy as critical success factors alongside visible features

Recommends proactive infrastructure scaling planning to avoid bottlenecks during usage spikes, while still avoiding premature optimization

Flags common mistakes: building for abstract futures, lacking product ownership, client-side tracking over server-side, and underestimating migration costs

Platform Infrastructure

Help the user design and scale internal platforms and shared technical infrastructure using insights from 5 product and engineering leaders.

How to Help

When the user asks for help with platform infrastructure:

Understand the platform's purpose - Ask whether they're building for internal developers, external partners, or both

Assess organizational readiness - Determine if they have the adoption and governance structures to support a platform

Identify the leverage points - Help them find where platform investment creates the most value multiplication

Design for adoption - Ensure the platform solves real developer problems, not theoretical ones

Core Principles

Abstract common capabilities into shared infrastructure

Daniel Lereya: "We actually stopped for the first time and say, 'What is the column like?' And we also organized all the product architecture around it... making the work of adding a new column just thinking about the specific." Scaling feature velocity requires abstracting repetitive components into a shared infrastructure so developers only focus on unique logic.