system-architect

Name: system-architect
Availability: InStock
Author: Marsolab

Architect production-grade software systems using architecture patterns and trade-off analysis.

Updated Jan 7, 2026

Search Tags:#architecture #scalability #observability #cloud #ADR #production-ready #system-design

Ready to run

npx skills add https://github.com/marsolab/skills --skill system-architect-marsolab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/marsolab/skills/tree/main/system-architect
Command: npx skills add https://github.com/marsolab/skills --skill system-architect-marsolab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineering teams design production-grade software architectures by applying proven patterns, trade-off analysis, and ADR-driven decision records to guide scalable, maintainable systems.

Core Features & Use Cases

Architecture pattern selection for monoliths, microservices, and hybrid approaches.
ADR documentation to capture context and rationale for major architectural decisions.
Observability-first design with metrics, traces, and logs planning, including SLIs/SLOs.
Clear data ownership, service boundaries, and deployment strategies for reliable systems.
Use cases include cloud-native platform design, technology evaluation, and large-scale migration guidance.

Quick Start

Example task: Request a complete system design for a cloud-based order service, including service boundaries, data ownership, ADR recommendations, and deployment considerations.

Frequently Asked Questions about system-architect

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

FAQPage Schema

How do I design a scalable, production-grade system architecture for cloud-native applications?▼

Design scalable, production-grade system architecture by applying proven patterns, trade-off analysis, and ADR-driven decision records to guide reliable, maintainable cloud-native systems.

What's the best way to document architecture decisions for microservices and distributed systems?▼

Document architecture decisions using ADR records to capture context and rationale, ensuring clear data ownership, service boundaries, and deployment strategies for reliable distributed systems.

How do I plan observability with metrics, traces, and logs for a production system?▼

Plan observability-first design by defining metrics, traces, logs, and SLIs/SLOs to ensure operational reliability and monitor system health across distributed architectures.

Can I use this to evaluate technology and guide large-scale cloud migrations?▼

Yes, you can evaluate technology and guide large-scale cloud migrations by applying architecture pattern selection, trade-off analysis, and deployment strategies for monoliths or microservices.

When should I choose microservices over a monolithic architecture pattern?▼

Choose microservices or monolithic architecture patterns based on trade-off analysis covering scalability, data ownership, service boundaries, and operational decision-making for your specific production context.