backend-architect

Designs scalable backend services, API contracts, and microservices architectures with resilience patterns.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/nperepichka/Antigravity --skill backend-architect-nperepichka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/nperepichka/Antigravity/tree/main/config/skills/backend-architect
Command: npx skills add https://github.com/nperepichka/Antigravity --skill backend-architect-nperepichka

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 instead of refactoring later. ## Core Features & Use Cases - API Design & Contracts: Design REST, GraphQL, gRPC, and WebSocket APIs with versioning, pagination, OpenAPI documentation, and contract testing strategies. - Microservices & Event-Driven Architecture: Define service boundaries with domain-driven design, plan saga and CQRS patterns, and build event-driven systems with Kafka, RabbitMQ, or SQS. - Resilience & Observability: Build in circuit breakers, retries, timeouts, distributed tracing, structured logging, and metrics as first-class architectural concerns. - Use Case: You are building a multi-tenant SaaS platform and need to decompose a monolith into services. The Skill produces service boundary definitions, API contracts, an architecture diagram, an authentication strategy, and a rollout plan with documented trade-offs. ## Quick Start Ask the agent to design a microservices architecture for your application, including service boundaries, API contracts, 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. The Skill guides you through API contracts, resilience patterns, observability, and a rollout plan with documented trade-offs.

Should I use REST, GraphQL, or gRPC for my API?▼

REST fits resource-oriented public APIs, GraphQL suits clients with varied data needs and real-time subscriptions, and gRPC works best for high-performance internal service-to-service calls. The Skill covers schema design, versioning, and contract testing for all three.

How do I add resilience patterns like circuit breakers and retries?▼

Apply circuit breakers with failure detection and fallback strategies, retries with exponential backoff and jitter, and timeouts with deadline propagation. The Skill covers tools like resilience4j and patterns like bulkheads, idempotency, and graceful degradation.

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, database-per-service, and event-driven data synchronization.

When should I not use this backend architecture Skill?▼

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