architecture

Analyze software design choices with explicit trade-off reasoning.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill architecture-luyzkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/architecture
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill architecture-luyzkk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you make sound architecture decisions (e.g., SOLID principles, CQRS/event sourcing, monolith vs microservices, REST vs GraphQL, ADR-level design patterns) by turning vague choices into explicit trade-offs tailored to your context instead of dogma.

Core Features & Use Cases

  • Architecture consultation with trade-off analysis: Evaluates options by complexity, operational impact, scalability needs, and team fit.
  • Pattern and principle guidance for decision-making: Covers common decision areas including dependency injection, IoC, DI vs DIP, Law of Demeter, Tell-Don’t-Ask, and composition over inheritance.
  • Profile- and stack-aware recommendations: Adapts guidance using architecture profile context and stack-specific security/knowledge prefaces when available.

Quick Start

Ask the AI for an architecture recommendation and trade-offs for your specific decision: "Given my project goals, team size, and constraints, compare monolith vs microservices and recommend the safest path forward with a suggested ADR outline."

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I decide between monolith vs microservices for my project?

Architecture trade-off analysis compares monolith versus microservices by evaluating complexity, operational impact, scalability needs, and team fit to recommend the safest path forward under your specific constraints.

What is the best way to structure an architecture decision record?

An architecture decision record (ADR) should explicitly document trade-offs tailored to your context. Generate ADR outlines by providing your project goals, team size, and constraints to capture pragmatic, context-aware design choices.

When do I need CQRS and event sourcing in system design?

CQRS and event sourcing are needed in system design when evaluating architecture patterns for complex domains. Trade-off analysis assesses their scalability benefits against operational complexity and team fit before adoption.

How do I choose between REST and GraphQL for my API?

Choosing between REST and GraphQL requires explicit trade-off reasoning based on your architecture profile. Compare options by operational impact, scalability needs, and team fit to select the right API boundary.

How do I apply SOLID principles like dependency injection without over-engineering?

Apply SOLID principles like dependency injection by evaluating trade-offs between composition over inheritance, DI vs DIP, and the Law of Demeter. Pragmatic guidance ensures pattern selection fits your team and operational complexity.