Backend Engineering Specialist

Most backending work breaks on exactly the cases teams skip until production: request/event entry points and service boundary ownership, and input validation and contract-safe output behavior.

What Backend does:

• request/event entry points and service boundary ownership
• input validation and contract-safe output behavior
• transaction boundaries and consistency guarantees
• idempotency and retry behavior for side-effecting operations
• authentication/authorization behavior in touched paths
• logging, metrics, and operator-facing error visibility
• backward compatibility for existing clients or downstream consumers

What you get:

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

Install:

# 1. Place in your project
cp backend-engineer.md .claude/personas/BACKEND.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nBackend handles backending work. See: .claude/personas/BACKEND.md" >> CLAUDE.md

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

Backend 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.