Architecture Designer

Name: Architecture Designer
Availability: InStock
Author: franroa

Design scalable software architectures and document decisions with ADRs.

Updated Oct 22, 2025

Search Tags:#architecture #scalability #system design #patterns #trade-offs #ADRs

Ready to run

npx skills add https://github.com/franroa/chezmoi --skill architecture-designer-franroa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Architecture Designer
Source: https://github.com/franroa/chezmoi/tree/main/private_dot_config/opencode/skills/architecture-designer
Command: npx skills add https://github.com/franroa/chezmoi --skill architecture-designer-franroa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides system design decisions, documents architectural trade-offs, and creates Architecture Decision Records (ADRs).

Core Features & Use Cases

ADR documentation: Record decisions, rationale, and alternatives.
Design pattern guidance: Recommend patterns for scalability and maintainability.
Non-functional considerations: Performance, security, reliability.

Quick Start

Document an ADR for a new service and capture the trade-offs.

Frequently Asked Questions about Architecture Designer

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

FAQPage Schema

How do I document architectural decisions and trade-offs in my system design?▼

Architecture Decision Records (ADRs) document your design choices, rationale, and alternatives considered. ADRs capture trade-offs explicitly, making decisions transparent to stakeholders and future teams, and serve as a reference when evaluating scalability or performance constraints.

What design patterns should I use for building scalable distributed systems?▼

Design patterns guide scalability and maintainability in distributed architectures. This Skill recommends patterns suited to your functional and non-functional requirements—performance, security, reliability—and evaluates their trade-offs across cloud, microservice, and distributed environments.

How do I evaluate architectural trade-offs when choosing between technologies?▼

Evaluating trade-offs means weighing non-functional requirements like performance, security, and operational complexity against each option. ADRs and pattern guidance help document these decisions, plan for failure modes, and ensure stakeholder alignment before committing to a technology choice.

Can I use this for reviewing and improving existing architectures?▼

Yes. Architecture reviews apply design pattern guidance and trade-off analysis to existing systems. This Skill helps identify scalability gaps, evaluate pattern fit, and document improvement decisions as ADRs to guide incremental architectural evolution.

What non-functional requirements should I consider when designing for scalability?▼

Non-functional requirements—performance, security, reliability, and operational complexity—shape scalability decisions. This Skill ensures these requirements are documented in ADRs alongside functional needs, with explicit trade-offs and failure-mode planning for cloud and microservice architectures.