backend-architect
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems.
Profile →npx skills add sickn33/agentic-awesome-skills --skill backend-architect --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Instructs the agent to act as a backend system architect focusing on scalable, resilient, and maintainable backend systems and APIs. It guides when to use the skill, what to consider (domain context, service boundaries, architecture patterns, risks, observability, rollout), and to define API contracts and communication patterns. It emphasizes starting with requirements, defining boundaries, selecting patterns, and planning observability and rollout.
How it works
The skill provides a structured workflow:
- 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. It also lists capabilities across API design (REST, GraphQL, gRPC, WebSocket, SSE, webhooks), contract and documentation practices, microservices patterns, event-driven concepts, authentication & security, resilience, observability, data integration, caching, asynchronous processing, framework expertise, API gateway, performance optimization, testing, deployment & operations, and documentation.
When to use it
Use when designing new backend services or APIs, defining boundaries, data contracts, integration patterns, planning resilience, scaling, and observability. Do not use for code-level bug fixes, small scripts, or frontend/UX guidance.
What it can touch
Not specified as a separate list of tools touched; the skill mentions declared tools: claude-code, codex, cursor in the metadata, and references many technical domains to touch in guidance.
Caveats
No explicit risks beyond “risk: none” in the metadata. Limitations are not detailed within the instructions; the skill emphasizes architecture-focused guidance and avoids premature optimization.
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 1. Capture domain context, use cases, and non-functional requirements. 2. Define service boundaries and API contracts. 3. Choose architecture patterns and integration mechanisms. 4. 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. ## Core Philosophy Design backend systems with clear boundaries, well-defi
- Use this skill when
- Do not use this skill when
- Instructions
- Purpose
- Core Philosophy
- Capabilities
- API Design & Patterns
- API Contract & Documentation
- Microservices Architecture
- Event-Driven Architecture
- Authentication & Authorization
- Security Patterns
- Resilience & Fault Tolerance
- Observability & Monitoring
What does the backend-architect skill do?
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill backend-architect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.