Verified:GitHub

architecture

Guides architectural decision-making through requirements analysis, trade-off evaluation, and ADR documentation.

41|Updated Apr 14, 2026

Search Tags:#architecture #system design #design patterns #microservices #adr #decision framework #trade-off analysis

One-click install

npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill architecture-devayoshaus

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/DevayoshaUS/Women-scholarship/tree/main/hackathon-main%20%281%29/hackathon-main/.agent/skills/architecture
Command: npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill architecture-devayoshaus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right software architecture is hard: teams often over-engineer simple projects or under-design systems that later need to scale. This Skill provides a structured framework for analyzing requirements, evaluating trade-offs, selecting patterns, and documenting decisions as Architecture Decision Records (ADRs). ## Core Features & Use Cases - Context Discovery: A question hierarchy covering scale, team, timeline, domain, and constraints, plus a project classification matrix (MVP, SaaS, Enterprise). - Pattern Selection: Decision trees for data access, domain logic, distributed systems, and real-time requirements, with anti-pattern red flags. - Trade-off Analysis & ADRs: Templates for documenting options, rationale, accepted trade-offs, consequences, and revisit triggers. - Use Case: A solo developer building an e-commerce MVP uses the framework to justify a Next.js monolith with Prisma and PostgreSQL, documenting each decision and its future migration path in ADRs. ## Quick Start Ask the assistant to help design the architecture for your project by describing your expected scale, team size, timeline, and constraints.

Frequently Asked Questions about architecture

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

FAQPage Schema

What questions should I ask before designing a system architecture?▼

Ask about scale (users, data volume, transaction rate), team size and expertise, timeline pressure, domain complexity, and constraints like budget or legacy integrations. These answers classify the project as MVP, SaaS, or Enterprise and drive pattern selection.