skills.rest
jlaws
jlawsCOMMUNITY
Explore all skills by this author →
GitHub

agent-architecture-specialist

Identify optimal system architectures and API designs for scalable software platforms.

2|Updated Jan 3, 2026
Search Tags:#architecture#patterns#api-design#system-design#decision-records#reference-library#distributed-patterns
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill agent-architecture-specialist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-architecture-specialist
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/agent-architecture-specialist
Command: npx skills add https://github.com/jlaws/dotfiles --skill agent-architecture-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides expert guidance for designing scalable system architectures, API contracts, and distributed patterns to help teams make architecture decisions.

Core Features & Use Cases

  • Architecture decision guidance for high-level system design, API boundary definitions, and distributed patterns.
  • Reference material and best practices drawn from established design principles and common patterns.
  • Use Case: You are evaluating whether to adopt an event-driven architecture versus a request-response model for a new service.

Quick Start

Outline a high-level reference architecture for a scalable microservices platform with clear API boundaries and data flow.

Frequently Asked Questions about agent-architecture-specialist

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

FAQPage Schema
How do I design scalable system architectures for microservices?▼

Event-driven architecture decouples services for asynchronous processing, while request-response models offer synchronous, immediate data retrieval. Choosing between them requires evaluating data flow needs and non-functional requirements.

What is the best way to define API contracts for distributed systems?▼

Architecture decision records document design choices for high-level system architecture, API boundary definitions, and distributed patterns. They provide reference material to guide technology evaluation and align non-functional requirements.

How do I evaluate an event-driven architecture versus a request-response model?▼

Evaluating event-driven versus request-response models requires analyzing data flow considerations and non-functional requirements. Event-driven supports asynchronous distributed patterns, while request-response offers immediate synchronous API design interactions.

When do I need architecture decision records for system design?▼

Architecture decision records are needed during high-level design reviews and technology evaluation to document system architectures and API contracts. They ensure teams align on distributed patterns and non-functional requirements.

Related Skills

Explore More Software Engineering Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
product-on-purposeproduct-on-purpose
527

develop-adr

Generate Architecture Decision Records using the Nygard-style ADR template.

Official
Basic
2good4me2good4me

system-architect

Design system architecture with tech stack selection and NFR coverage.

Community
Advanced
dralgorhythmdralgorhythm
111

designing-systems

Design scalable software systems with C4 diagrams and trade-off analysis.

Community
Advanced