architecture-design-principles

Distill platform engineering expertise into architectural principles for self-service developer platforms.

3|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/broomva/skills --skill architecture-design-principles-broomva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-design-principles
Source: https://github.com/broomva/skills/tree/main/skills/governance/architecture-design-principles
Command: npx skills add https://github.com/broomva/skills --skill architecture-design-principles-broomva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexity of building and maintaining self-service developer platforms, helping teams avoid common pitfalls like architectural coupling, churn, and the collapse of infrastructure layers.

Core Features & Use Cases

  • Principle Mapping: Provides a structured map of 14 durable engineering principles, from IaC layering to edge-centralized cross-cutting concerns.
  • Operational Guidance: Offers deep-dive references on platform migration, sidecar vs. native proxy tradeoffs, and long-term maintenance strategies.
  • Use Case: Use this Skill when designing an internal developer platform, planning a fleet-wide infrastructure migration, or auditing a long-lived codebase for maintenance burden and coupling.

Quick Start

Invoke the architecture-design-principles skill to receive a detailed breakdown of the three IaC layers and how to apply them to your current platform architecture.

Frequently Asked Questions about architecture-design-principles

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

FAQPage Schema
How do I design an internal developer platform to avoid architectural coupling?

Apply three IaC layers to separate foundational, platform, and application infrastructure. This layering strategy prevents infrastructure collapse and reduces coupling in self-service developer platforms during system design and migration.

What are the tradeoffs of using a sidecar proxy vs a native proxy for platform engineering?

The Skill provides operational guidance on sidecar vs native proxy tradeoffs for control-plane design, evaluating isolation against performance. It applies SRE and DDD patterns to help teams choose the right proxy architecture for distributed services.

When do I need SRE and DDD patterns for infrastructure migration?

You need SRE and DDD patterns when planning fleet-wide infrastructure migration or auditing long-lived codebases for maintenance burden. These canonical patterns ground platform engineering decisions in durable operational standards.

How do I audit a long-lived codebase for maintenance burden and coupling?

Audit a long-lived codebase by evaluating it against 14 durable engineering principles, focusing on IaC layering and edge-centralized cross-cutting concerns. This identifies architectural coupling and guides long-term maintenance strategies for distributed services.

Does this platform engineering guidance support modern tooling context for 2026-era infrastructure?

Yes, this guidance satisfies requirements for canonical grounding in SRE, DORA, and DDD patterns while providing modern 2026-era tooling context. It distills senior platform engineering expertise into actionable architectural principles for current distributed services.