backend-architect

Designs scalable backend services, APIs, and microservices architectures with resilience and observability patterns.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill backend-architect-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/Tgoldi/claude-skills/tree/main/backend-architect
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill backend-architect-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing backend systems that scale, stay resilient under failure, and remain maintainable requires deep expertise across API design, distributed systems, and observability. This Skill provides structured architectural guidance so you can define service boundaries, API contracts, and communication patterns correctly from the start. ## Core Features & Use Cases - API Design: Guides REST, GraphQL, gRPC, WebSocket, and webhook design including versioning, pagination, and contract-first documentation with OpenAPI. - Microservices & Event-Driven Architecture: Covers service decomposition, saga patterns, CQRS, message queues, event streaming with Kafka, and service mesh patterns. - Resilience & Observability: Builds in circuit breakers, retries, timeouts, distributed tracing, structured logging, and metrics from day one. - Use Case: Ask it to design a microservices architecture for a multi-tenant SaaS platform, and it will produce service boundary definitions, API contracts, communication patterns, and a Mermaid architecture diagram. ## Quick Start Ask the assistant to design a RESTful API and microservices architecture for your application, including authentication, resilience patterns, and an observability strategy.

Frequently Asked Questions about backend-architect

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

FAQPage Schema
How do I design a microservices architecture for a new application?

Start by defining service boundaries using domain-driven design and bounded contexts, then choose synchronous or asynchronous communication patterns per interaction. This Skill guides decomposition, API contracts, resilience patterns, and observability setup for each service.

REST vs GraphQL vs gRPC: which API style should I choose?

REST fits resource-oriented public APIs, GraphQL suits clients needing flexible queries and real-time subscriptions, and gRPC works best for high-performance internal service-to-service calls. The Skill covers schema design, versioning, and streaming patterns for all three.

How do I add circuit breakers and retries to service communication?

Implement circuit breakers with tools like resilience4j, combine them with exponential backoff and jitter for retries, and enforce timeouts with deadline propagation. The Skill covers failure isolation, fallback strategies, and idempotency for safe retries.

Does this Skill design database schemas?

No, database schema design is explicitly deferred to a database-architect skill. This Skill focuses on service architecture, API contracts, and data integration patterns like CQRS and database-per-service, working after the data layer is designed.

When should I not use a backend architecture Skill?

Skip it for code-level bug fixes, small scripts without architectural concerns, or frontend and UX questions. It is intended for designing new services, defining service boundaries, and planning resilience, scaling, and observability.