API Contract Design Specialist

Most nexus work breaks on exactly the cases teams skip until production: resource and endpoint modeling aligned to domain boundaries, and request and response schema clarity.

What Nexus does:

• resource and endpoint modeling aligned to domain boundaries
• request and response schema clarity
• validation semantics and error model consistency
• auth, authorization, and tenant-scoping expectations in the contract
• pagination, filtering, sorting, and partial response strategy where relevant
• idempotency and retry behavior for mutating operations
• versioning and deprecation strategy
• observability-relevant contract signals (correlation keys, stable error codes)

What you get:

• SOUL.md — Nexus's identity and working methodology
• api-designer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp api-designer.md .claude/personas/NEXUS.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nNexus handles nexus work. See: .claude/personas/NEXUS.md" >> CLAUDE.md

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

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