designing-systems

Design scalable software systems with C4 diagrams and trade-off analysis.

111|18|Updated Dec 17, 2025

Search Tags:#architecture #ADR #system-design #C4

Ready to run

npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill designing-systems

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: designing-systems
Source: https://github.com/dralgorhythm/claude-agentic-framework/tree/main/.claude/skills/architecture/desiging-systems
Command: npx skills add https://github.com/dralgorhythm/claude-agentic-framework --skill designing-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides system design with goals, diagrams, data models, and trade-offs.

Core Features & Use Cases

Diagrams & Architecture: C4 diagrams and ADRs.
Trade-offs: Document decisions and alternatives.
Use Case: Outline a system design for an e-commerce catalog.

Quick Start

Draft a C4 context diagram for a new service and capture ADRs.

Frequently Asked Questions about designing-systems

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

FAQPage Schema

How do I create a C4 diagram for system architecture?▼

C4 diagrams visualize software architecture at four levels: context, container, component, and code. Use them to document system boundaries, dependencies, and technology choices. This Skill guides you through drafting each level with clear relationships and trade-offs.

What should I include in an Architecture Decision Record?▼

An ADR documents a major architectural choice, its context, alternatives considered, and consequences. ADRs capture the reasoning behind decisions so teams understand why a system was designed a certain way and what trade-offs were accepted.

How do I decompose a system into manageable components?▼

System decomposition breaks a large system into smaller, independently designable parts based on concerns, data flow, and scaling needs. This Skill covers decomposition techniques alongside C4 diagrams to ensure each component has clear responsibilities and interfaces.

When should I use system design documentation for new features?▼

Document system design for major features, architecture changes, or new services before implementation. Design documentation—including data models, API definitions, and risk assessment—prevents costly rework and aligns teams on requirements and trade-offs.

Can system design documentation help with scaling decisions?▼

Yes. System design addresses scalability by analyzing trade-offs between consistency, availability, and performance; documenting data model choices; and planning decomposition. ADRs and C4 diagrams record scaling decisions and their architectural implications.

What trade-offs should I document when designing systems?▼

Document trade-offs between technology choices, architectural patterns, data consistency models, and deployment strategies. This Skill helps you capture alternatives and their consequences so decisions remain transparent and revisable as requirements evolve.