architecture

Guide architectural decisions with ADR templates and pattern selection frameworks.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/achmf/KostaHub --skill architecture-achmf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/achmf/KostaHub/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/achmf/KostaHub --skill architecture-achmf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of making consistent, well-reasoned architectural decisions by providing a structured framework for requirements analysis, trade-off evaluation, and documentation.

Core Features & Use Cases

  • Decision Framework: Provides templates for Architecture Decision Records (ADRs) to ensure rationale is captured.
  • Pattern Selection: Offers decision trees to help choose between patterns like Monolith vs. Microservices or REST vs. GraphQL.
  • Context Discovery: Guides users through a hierarchy of questions regarding scale, team, and domain to classify project needs.
  • Use Case: Use this when you need to decide whether to adopt a repository pattern or when you need to document why a specific database technology was chosen for a new service.

Quick Start

Use the architecture skill to analyze the trade-offs for implementing a microservices architecture in a team of five developers.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document architectural decisions for a new software project?

To document architectural decisions, use Architecture Decision Records (ADRs) to capture the rationale, trade-offs, and pattern selection context for your system design. This framework provides templates ensuring your technical planning rationale is consistently recorded.

When do I need to choose between monolith and microservices architectures?

Choose between monolith and microservices architectures by evaluating project scale, team size, and domain needs. This framework guides you through a context discovery hierarchy of questions to classify project needs and offers decision trees for pattern selection.

What is the best way to analyze trade-offs for system design patterns?

The best way to analyze trade-offs for system design patterns is using a structured decision-making framework. It guides you through requirements gathering and context discovery to evaluate options like REST versus GraphQL based on your specific scale and domain.

Does this architectural decision framework work for both MVPs and enterprise-scale distributed systems?

Yes, this architectural decision framework supports technical planning for projects ranging from MVPs to enterprise-scale distributed systems. It adapts to your scale and team size by guiding you through a structured hierarchy of context discovery questions.

How do I create an Architecture Decision Record for a database technology choice?

To create an Architecture Decision Record for a database choice, use the provided ADR templates to document the requirements, trade-offs, and decision rationale. This ensures the reasoning behind adopting specific technologies is captured consistently.

What are the limitations of using a structured framework for architectural pattern selection?

The limitation of using a structured framework for architectural pattern selection is that it relies heavily on accurate context discovery regarding scale, team, and domain. Incorrect classification of project needs may lead to inappropriate trade-off evaluation and suboptimal decisions.