backend-architect

Design scalable backend systems with service boundaries and API contracts.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/AmidVoshakul/chatorai --skill backend-architect-amidvoshakul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/AmidVoshakul/chatorai/tree/main/assets/skills/backend-architect
Command: npx skills add https://github.com/AmidVoshakul/chatorai --skill backend-architect-amidvoshakul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of designing robust backend systems by providing a structured framework for service decomposition, API contract definition, and resilience planning.

Core Features & Use Cases

  • API Design & Patterns: Expert guidance on REST, GraphQL, gRPC, and WebSocket implementations.
  • Microservices & Event-Driven Architecture: Strategies for service boundaries, message queues, and distributed transactions.
  • Resilience & Observability: Implementation of circuit breakers, retry patterns, and monitoring strategies to ensure system reliability.

Quick Start

Use the backend-architect skill to design a microservices architecture for a new e-commerce platform including service boundaries and inter-service communication patterns.

Frequently Asked Questions about backend-architect

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

FAQPage Schema
How do I design service boundaries for a microservices architecture?

Designing service boundaries for a microservices architecture requires applying domain-driven design to define service decomposition and establish resilient inter-service communication patterns.

What is the best way to define API contracts for distributed systems?

Defining API contracts for distributed systems involves selecting appropriate integration strategies like REST, GraphQL, gRPC, or WebSocket to ensure maintainable and high-performance communication.

How do I implement resilience patterns like circuit breakers in backend infrastructure?

Implementing resilience patterns like circuit breakers in backend infrastructure ensures system reliability by preventing cascading failures and providing structured retry mechanisms for distributed transactions.

When should I use event-driven architecture for microservices?

You should use event-driven architecture for microservices when managing complex distributed transactions and requiring asynchronous message queues to achieve scalable and maintainable backend systems.

Does this approach support observability and monitoring for high-performance APIs?

Yes, this approach supports observability and monitoring for high-performance APIs by integrating specific resilience patterns and monitoring strategies to ensure system reliability.