architecture-designer

Creates architectural system designs and generates BSDs from high-level specifications.

17|3|Updated Mar 18, 2026

Search Tags:#architecture #scalability #microservices #infrastructure #system-design #decision-record

Ready to run

npx skills add https://github.com/codeApe-7/ai-agent-workflowGroup --skill architecture-designer-codeape-7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/codeApe-7/ai-agent-workflowGroup/tree/main/skills/backend/architecture-designer
Command: npx skills add https://github.com/codeApe-7/ai-agent-workflowGroup --skill architecture-designer-codeape-7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill assists senior architects and system designers in creating comprehensive high-level system architectures, reviewing design options, and documenting architectural decisions effectively.

Core Features & Use Cases

System Design Planning: Develop detailed architecture diagrams, choose suitable patterns, and evaluate technology options.
Decision Documentation: Generate ADRs to record key trade-offs and rationales.
Review & Validation: Assist in architecture reviews, risk assessment, and scalability planning.
Use Case: A cloud infrastructure team can utilize this Skill to design a robust microservices architecture with scalability considerations and generate ADRs to justify technology choices.

Quick Start

Describe a new payment processing system's architecture to get a tailored high-level design and decision summaries.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema

How do I design a scalable microservices architecture for a new system?▼

Designing scalable microservices architecture requires evaluating infrastructure options, selecting suitable system design patterns, and documenting technology trade-offs. This process yields a high-level design that supports robust scalability and meets your specific technical requirements for infrastructure planning.

What is an architectural decision record and when do I need one?▼

An architectural decision record (ADR) is a document capturing key trade-offs and rationales for technology choices. You need ADRs during system design to justify infrastructure decisions, record pattern selection logic, and provide clear technical context for future architecture reviews and scalability planning.

Can I use this for evaluating technology options during infrastructure planning?▼

Yes, you can use this for evaluating technology options during infrastructure planning. It assists senior architects in technology evaluation, pattern selection, and risk assessment, providing expert insights to validate scalable system designs and justify final technical decisions for your team.

What's the best way to document trade-offs for a high-level system design?▼

The best way to document trade-offs for high-level system design is by generating architectural decision records (ADRs). ADRs capture the rationale behind pattern selection, technology evaluation, and scalability considerations, ensuring your infrastructure planning decisions are well-justified and easily reviewable.

How do I assess scalability risks when reviewing a system architecture?▼

To assess scalability risks when reviewing system architecture, evaluate chosen design patterns, technology options, and infrastructure limitations. This architecture review process identifies potential bottlenecks and validates that the high-level design meets required scalability considerations for robust system performance.