architecture-designer

Create ADR-style architecture decision guidance for system design reviews.

7|4|Updated Dec 12, 2023
One-click install
npx skills add https://github.com/BridgingIT-GmbH/bITdevKit --skill architecture-designer-bridgingit-gmbh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/BridgingIT-GmbH/bITdevKit/tree/main/.agents/skills/architecture-designer
Command: npx skills add https://github.com/BridgingIT-GmbH/bITdevKit --skill architecture-designer-bridgingit-gmbh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architecture decisions are often slow and risky; this skill helps synthesize requirements into ADR-ready design guidance.

Core Features & Use Cases

  • ADR templates for architecture decisions
  • Architecture review guidance and design pattern recommendations
  • System design checklists and references for ADR documentation

Quick Start

Draft an ADR for a new service boundary based on the provided requirements.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I write ADR documentation for microservices architecture?

ADR documentation for microservices is generated by synthesizing system requirements into structured architecture decision records, covering design patterns, service boundaries, and non-functional considerations to ensure scalable trade-offs are documented.

What is the best way to prepare for a system design architecture review?

Preparing for an architecture review involves applying system design checklists and pattern recommendations to evaluate cloud-native or monolithic systems, ensuring non-functional requirements and scalable design trade-offs are thoroughly assessed.

Can I use this to select design patterns for cloud-native architectures?

Yes, design pattern selection for cloud-native architectures is supported by providing tailored recommendations and ADR-style guidance that evaluates non-functional considerations and scalability requirements across different architectural styles.

How do I document architecture decisions for non-functional requirements?

Architecture decisions for non-functional requirements are documented using ADR templates that capture system design trade-offs, ensuring scalability, performance, and reliability constraints are explicitly addressed in the final guidance.

When do I need ADR guidance for monolithic system design?

ADR guidance is needed for monolithic system design when defining service boundaries, selecting structural design patterns, or evaluating scalability trade-offs to ensure architecture decisions are explicitly captured and reviewed.

What are the limitations of using ADR templates for system design?

ADR templates guide the synthesis of architecture decisions and trade-offs but do not automatically resolve non-functional requirements; engineers must still manually input system constraints and evaluate pattern suitability.