architecture-designer

Plan scalable software architectures and document decisions with ADRs and diagrams.

Updated May 14, 2026

Search Tags:#architecture #scalability #microservices #adr #system-design #architecture-decisions

Ready to run

npx skills add https://github.com/nkseth/copilot-dev-skills --skill architecture-designer-nkseth

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineering teams need a structured, repeatable process to design scalable systems and document architectural decisions, ensuring alignment and traceability across stakeholders.

Core Features & Use Cases

ADR creation and architecture decision documentation
System design guidance across patterns (monolith, microservices), scalability planning, and non-functional requirements
Generate architecture diagrams and reference guides for reviews and stakeholder alignment
Use cases include evaluating trade-offs for new services, planning component interactions, and documenting decisions for long-term maintainability.

Quick Start

Provide a system design brief for a new service and generate an ADR and architecture diagram.

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 for a new microservice?▼

System design for microservices involves evaluating patterns, planning component interactions, and enforcing non-functional requirements. This Skill guides architecture planning by evaluating trade-offs and producing structured diagrams alongside decision records.

What is the best way to evaluate trade-offs between a monolith and microservices architecture?▼

Evaluating monolith versus microservices trade-offs requires assessing scalability needs and operational considerations. This Skill evaluates architectural patterns to document clear trade-offs and generate reference guides for stakeholder alignment.

How do I plan for software scalability and assess infrastructure risks?▼

Plan scalability and assess infrastructure risks by enforcing non-functional requirements and operational considerations. This Skill produces structured diagrams and decision records that map component interactions to mitigate long-term maintainability risks.

Can I generate architecture diagrams and reference guides from a system design brief?▼

Yes, you generate architecture diagrams and reference guides directly from a system design brief. Providing a service brief prompts this Skill to output a structured visual diagram and an ADR to support architecture reviews and stakeholder alignment.

When should I not use microservices for system design?▼

Reconsider microservices when operational considerations and non-functional requirements favor simpler patterns. This Skill enforces risk assessment and pattern evaluation to determine if a monolith architecture better suits your maintainability and scalability needs.