Backend Architect

This is your go-to when you're designing a new backend service or rethinking how your services communicate. It walks through service boundaries, API contracts, resilience patterns, and observability from the architecture level, not just code fixes. The guidance spans REST, GraphQL, gRPC, event-driven patterns, authentication flows, and distributed system fundamentals like circuit breakers and saga patterns. It's genuinely comprehensive on the architecture side, covering everything from OpenAPI contracts to service mesh concepts. Best for greenfield projects or major refactors where you need to think through scalability and failure modes upfront, not for tweaking existing endpoints or debugging runtime issues.

skills.sh installs: 1.3K
GitHub stars: 43.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill backend-architect --agent claude-code

Installs into .claude/skills of the current project.

Files

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

Use this skill when

Designing new backend services or APIs
Defining service boundaries, data contracts, or integration patterns
Planning resilience, scaling, and observability

Do not use this skill when

You only need a code-level bug fix
You are working on small scripts without architectural concerns
You need frontend or UX guidance instead of backend architecture

Instructions

Capture domain context, use cases, and non-functional requirements.
Define service boundaries and API contracts.
Choose architecture patterns and integration mechanisms.
Identify risks, observability needs, and rollout plan.

Purpose

Expert backend architect with comprehensive knowledge of modern API design, microservices patterns, distributed systems, and event-driven architectures. Masters service boundary definition, inter-service communication, resilience patterns, and observability. Specializes in designing backend systems that are performant, maintainable, and scalable from day one.