skills.rest
derHaken
derHakenCOMMUNITY
Explore all skills by this author →
GitHub

architecture-design

Guide scalable system architecture design with constraint gathering and trade-off analysis.

437|13|Updated Feb 25, 2026
Search Tags:#design#architecture#scalability#trade-offs#system-architecture#api-design#data-models
One-click install
npx skills add https://github.com/derHaken/SuperAntigravity --skill architecture-design-derhaken
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-design
Source: https://github.com/derHaken/SuperAntigravity/tree/main/skills/architecture-design
Command: npx skills add https://github.com/derHaken/SuperAntigravity --skill architecture-design-derhaken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing scalable software systems and architectures requires evaluating constraints, trade-offs, and long-term impact before coding. This Skill provides a structured approach to gather requirements, generate viable options, compare trade-offs, and document decisions.

Core Features & Use Cases

  • Structured constraint gathering: captures scale, latency, consistency, cost, and team constraints to ground architecture decisions.
  • Option generation & analysis: produces multiple architecture options with pros/cons and mapping to constraints.
  • Decision documentation: records recommendations, decisions, and open questions for traceability.

Quick Start

Design an architecture for a new service and present 2–3 options with trade-offs plus a recommended choice.

Frequently Asked Questions about architecture-design

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

FAQPage Schema
How do I design a scalable system architecture before coding?▼

Scalable system architecture requires gathering scale, latency, consistency, and cost constraints first, then generating 2–3 viable options to analyze trade-offs. This structured process grounds early-stage decisions and defines service boundaries before implementation.

What's the best way to evaluate architecture trade-offs for new components?▼

Evaluating architecture trade-offs is best done by mapping multiple design options against predefined constraints like team size and latency requirements. Producing pros and cons for each option ensures recommendations align with long-term system goals.

How do I define service boundaries and data models for a new service?▼

Defining service boundaries and data models involves capturing structural constraints early and applying option analysis. This process clarifies API design and maps data relationships across new components to ensure robust system architecture.

Can I document architecture decisions and open questions for traceability?▼

Yes, you can document architecture decisions for traceability by recording recommendations, decisions, and an open-questions section. This decision record ensures future teams understand the evaluated options and trade-offs.

Do I need to specify latency and consistency constraints to analyze API design?▼

Yes, specifying latency and consistency constraints is required to analyze API design effectively. Capturing these parameters grounds the architecture decisions and ensures generated options properly address system scalability and data model requirements.

Related Skills

Explore More Software Engineering Skills→
OzeroHAXOzeroHAX
32

coder-system-design-perf-patterns

Select system-level performance patterns for latency, throughput, or cost constraints.

Community
Advanced
hoanghd218hoanghd218

brainstorm

Generate 2-3 viable design options with trade-offs and risk assessments.

Community
Advanced
rakibulismrakibulism
2

system-architect

Design system architecture and record architecture decisions for services, APIs, and data models.

Community
Advanced
snoodleboot-iosnoodleboot-io
2

technical-decision-making

Assess technical solutions using structured criteria and best practices.

Official
Intermediate