system-design-decision-engine

Detects design patterns and generates a contract-like architecture specification.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/arbgjr/smart_alarm --skill system-design-decision-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-design-decision-engine
Source: https://github.com/arbgjr/smart_alarm/tree/main/.claude/skills/system-design-decision-engine
Command: npx skills add https://github.com/arbgjr/smart_alarm --skill system-design-decision-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill guides users through rigorous architectural decision-making by detecting design patterns, eliciting mandatory questions, enforcing explicit trade-offs, and consolidating a coherent proposal for interviews or production reviews.

Core Features & Use Cases

  • Pattern activation: identifies relevant design patterns from problem statements and surfaces mandatory questions.
  • Structured decisions: ties each activated pattern to explicit decisions, trade-offs, risks, and alternatives.
  • Quick-start workflow: run pattern detection, generate required questions, and consolidate an architecture following a contract.

Quick Start

Provide a problem statement and run the workflow to detect patterns, generate mandatory questions, and finalize the architecture according to the contract.

Frequently Asked Questions about system-design-decision-engine

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

FAQPage Schema
How do I make rigorous system design decisions with explicit trade-offs?▼

You prepare for system design interviews by running pattern detection on a problem statement, answering generated mandatory questions, and consolidating a contract-like architecture specification with documented trade-offs and risks.

How do I identify relevant design patterns from a problem statement?▼

Identifying relevant design patterns is achieved by running the quick-start workflow, which analyzes your problem statement, activates applicable patterns, and surfaces mandatory questions to guide your architectural choices.

Can I use this for production architecture planning and design reviews?▼

Yes, you can use this for production planning and design reviews, as it enforces explicit decisions, records risks and alternatives, and outputs a contract-like architecture specification for delivery.

What is the best way to document architecture risks and alternatives?▼

The best way to document architecture risks and alternatives is to tie each activated design pattern to explicit decisions, trade-offs, and alternatives, consolidating them into a formal proposal.

Does this require any specific frameworks or dependencies?▼

No, this skill requires no external dependencies, operating entirely through provided scripts to guide pattern activation, mandatory questions, and final architecture consolidation.

When should I not use a pattern-based decision engine for system design?▼

You should avoid a pattern-based decision engine when your problem requires ad-hoc architectural choices outside established patterns, or when you cannot provide a coherent problem statement to trigger pattern detection.