system-architect

Design system architectures, generate C4 model diagrams, and create Architecture Decision Records.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imudak/claudemd-gen --skill system-architect-imudak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/imudak/claudemd-gen/tree/main/.claude/skills/system-architect
Command: npx skills add https://github.com/imudak/claudemd-gen --skill system-architect-imudak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill assists in designing robust system architectures, creating C4 model diagrams, documenting decisions with ADRs, and analyzing technical tradeoffs to ensure optimal system design.

Core Features & Use Cases

  • Architecture Design: Guides users through designing system structures, component divisions, and responsibility assignments.
  • Diagramming: Generates C4 model diagrams (Context, Container, Component) to visualize architecture.
  • Decision Documentation: Facilitates the creation of Architecture Decision Records (ADRs) to document key choices.
  • Tradeoff Analysis: Helps in evaluating different architectural options and their implications.
  • Use Case: A startup needs to design the architecture for a new SaaS product. This Skill can guide them through selecting appropriate patterns, documenting decisions, and visualizing the system structure.

Quick Start

Use the system-architect skill to design the architecture for a new e-commerce platform, including C4 diagrams and ADRs.

Frequently Asked Questions about system-architect

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

FAQPage Schema
How do I create C4 model diagrams for system architecture design?

C4 model diagrams for system architecture are generated by visualizing Context, Container, and Component levels. This guides you through creating these diagrams to map system structures, component divisions, and responsibility assignments.

What is an Architecture Decision Record and when should I document one?

An Architecture Decision Record (ADR) is a document capturing key technical choices. You should create an ADR when selecting architectural patterns or technologies, ensuring tradeoff evaluations and system design decisions are formally documented.

How do I conduct a tradeoff analysis for scalable system patterns?

Tradeoff analysis for scalable system patterns is conducted by evaluating different architectural options and their implications. This helps compare technology selections to ensure systems remain scalable, secure, and maintainable.

Can I use this for SaaS architecture design from scratch?

Yes, this supports SaaS architecture design from scratch. It guides comprehensive system architecture design, from selecting appropriate patterns and evaluating tradeoffs to generating C4 diagrams and documenting decisions with ADRs.