backend-architect

Design backend architectures with pattern recommendations and Mermaid diagrams.

17|1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/codeworksID/everything-backend --skill backend-architect-codeworksid
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/codeworksID/everything-backend/tree/main/.agents/skills/backend-architect
Command: npx skills add https://github.com/codeworksID/everything-backend --skill backend-architect-codeworksid

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill assists in designing backend architectures, including system structure, tech stack selection, and component boundaries, providing iterative question-asking, pattern recommendations, and architecture documentation creation.

Core Features & Use Cases

  • Architecture Design: Guides through architecture design with recommendations for monolith, microservices, or serverless patterns.
  • Tech Stack Selection: Suggests appropriate tech stacks based on project requirements.
  • Documentation: Generates architecture documentation with Mermaid diagrams for clear visualization.
  • Use Case: When starting a new project or restructuring an existing one, this Skill helps in planning the backend architecture efficiently.

Quick Start

Use the backend-architect skill to design the architecture for your new project.

Frequently Asked Questions about backend-architect

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

FAQPage Schema
How do I design a backend architecture for a new project?โ–ผ

Backend architecture design involves iterative question-asking to gather requirements and recommend structural patterns like monolithic, microservices, or serverless. It includes tech stack selection and generates architecture documentation with Mermaid diagrams for clear visualization.

What is the best way to choose between monolithic and microservices architecture?โ–ผ

Choosing between monolithic and microservices architecture requires evaluating project requirements, scale, and component boundaries. By iteratively analyzing your specific use case, you can receive tailored recommendations on whether a monolithic, microservices, or serverless pattern fits best.

How do I generate Mermaid diagrams for backend architecture documentation?โ–ผ

Generating Mermaid diagrams for backend architecture documentation is achieved by defining system structure, component boundaries, and tech stack. The diagram visually maps the recommended architecture pattern, providing clear visualization for new projects or tech stack migrations.

When do I need to restructure my existing tech stack and backend architecture?โ–ผ

You need to restructure your backend architecture during major feature developments or tech stack migrations. This involves reviewing existing system structure and component boundaries, then iteratively planning an updated architecture design with appropriate pattern recommendations.

Can I use this approach for serverless pattern tech stack selection?โ–ผ

Yes, you can use this approach for serverless pattern tech stack selection. It assesses project requirements to recommend whether a serverless architecture fits your context, followed by suggesting an appropriate tech stack and generating supporting documentation.