system-architecture

Formalize system-architecture design processes with ADRs and documentation deliverables.

3|1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/ProjAnvil/MindForge --skill system-architecture-projanvil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-architecture
Source: https://github.com/ProjAnvil/MindForge/tree/main/skills/zh-cn/system-architecture
Command: npx skills add https://github.com/ProjAnvil/MindForge --skill system-architecture-projanvil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides structured guidance for designing scalable, well-documented software architectures, helping teams choose patterns, evaluate technologies, and produce solid architecture documentation.

Core Features & Use Cases

  • Architecture pattern guidance for common styles (layered, microservices, event-driven) with trade-offs.
  • Technology evaluation framework to select stacks, tools, and platforms based on criteria like scalability, maintainability, and cost.
  • Architecture documentation support, including ADRs and architecture artifacts for governance, onboarding, and compliance.

Quick Start

Define an initial architecture scope, select a pattern to begin, and document the key ADRs to kick off the design.

Frequently Asked Questions about system-architecture

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

FAQPage Schema
How do I document architecture decisions for distributed systems?

Architecture documentation for distributed systems is formalized through Architecture Decision Records (ADRs) and structured artifacts, capturing pattern selection, technology evaluation criteria, and trade-offs to ensure governance and compliance.

What is the best way to choose architecture patterns for enterprise-scale projects?

Choosing architecture patterns for enterprise-scale projects requires evaluating common styles like layered, microservices, and event-driven architectures against specific trade-offs. This framework guides selection based on scalability, maintainability, and cost criteria.

How do I evaluate technology stacks for system design?

Evaluate technology stacks for system design by applying a structured framework that assesses tools and platforms against scalability, maintainability, and cost criteria. This produces solid architecture documentation for governance and onboarding.

Can I use this system design framework for microservices and event-driven architectures?

Yes, this system design framework applies to microservices and event-driven architectures, providing specific pattern guidance and trade-off analysis. It supports distributed systems where architecture decisions must be recorded and communicated.

What are the limitations of using predefined architecture patterns?

Predefined architecture patterns require careful trade-off analysis, as limitations arise when styles like layered or event-driven architectures mismatch specific enterprise-scale project constraints. Technology evaluation criteria must be applied to ensure scalability and maintainability.