skills.rest
newkayak12
newkayak12COMMUNITY
Explore all skills by this author →
GitHub

architecture-designer

Design high-level system architectures and generate Architecture Decision Records.

1|Updated Mar 11, 2026
Search Tags:#architecture#scalability#system design#design patterns#microservices#ADR
One-click install
npx skills add https://github.com/newkayak12/claude-skills --skill architecture-designer-newkayak12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/newkayak12/claude-skills/tree/main/plugins/newkayak12-skills/skills/architecture-designer
Command: npx skills add https://github.com/newkayak12/claude-skills --skill architecture-designer-newkayak12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design new high-level system architectures, review existing ones, and make critical architectural decisions, ensuring robust, scalable, and well-documented systems.

Core Features & Use Cases

  • Architecture Design: Create diagrams and document trade-offs for new systems.
  • ADR Authoring: Generate Architecture Decision Records to capture key choices.
  • Scalability Planning: Evaluate and plan for future growth.
  • Use Case: You need to design the architecture for a new e-commerce platform, including choosing between microservices and a monolith, and documenting the decision with an ADR.

Quick Start

Use the architecture-designer skill to design a scalable architecture for a new social media application.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I design and document system architecture for a new scalable platform?▼

Designing system architecture involves structuring component interactions, generating diagrams, and authoring Architecture Decision Records to capture critical choices and trade-offs for your new scalable platform.

What is an Architecture Decision Record and when do I need it for microservices design?▼

An Architecture Decision Record (ADR) is a document capturing key architectural choices. You need it when designing microservices to record trade-offs, structure component interactions, and facilitate system-level decision-making.

How do I evaluate trade-offs between a microservices and monolith system design?▼

To evaluate trade-offs between microservices and monoliths, you assess technology options, plan for scalability, and generate an Architecture Decision Record to document the evaluated choices for your system design.

Does this approach to system design work for planning scalability and reviewing existing architectures?▼

Yes, this approach supports scalability planning and reviewing existing architectures by evaluating technology trade-offs, structuring component interactions, and facilitating high-level architectural decision-making for future growth.

What are the limitations of high-level system architecture design compared to code-level patterns?▼

High-level system architecture design focuses strictly on system-level structuring, scalability planning, and ADRs, meaning it does not handle code-level design patterns or specific implementation details for your software engineering project.

Related Skills

Explore More Software Engineering Skills→
proyecto26proyecto26
42

requirements-scoping

Structure ambiguous system design prompts into functional requirements, non-functional constraints, and out-of-scope boundaries.

Official
Intermediate
mouchegmouradianmouchegmouradian
2

product-requirements-builder

Create PRDs and RFCs with standardized templates for software specifications.

Community
Advanced
codeApe-7codeApe-7
17

nestjs-expert

Generate NestJS backend boilerplate with TypeScript, class-validator, Swagger, and Jest.

Community
Advanced
ajianazajianaz
4

devops-deployer

Automate DevOps deployment and infrastructure provisioning across cloud environments.

Community
Advanced