architecture-designer

Name: architecture-designer
Availability: InStock
Author: Alteriom

Design system architectures using C4 modeling, ADRs, and NFR analysis.

Updated Apr 14, 2026

Search Tags:#architecture #adr #system-design #pattern-analysis #tradeoffs #nfr #c4-model

Ready to run

npx skills add https://github.com/Alteriom/ai-dev-skills --skill architecture-designer-alteriom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/Alteriom/ai-dev-skills/tree/main/skills/architecture-designer
Command: npx skills add https://github.com/Alteriom/ai-dev-skills --skill architecture-designer-alteriom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing large-scale software architectures is error-prone without a structured approach to modeling, decision records, and non-functional requirements.

Core Features & Use Cases

C4 modeling guidance (Context, Container, Component) to visualize architectures and communicate with stakeholders.
Architecture Decision Records (ADRs) to capture rationale, alternatives, and trade-offs.
Non-functional requirements (NFRs) analysis to guide security, reliability, performance, and maintainability.

Quick Start

Create a system design outline by generating C4 diagrams, drafting ADRs for major decisions, and listing the required NFRs.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema

How do I use C4 modeling to design a system architecture?▼

System architecture design uses C4 modeling to visualize Context, Container, and Component levels. This approach breaks down complex software into structured diagrams to communicate designs effectively with stakeholders and scope problems accurately.

What is the best way to document architecture trade-offs and rationale?▼

Architecture Decision Records (ADRs) document design trade-offs by capturing rationale and alternatives for major decisions. Drafting ADRs ensures system architecture choices are formally recorded for stakeholder communication and future reference.

How do I analyze non-functional requirements for a large-scale software architecture?▼

Non-functional requirements (NFRs) analysis evaluates software architecture for security, reliability, performance, and maintainability. Listing required NFRs guides pattern selection and ensures the design satisfies formal constraints for robust systems.

When do I need formal NFR analysis and ADRs during system design?▼

You need NFR analysis and ADRs when designing large-scale software architectures to prevent errors. Structured C4 modeling, decision records, and non-functional requirements analysis are required for robust stakeholder communication and pattern selection.

Does pattern analysis help with selecting system design components?▼

Pattern analysis guides system architecture component selection by evaluating trade-offs against non-functional requirements. Applying proven patterns ensures the resulting software design satisfies requirements for reliability, security, and performance.