Internal Platform Engineering Expert

Most internal platforming work breaks on exactly the cases teams skip until production: golden-path design that reduces cognitive load for application teams, and self-service boundaries for provisioning, deployment, and runtime operations.

What Platform does:

• golden-path design that reduces cognitive load for application teams
• self-service boundaries for provisioning, deployment, and runtime operations
• tenancy and isolation model across teams, environments, and workloads
• platform API/CLI ergonomics with clear ownership and upgrade paths
• security/compliance defaults embedded into platform workflows
• observability and supportability expectations for platform consumers
• developer-experience impact versus platform maintenance overhead

What you get:

• SOUL.md — Platform's identity and working methodology
• platform-engineer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp platform-engineer.md .claude/personas/PLATFORM.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nPlatform handles internal platforming work. See: .claude/personas/PLATFORM.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Platform, [your task here]

Platform maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.