skills.rest
flc1125
flc1125COMMUNITY
Explore all skills by this author →
WebsiteGitHub

engineering-backend-architect

Design and review backend system architecture, including service boundaries, data models, and communication patterns.

32|6|Updated Jan 23, 2026
Search Tags:#design#architecture#database#scalability#api#backend#microservices
One-click install
npx skills add https://github.com/flc1125/skills --skill engineering-backend-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-backend-architect
Source: https://github.com/flc1125/skills/tree/main/skills/engineering-backend-architect
Command: npx skills add https://github.com/flc1125/skills --skill engineering-backend-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill assists in designing robust backend system architectures, reviewing existing designs, and defining critical components like services, APIs, and data models.

Core Features & Use Cases

  • Architecture Design: Create new backend architectures for systems, features, or refactors.
  • Design Review: Analyze and provide feedback on existing backend designs.
  • Component Definition: Define service boundaries, data models, communication patterns, security, reliability, and scaling strategies.
  • Use Case: You need to design a scalable and secure backend for a new e-commerce platform, including microservices, database schemas, and API definitions.

Quick Start

Use the engineering-backend-architect skill to design a backend architecture for a new social media application.

Frequently Asked Questions about engineering-backend-architect

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

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

Defining service boundaries involves mapping microservices, database schemas, and API definitions to domain requirements. This process ensures clear separation of concerns, explicit security measures, and reliable communication patterns across the backend system.

What is the best way to review an existing backend architecture design?▼

Reviewing backend architecture involves analyzing existing designs against requirements, security, and reliability standards. It provides feedback on service boundaries, data layers, and communication patterns while identifying necessary tradeoffs to maintain system simplicity and performance.

Can I use this approach to define microservices and database schemas for an e-commerce platform?▼

Yes, you can define microservices and database schemas for e-commerce platforms. It creates backend architectures covering data layers, API definitions, and scaling strategies tailored to handle specific platform requirements and reliability constraints.

When should I avoid over-engineering backend architecture and system design?▼

You should avoid over-engineering backend architecture by adopting the smallest viable architecture. This methodology explicitly states assumptions and tradeoffs, prioritizing security and reliability without adding unnecessary complexity to the system delivery plan.

Related Skills

Explore More Software Engineering Skills→
CraigtutCraigtut
1

doc-explorer

Load foundational Animus docs and explore topic-specific project documentation.

Community
Intermediate
jpoutrinjpoutrin
14

technical-specification

Generates comprehensive technical specification documents for implementation-ready projects.

Community
Basic
travisjneumantravisjneuman
88

generic-feature-developer

Guide feature development with architecture patterns and decision frameworks.

Community
Intermediate
davekim917davekim917
1

software-engineering

Automate assessment of software engineering practices with structured patterns and checklists for web apps, APIs, and cloud infrastructure.

Community
Advanced