backend-architect

Designs scalable backend architectures, API contracts, and microservices communication patterns.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill backend-architect-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/backend-architect
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill backend-architect-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing backend systems that scale, stay resilient under failure, and remain maintainable requires deep expertise across APIs, microservices, messaging, and observability. This Skill provides structured architectural guidance so you can define service boundaries, contracts, and resilience patterns correctly from the start. ## Core Features & Use Cases - API Design: Guides REST, GraphQL, gRPC, WebSocket, and webhook design with versioning, pagination, and OpenAPI contract-first documentation. - Microservices & Event-Driven Architecture: Covers service boundaries with DDD, saga and CQRS patterns, Kafka/message-queue integration, and circuit breakers. - Security, Resilience & Observability: Addresses OAuth 2.0/JWT authentication, rate limiting, retry strategies, distributed tracing, and monitoring. - Use Case: Ask it to design a microservices architecture for a multi-tenant SaaS platform and receive service boundaries, API contracts, communication patterns, and a rollout plan. ## Quick Start Ask the agent to design a RESTful API and microservices architecture for your application, including authentication, resilience patterns, and 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 (REST, gRPC) or asynchronous (message queues, events) communication per interaction. Build in resilience patterns like circuit breakers and retries, and plan observability with logging, metrics, and distributed tracing from the start.

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

REST fits resource-oriented public APIs with simple caching needs, GraphQL suits clients with flexible data requirements and real-time subscriptions, and gRPC works best for high-performance internal service-to-service communication. The choice depends on consumers, latency requirements, and team expertise.

How do I migrate a monolith to microservices?

Use the strangler pattern to gradually extract capabilities into services while the monolith keeps running. Define clear service boundaries first, route traffic through an API gateway, and migrate incrementally rather than rewriting everything at once.

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 communication patterns, and works after the data layer has been 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 services, defining contracts, and planning resilience, scaling, and observability.