architecture

Guide architectural decisions through requirements discovery, trade-off evaluation, and ADR documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams turn ambiguous system design inputs into clear architectural decisions by guiding requirements discovery, trade-off evaluation, and ADR documentation.

Core Features & Use Cases

  • Selective context discovery: Prioritizes the right questions (scale, team, timeline, domain, constraints) before proposing architecture.
  • Trade-off analysis and ADR-ready thinking: Uses structured templates to record context, options, rationale, consequences, and revisit triggers.
  • Pattern selection guidance: Provides decision trees to choose patterns based on data access complexity, business rules, independent scaling, and real-time needs.
  • Pattern and anti-pattern references: Quick lookup for common architecture patterns and red flags like premature microservices or over-abstraction.

Real-world use case: When planning the evolution of a product from an MVP to a SaaS offering, use this Skill to document why you chose a modular monolith, what alternatives you considered, and what trigger would justify moving toward distributed components.

Quick Start

Use the architecture skill to guide your next design session by asking the context questions first, then selecting patterns via the decision tree and recording the outcome in an ADR draft.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I write an Architecture Decision Record for system design?

To write an Architecture Decision Record (ADR), document the context, evaluated options, trade-off analysis, rationale, consequences, and revisit triggers to capture why a specific architectural choice was made.

What is the best way to choose architecture patterns during a design session?

Choosing architecture patterns involves using a decision tree to evaluate data access complexity, business rules, independent scaling requirements, and real-time needs to select the optimal pattern for your system constraints.

How do I evaluate trade-offs when evolving an MVP to an enterprise SaaS architecture?

Evaluating trade-offs for MVP-to-enterprise evolution requires structured requirements discovery covering scale, team size, timeline, and domain constraints before proposing a pattern like a modular monolith.

When should I avoid premature microservices in system design?

Avoid premature microservices by recognizing them as an anti-pattern during pattern selection, opting for a modular monolith until independent scaling or real-time needs justify distributed components.

What context do I need for requirements discovery before selecting software architecture?

Requirements discovery for software architecture prioritizes questions about system scale, team structure, project timeline, domain complexity, and technical constraints to gather necessary context before proposing solutions.