architecture-designer

Translate requirements into architecture patterns and ADR-style decision documentation.

18|2|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/yuanyuekejiJN/AivoClaw --skill architecture-designer-yuanyuekejijn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/yuanyuekejiJN/AivoClaw/tree/main/extraSkills/architecture-designer-0.1.0
Command: npx skills add https://github.com/yuanyuekejiJN/AivoClaw --skill architecture-designer-yuanyuekejijn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you make high-quality system architecture decisions without losing sight of scalability, maintainability, and non-functional requirements.

Core Features & Use Cases

  • System architecture design: Produce a structured architecture proposal with clear components and interactions.
  • Architectural review & pattern selection: Evaluate requirements against architecture patterns (e.g., monolith vs microservices, event-driven, CQRS).
  • ADR-ready decision documentation: Turn key choices into ADR-style artifacts, including context, decisions, consequences, and alternatives.
  • Scalability and NFR planning: Explicitly capture performance, availability, security, reliability, and cost considerations.

Quick Start

Use the architecture-designer skill to design an architecture for a new microservices platform by asking it to include an requirements summary, a high-level architecture diagram description, ADR-style key decisions with trade-offs, and a risks-and-mitigation section.

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 architecture and document trade-offs for distributed systems?

Design scalable architecture by translating requirements into system patterns and ADR-style documentation. This process yields structured outputs that capture context, decisions, alternatives, and failure-mode planning for distributed systems.

What is the best way to document architectural decisions and non-functional requirements?

Document architectural decisions using ADR-style artifacts that explicitly capture non-functional requirements. This format records context, decisions, consequences, and alternatives to ensure scalability, security, and reliability considerations are evaluated.

How do I evaluate microservices vs monolith architecture patterns for my system design?

Evaluate microservices vs monolith architecture patterns by reviewing requirements against operational complexity and scalability. This architectural review produces structured recommendations and risk mitigation plans based on your specific non-functional requirements.

Can I use this to plan for system availability, performance, and operational complexity?

Yes, you can plan for system availability, performance, and operational complexity. The architecture design process explicitly captures these non-functional requirements and translates them into structured failure-mode planning and risk mitigation strategies.

When do I need to generate ADR-style documentation for architecture review?

Generate ADR-style documentation when making high-quality system architecture decisions for new system design or trade-off evaluation. It ensures explicit consideration of documented alternatives and consequences for scalability and maintainability.