agency-backend-architect

Designs scalable backend architectures, database schemas, and API contracts with security and observability patterns.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-backend-architect-immamdouhaboammar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-backend-architect
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/engineering-backend-architect
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-backend-architect-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing backend systems that scale reliably while staying secure is hard, and teams often ship architectures with missing error handling, weak API contracts, or unsafe data migrations. This Skill provides a senior backend architect persona that produces structured system designs, database schemas, and API specifications following proven reliability and security patterns. ## Core Features & Use Cases - System Architecture Design: Chooses between monolith, modular monolith, microservices, or serverless patterns and produces a full architecture specification with service decomposition, communication patterns, and reliability strategies. - Database & API Engineering: Generates indexed SQL schemas, zero-downtime migration plans using expand-and-contract patterns, and OpenAPI/AsyncAPI contracts with versioning, pagination, and idempotency semantics. - Reliability & Observability by Default: Builds in circuit breakers, retry policies, dead-letter queues, structured logging, distributed tracing, and SLO definitions for every design. - Use Case: Ask it to design the backend for an e-commerce platform and receive a service decomposition, PostgreSQL schema with proper indexing, and an OpenAPI contract covering error responses and rate limiting. ## Quick Start Ask the agent to design a scalable backend architecture with database schema and API contract for your application idea.

Frequently Asked Questions about agency-backend-architect

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

FAQPage Schema
How do I design a scalable backend architecture?▼

Start by choosing an architecture pattern based on team size, domain boundaries, and scaling needs: monolith, modular monolith, microservices, or serverless. Then define service decomposition, communication patterns, database schemas, and API contracts with explicit reliability and observability requirements.

When should I use microservices vs a monolith?▼

Use microservices only when independent deployment, team ownership, or independent scaling justifies the operational complexity. For most teams, a modular monolith with clear domain boundaries is simpler to operate and can evolve toward services later.

How do I perform zero-downtime database migrations?▼

Use the expand-and-contract pattern: add new schema elements alongside old ones, backfill data with dual writes, validate with reconciliation checks, then remove the old schema after cutover. Always plan rollback strategies before changing critical data models.

What should an API contract specification include?▼

An API contract should use OpenAPI, AsyncAPI, or protobuf and define versioning, standardized error responses, pagination, filtering, idempotency keys, correlation IDs, and timeout, retry, rate limit, and authentication semantics for every endpoint.

How do I make backend systems observable in production?▼

Emit structured logs with request IDs and stable error codes, define SLIs and SLOs for latency and error rates, and use distributed tracing across services, queues, and databases. Build alerts around user-impacting symptoms rather than only infrastructure metrics.