Systems Architecture

Structure architectural decisions for monoliths, modular monoliths, or microservices.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/melissa-pereira-deel/creative-technologist-agent --skill systems-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Systems Architecture
Source: https://github.com/melissa-pereira-deel/creative-technologist-agent/tree/main/skills/systems-architecture
Command: npx skills add https://github.com/melissa-pereira-deel/creative-technologist-agent --skill systems-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are among the most expensive to reverse and can paralyze teams when scale or complexity grows. This Skill helps you frame tradeoffs, select appropriate boundaries, and guide reliable, evolvable system design.

Core Features & Use Cases

  • Clarifies monolith vs modular monolith vs microservices decisions for teams of varying size
  • Guides API design, data boundaries, and deployment strategies to improve maintainability
  • Use Case: when designing a new product, outline service boundaries and choose an evolution path that minimizes risk and rewrites

Quick Start

Create a high-level architectural plan for a notional product, defining components, boundaries, and interaction patterns to support reliable growth.

Frequently Asked Questions about Systems Architecture

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

FAQPage Schema
How do I decide between a monolith, modular monolith, or microservices architecture?

Choosing between a monolith, modular monolith, or microservices requires balancing complexity, risk, and team capabilities. This Skill helps frame tradeoffs and select appropriate service boundaries to improve maintainability.

What is the best way to define service boundaries and API design for a new product?

Defining service boundaries and API design for a new product involves outlining components and interaction patterns. This Skill guides data boundaries and deployment strategies to minimize risk and rewrites during reliable growth.

How do I structure architectural decisions to ensure system reliability and scalability?

Structuring architectural decisions to ensure reliability and scalability requires codifying choices about observability and resilience. This Skill provides criteria and guardrails to guide evolvable system design.

When should I not use microservices for my application architecture?

You should avoid microservices when teams lack the capabilities to manage their complexity and risk. This Skill clarifies architectural decisions for teams of varying sizes, ensuring appropriate boundaries without unnecessary rewrites.

Can I use this to plan deployment strategies and observability for scalable systems?

Yes, you can use this to plan deployment strategies and observability for scalable systems. This Skill structures architectural decisions regarding resilience and reliable growth to improve overall maintainability.

Why does architectural complexity paralyze teams and how can I prevent it?

Architectural complexity paralyzes teams because decisions are expensive to reverse as scale grows. Prevent this by framing tradeoffs and selecting appropriate boundaries to guide reliable, evolvable system design.