skills.rest
jieni777
jieni777COMMUNITY
Explore all skills by this author →
GitHub

backend-architect

Designs scalable APIs and distributed services for microservice architectures.

1|Updated Jan 30, 2026
Search Tags:#architecture#backend#microservices#resilience#observability#api-design
One-click install
npx skills add https://github.com/jieni777/opencode-config-backup --skill backend-architect-jieni777
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/jieni777/opencode-config-backup/tree/main/skills/backend-architect
Command: npx skills add https://github.com/jieni777/opencode-config-backup --skill backend-architect-jieni777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend teams often lack a cohesive architectural playbook to design scalable, resilient APIs and distributed services.

Core Features & Use Cases

  • API design patterns, service boundary definition, and resilience strategies for modern backends.
  • Guidance on observability, deployment considerations, and inter-service communication.
  • Use case: plan a new microservice with defined boundaries, contracts, and rollout plan.

Quick Start

Describe domain boundaries and draft the initial API contracts for a new backend service.

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 and API contracts for a new microservice?▼

To design scalable backend APIs, apply domain-driven boundaries, contract-first API design, and resilience patterns like retries and circuit breakers to ensure robust distributed service communication.

What resilience patterns should I use for distributed services?▼

For resilient distributed services, implement patterns such as retries, circuit breakers, and service mesh to handle inter-service communication failures and maintain system availability.

Can this help plan observability across microservices?▼

Yes, this helps plan observability across microservices by providing architectural guidance on monitoring strategies and deployment considerations tailored for distributed backend systems.

What is the best way to architect a scalable backend system?▼

The best way to architect a scalable backend system is using a cohesive playbook that addresses domain-driven boundaries, API design patterns, and deployment considerations for distributed services.

When should I use a service mesh in my backend architecture?▼

Use a service mesh in your backend architecture when managing complex inter-service communication across microservices, requiring advanced resilience patterns and observability without modifying application code.

Related Skills

Explore More Software Engineering Skills→
Fr-e-dFr-e-d
157

architecture-extract

Analyze project directory structures to generate architectural summaries.

Community
Basic
mnthemnthe

plan

Convert vague automation requirements into structured Markdown implementation plans.

Community
Basic
M-Abdullah07M-Abdullah07
1

backend-architect

Architect scalable backend systems with service boundaries and resilience patterns.

Community
Advanced
mahg-esmahg-es
3

microservice

Define microservice boundaries with bounded contexts, data ownership, and API contracts.

Official
Advanced