skills.rest
nguyenphp
nguyenphpCOMMUNITY
Explore all skills by this author →
GitHub

architecture

Facilitate architectural decision-making with requirements analysis, trade-off evaluation, and ADR documentation.

41|12|Updated Jan 16, 2026
Search Tags:#architecture#decision making#system design#design patterns#ADR#trade-offs
One-click install
npx skills add https://github.com/nguyenphp/antigravity-marketing --skill architecture-nguyenphp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/nguyenphp/antigravity-marketing/tree/main/templates/.agent/skills/architecture
Command: npx skills add https://github.com/nguyenphp/antigravity-marketing --skill architecture-nguyenphp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework for making sound architectural decisions, ensuring that system designs are robust, scalable, and aligned with project requirements and constraints.

Core Features & Use Cases

  • Requirements Analysis: Guides the process of understanding project needs and constraints.
  • Trade-off Evaluation: Facilitates the systematic comparison of different architectural options.
  • ADR Documentation: Standardizes the recording of architectural decisions and their rationale.
  • Use Case: When designing a new microservice, use this Skill to analyze different communication patterns (e.g., REST vs. gRPC vs. message queues) and document the chosen approach with its trade-offs.

Quick Start

Use the architecture skill to analyze trade-offs for a new SaaS product's data access layer.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I evaluate trade-offs for system design decisions?▼

Evaluating trade-offs for system design requires a structured framework to compare architectural options against project scale, team expertise, and timeline constraints to identify the most robust solution.

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) standardizes the documentation of architectural choices and their rationale, needed when comparing patterns like REST versus gRPC to ensure system designs remain aligned with constraints.

How do I choose the right design patterns for my project scale?▼

Choosing the right design patterns requires analyzing project requirements and team expertise, systematically comparing options to ensure the selected architecture fits your specific scale and timeline constraints.

Can I use this framework to analyze communication patterns for microservices?▼

Yes, you can use this framework to analyze microservice communication patterns, evaluate options like REST versus message queues, and document the chosen approach with its specific trade-offs.

What is the best way to document architectural rationale and requirements?▼

The best way to document architectural rationale is using a standardized ADR format, which records requirements analysis and the specific trade-offs evaluated, ensuring system designs are robust and scalable.

Related Skills

Explore More Software Engineering Skills→
simoabidsimoabid
1

architecture

Guides requirements analysis, trade-off evaluation, and ADR documentation for architectural decisions.

Community
Advanced
LinoWhyLinoWhy

create-architecture-documentation

Generate C4 or arc42 architecture documentation from codebases and existing documentation.

Community
Intermediate
xenotaurxenotaur
1

lrh-design

Generate structured technical designs for software features using a multi-phase evaluation framework.

Community
Advanced
MisonLMisonL
8

architecture

Document architectural decisions with structured templates, checklists, and frontmatter-driven records.

Community
Advanced