backend-architect

Designs scalable backend service architectures, API contracts, and resilience patterns.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill backend-architect-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/TongQuan/skills/backend-architect
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill backend-architect-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing backend systems that scale, stay resilient under failure, and remain maintainable is hard without a structured architectural approach. This Skill guides the AI to act as a backend system architect, producing service boundaries, API contracts, and resilience strategies grounded in proven patterns. ## Core Features & Use Cases - API Design: Models REST, GraphQL, gRPC, and WebSocket APIs with versioning, pagination, and OpenAPI documentation. - Microservices Architecture: Defines service boundaries with domain-driven design, event-driven communication, saga patterns, and circuit breakers. - Security & Observability: Plans OAuth 2.0/JWT authentication, rate limiting, distributed tracing, metrics, and alerting. - Use Case: Ask it to design a microservices architecture for a multi-tenant SaaS platform, and receive service boundary definitions, API contracts, a Mermaid architecture diagram, and a rollout plan. ## Quick Start Ask the AI 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 SaaS platform?▼

Start by defining service boundaries using domain-driven design and bounded contexts, then choose synchronous (REST, gRPC) or asynchronous (message queues, events) communication. This Skill produces service definitions, API contracts, resilience patterns, and a rollout plan.

What API style should I use: REST, GraphQL, or gRPC?▼

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 documentation for all three.

How do I add resilience patterns like circuit breakers to backend services?▼

Apply circuit breakers with tools like resilience4j, combine them with exponential backoff retries, timeouts, and bulkhead isolation. The Skill guides failure detection, fallback strategies, and graceful degradation design.

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 such as CQRS and database-per-service.

When should I not use a backend architecture Skill?▼

Avoid it for code-level bug fixes, small scripts without architectural concerns, or frontend and UX questions. It is intended for service design, integration patterns, and system-level planning.