backend-architect

Design scalable backend architectures with service boundaries and resilience patterns.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/aolus-software/clean-elysia-prisma --skill backend-architect-aolus-software
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/aolus-software/clean-elysia-prisma/tree/main/.claude/backend-architect
Command: npx skills add https://github.com/aolus-software/clean-elysia-prisma --skill backend-architect-aolus-software

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You are a backend system architect specializing in scalable, resilient, and maintainable backend systems and APIs.

Core Features & Use Cases

  • Define service boundaries, data contracts, and integration patterns for scalable systems.
  • Plan resilience, observability, security, and deployment strategies for microservices.
  • Provide architecture guidance for API design, data flows, and inter-service communication.

Quick Start

Define the high-level service boundaries and contracts for your backend project and outline resilience and observability requirements.

Frequently Asked Questions about backend-architect

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

FAQPage Schema
How do I define service boundaries and data contracts for a new microservices architecture?

Microservices architecture design defines service boundaries and data contracts by establishing bounded contexts and integration patterns. This specifies inter-service communication and data flows to ensure scalable, maintainable backend systems.

What resilience patterns should I plan for backend microservices?

Resilience patterns for backend microservices include planning circuit breakers, retries, and timeouts. Architecture design incorporates these mechanisms alongside observability requirements to prevent cascading failures and maintain system stability.

How do I design an API with scalable integration patterns?

Scalable API design establishes integration patterns and data contracts for backend communication. Architecture planning defines service boundaries and data flows to structure APIs that support resilient inter-service communication.

What's the best way to plan deployment orchestration and observability for microservices?

Deployment orchestration and observability for microservices are planned by outlining resilience requirements and deployment strategies. Architecture design integrates security and monitoring to ensure scalable, maintainable backend operations.

When do I need to define bounded contexts for backend architecture?

Bounded contexts for backend architecture are needed when planning new services or APIs to define clear service boundaries. This process structures data contracts and integration patterns, ensuring scalable and maintainable microservices design.