architecture

Analyze requirements, evaluate trade-offs, and document architectural decisions with ADRs.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/dgkngk/super-kit --skill architecture-dgkngk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/dgkngk/super-kit/tree/main/skills/tech/architecture
Command: npx skills add https://github.com/dgkngk/super-kit --skill architecture-dgkngk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework for making sound architectural decisions, ensuring that requirements are met, trade-offs are evaluated, and decisions are well-documented.

Core Features & Use Cases

  • Requirements Analysis: Guides the process of gathering essential project context through targeted questions.
  • Trade-off Evaluation: Offers a systematic approach to analyzing the pros and cons of different architectural options.
  • ADR Documentation: Facilitates the creation of Architecture Decision Records to capture the rationale behind key choices.
  • Pattern Selection: Provides decision trees to help select appropriate architectural patterns based on project needs.
  • Use Case: When designing a new microservice, use this Skill to analyze scale, team expertise, and domain complexity to choose between a modular monolith or microservices, and document the decision using an ADR.

Quick Start

Use the architecture skill to help decide between a modular monolith and microservices for a new project.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I evaluate architectural trade-offs for system design?

To evaluate architectural trade-offs, systematically analyze the pros and cons of different system design options against your project requirements. This framework provides a structured approach to assess choices based on scale, team expertise, and domain complexity.

What is an Architecture Decision Record and how does it help pattern selection?

An Architecture Decision Record (ADR) is a structured document that captures the rationale behind key architectural choices. It supports pattern selection by linking chosen system design patterns to evaluated requirements and trade-offs.

What's the best way to choose between a modular monolith and microservices?

Choosing between a modular monolith and microservices requires analyzing project scale, team expertise, and domain complexity. This framework offers decision trees to guide your architectural pattern selection based on these specific factors.

How do I document architectural decisions for a new project?

Document architectural decisions by creating Architecture Decision Records (ADRs) that detail the chosen patterns and rationale. This framework guides requirements analysis and trade-off evaluation to support structured documentation of your choices.

Can I use this framework for architectural decision-making on small team projects?

Yes, you can use this framework for architectural decision-making on small team projects. It guides pattern selection by explicitly factoring team expertise and project scale into the requirements analysis and trade-off evaluation process.

When should I not use microservices architecture?

You should reconsider microservices architecture when project scale is low or team expertise is limited. This framework helps identify such constraints through trade-off evaluation, potentially guiding you toward a modular monolith instead.