system-architect

Design scalable, secure architectures with C4 diagrams, ADRs, and trade-off analysis.

Updated Jan 10, 2026

Search Tags:#design #architecture #security #cloud #ADR #trade-offs #C4-model

Ready to run

npx skills add https://github.com/Eigo-Mt-Fuji/portfolio-2026 --skill system-architect-eigo-mt-fuji

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/Eigo-Mt-Fuji/portfolio-2026/tree/main/.claude/skills/system-architect
Command: npx skills add https://github.com/Eigo-Mt-Fuji/portfolio-2026 --skill system-architect-eigo-mt-fuji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product and engineering teams design scalable, secure, and maintainable system architectures by providing structured guidance on architecture patterns, decision records, and visual modeling.

Core Features & Use Cases

C4 model guidance: create context, container, and component diagrams to communicate architecture clearly.
ADR support: document important architectural decisions with rationale and tradeoffs.
Tradeoff analysis: evaluate quality attributes and technology options to balance performance, scalability, and cost.
Technology and pattern selection: assist in choosing appropriate patterns (Monolith, Microservices, Event-driven, Serverless) and technology stacks for a given problem.
Documentation scaffolding: generate structured design documents and diagrams to align stakeholders.

Quick Start

Provide a high-level brief of the system you'd like to build, including expected scale and key non-functional concerns, and ask the AI to produce an architecture plan.

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 system architecture for microservices?▼

Scalable system architecture for microservices starts with defining components using C4 diagrams, then documenting decisions via ADRs that address trade-offs between performance, scalability, and cost. This Skill guides pattern selection, technology choices, and visual modeling to communicate designs clearly to stakeholders.

What's the difference between monolith, microservices, and serverless architectures?▼

Architecture patterns—monolith, microservices, event-driven, and serverless—each solve different scalability and deployment challenges. This Skill helps evaluate trade-offs across these patterns based on your system's scale, team structure, and non-functional requirements to select the right fit.

How do I document architectural decisions and their trade-offs?▼

Architectural Decision Records (ADRs) document important design choices with rationale and trade-offs, ensuring team alignment. This Skill provides ADR scaffolding templates and guidance to structure decisions around quality attributes, technology options, and long-term maintainability.

Can I use C4 diagrams to communicate my system design?▼

C4 model diagrams—context, container, and component layers—communicate architecture across technical and non-technical audiences. This Skill guides creating each diagram level to clarify system boundaries, dependencies, and interactions without overwhelming detail.

How do I choose technologies and patterns for a complex system?▼

Technology and pattern selection requires evaluating trade-offs across performance, scalability, cost, and security for your system's scale and constraints. This Skill supports tradeoff analysis and technology assessment to align choices with non-functional requirements and business goals.

What security considerations should I include in architecture design?▼

Security architecture integrates threat models, access control, and data protection into system design from the start. This Skill addresses security as a core non-functional requirement within architecture patterns, ADRs, and technology selection processes.