system-architect

Design system architectures with Mermaid diagrams and ADR documentation.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill system-architect-vivekmano27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/Vivekmano27/agent-orchestrator/tree/main/plugins/project-orchestrator/skills/system-architect
Command: npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill system-architect-vivekmano27

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design production-grade system architecture with clear diagrams, rationale, and documented decisions to guide implementation.

Core Features & Use Cases

  • Architecture decision process: understand constraints, choose pattern, define module boundaries, design data flow, plan infrastructure, document ADRs.
  • Pattern Selection Guide: Monolith, Modular Monolith, Microservices, Serverless with a practical suitability chart and guidelines.
  • Use Case: When starting a new app, outline the architecture, draw Mermaid diagrams, and capture decisions in ADRs to align team.

Quick Start

Tell me your constraints and goals, and I will draft an initial architecture plan with module boundaries and a Mermaid diagram.

Frequently Asked Questions about system-architect

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

FAQPage Schema
What is the best way to document system architecture decisions for a new application?

Documenting system architecture decisions is best handled by generating Architecture Decision Records (ADRs) alongside diagrams. This approach captures constraints, module boundaries, and infrastructure topology rationale to guide implementation and align teams.

How do I choose between a monolith and microservices for my system design?

Choosing between a monolith and microservices requires evaluating constraints against a pattern suitability chart. You compare monolith, modular monolith, microservices, and serverless options to define module boundaries and infrastructure topology.

How can I generate Mermaid diagrams for microservices architecture?

You can generate Mermaid diagrams for microservices by defining module boundaries and mapping data flow. Supplying project constraints and goals allows the system to draft an initial architecture plan with clear visual diagrams.

When do I need an ADR template for production-grade infrastructure topology?

You need an ADR template for production-grade infrastructure topology when you must document architecture decisions across teams. It ensures clear rationale for pattern selection, data flow design, and module boundary definitions.

Does system design for modular monoliths require predefined module boundaries?

System design for modular monoliths requires predefined module boundaries to ensure separation of concerns. Establishing these boundaries early dictates data flow and infrastructure topology before finalizing architecture decisions.