senior-backend

Design scalable backend architectures with API design, data modeling, and service boundaries.

467|103|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/borghei/Claude-Skills --skill senior-backend-borghei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: senior-backend
Source: https://github.com/borghei/Claude-Skills/tree/main/engineering/senior-backend
Command: npx skills add https://github.com/borghei/Claude-Skills --skill senior-backend-borghei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides expert guidance for building robust, scalable backends, bridging the gap between product requirements and reliable server-side implementations.

Core Features & Use Cases

  • API design (REST, GraphQL, gRPC) for scalable services.
  • Database design and optimization for high-traffic systems.
  • Microservices architecture with well-defined boundaries.
  • Message queues and event-driven patterns for decoupled services.
  • Caching strategies and performance tuning.
  • Authentication and authorization across services.
  • Observability, monitoring, and tracing for performance and reliability.
  • Real-world use case: design a multi-service e-commerce backend with separate catalog, order, and payment services.

Quick Start

Create a minimal backend scaffold with endpoints for a resource, connect to a PostgreSQL database, wire a Redis cache, and implement a basic authentication flow. Start by scaffolding using your preferred stack (Node.js/Express, Python/FastAPI) and ensure API endpoints, DB models, and a simple service communication pattern are wired.

Frequently Asked Questions about senior-backend

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

FAQPage Schema
How do I design scalable microservices with well-defined service boundaries?

To design scalable microservices, you define clear service boundaries by domain, implement robust APIs for communication, and apply caching and observability patterns. This ensures reliable, decoupled server-side ecosystems across complex domains.

What's the best way to structure a backend scaffold with PostgreSQL and Redis caching?

The best way to structure a backend scaffold is to wire API endpoints to PostgreSQL database models and connect a Redis cache. You implement a basic authentication flow alongside a simple service communication pattern to ensure scalable data access.

When should I use gRPC versus REST or GraphQL for API design?

API design for scalable services requires choosing between REST, GraphQL, and gRPC based on interaction needs. REST suits standard resource operations, GraphQL optimizes client-driven queries, and gRPC enables efficient inter-service messaging in microservice architectures.

How do I implement authentication and authorization across multiple backend services?

Implementing authentication and authorization across multiple backend services requires enforcing best practices and reference patterns for secure access. You apply concrete design decisions to maintain consistent security boundaries throughout your microservices architecture.

How do I add observability and tracing to a microservices architecture?

Adding observability and tracing to a microservices architecture involves applying monitoring patterns and reference designs for performance tuning. This enforces reliability across complex domains by providing visibility into service communication and system health.