architecture
Architecture guides you through designing complete system architectures—from monolithic and microservices to event-driven and serverless approaches. It covers design patterns, quality attributes like performance and security, technology selection, and provides frameworks for documenting architectural decisions. Use it to evaluate trade-offs, plan scalability, and ensure your systems are maintainable and resilient.
Architecture helps you design, evaluate, and document software system architectures for scalability and maintainability.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-02-05
Architecture helps you design, evaluate, and document software system architectures for scalability and maintainability. Architecture guides you through designing complete system architectures—from monolithic and microservices to event-driven and serverless approaches. It covers design patterns, quality attributes like performance and security, technology selection, and provides frameworks for documenting architectural decisions. Use it to evaluate trade-offs, plan scalability, and ensure your systems are maintainable and resilient.
Use it when
- Architecture compares these fundamental approaches: monolithic systems bundle all functionality in one deployable unit (simpler initially.
- Architecture prepares you for system design interviews by covering the full scope: designing high-availability distributed systems.
Verify before relying
Read SKILL.md below before installing (4 files). Open directory: indexed for reading, not audited.
Install
josavicentevw/ai-agent-skills/architecture · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to design a scalable system architecture?
Architecture helps you design scalable systems by covering monolithic, microservices, event-driven, and serverless approaches. It guides you through key patterns like API gateways, circuit breakers, and load balancing, plus strategies for horizontal and vertical database scaling. You'll learn to evaluate trade-offs between approaches, plan for performance optimization, and ensure your architecture supports growth from initial design through millions of users.
What are the main differences between microservices vs monolithic architecture?
Architecture compares these fundamental approaches: monolithic systems bundle all functionality in one deployable unit (simpler initially, harder to scale), while microservices split functionality into independent services (better scalability, increased complexity). Architecture helps you weigh trade-offs—deployment simplicity, team autonomy, data consistency, operational overhead—and choose based on your system's requirements, team size, and growth trajectory.
How does Architecture help with system design interview preparation?
Architecture prepares you for system design interviews by covering the full scope: designing high-availability distributed systems, capacity planning, technology selection frameworks, and documented decision-making. It teaches patterns like CQRS, event sourcing, hexagonal architecture, and resilience strategies. You'll learn to articulate trade-offs, justify architectural choices, and present structured solutions using frameworks like the C4 model for documentation.
What design patterns and best practices does Architecture cover?
Architecture covers essential patterns including API gateways, circuit breakers, event-driven systems, CQRS, event sourcing, and hexagonal architecture (ports and adapters). It addresses caching strategies (Redis, CDN), load balancing, fault tolerance, and resilience patterns. You'll also learn technology selection criteria, documentation approaches like architecture decision records (ADR) and C4 models, and evaluation frameworks for reviewing architectural choices.
How do I choose between REST, GraphQL, and gRPC for my system?
Architecture provides a technology selection framework to compare REST, GraphQL, and gRPC based on your system's needs. It helps you evaluate criteria like query flexibility, performance, real-time requirements, and client complexity. Each has trade-offs: REST is simple and cacheable, GraphQL reduces over-fetching, gRPC offers high performance for service-to-service communication. Architecture guides you through documenting these decisions using architecture decision records.
What's included in Architecture's approach to documenting decisions?
Architecture teaches you to document architectural decisions through architecture decision records (ADR templates) and the C4 model for visualizing systems at different abstraction levels. It emphasizes capturing trade-offs, rationale, and consequences so teams understand why choices were made. This documentation supports architecture reviews, onboarding, and ensures decisions remain traceable and maintainable as systems evolve.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Architecture
A comprehensive architecture skill that helps design, evaluate, and document software architectures for robust, scalable, and maintainable systems.
Quick Start
Basic architecture workflow:
# Understand requirements (functional + non-functional)
# Identify constraints and trade-offs
# Design system components and relationships
# Document architecture decisions
# Validate against requirements
Core Capabilities
1. System Architecture Design
Design complete system architectures:
- Monolithic: Single deployable unit
- Microservices: Distributed services architecture
- Serverless: Event-driven, function-based
- Event-Driven: Asynchronous message-based
- Layered: Separation of concerns in layers
- Hexagonal: Ports and adapters pattern
- CQRS: Command Query Responsibility
(truncated - see the full file via the links below)
File tree — 4 files
skills/architecture/SKILL.md
skills/architecture/examples/01-microservices-design.md
skills/architecture/examples/02-system-design.md
skills/architecture/examples/README.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Design or evaluate a software system architecture”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill covers error handling strategies for building resilient applications across multiple languages. Learn when to use exceptions versus Result types, how to categorize recoverable and unrecoverable errors, and implement patterns like retry with exponential backoff and async error handling. Includes language-specific examples for Python, TypeScript, and Rust.
Learn to architect microservices by decomposing monoliths into independent services, managing inter-service communication through synchronous and asynchronous patterns, and implementing resilience strategies like circuit breakers and sagas. This skill covers service decomposition strategies, data management across distributed systems, and practical patterns for building fault-tolerant distributed architectures.
Master the core patterns for building distributed architectures, from decomposing monoliths to implementing resilient inter-service communication. Covers service boundaries organized by business capability, synchronous and asynchronous messaging, and failure-handling techniques like circuit breakers and bulkheads.
Master architectural patterns for building distributed systems through service decomposition, inter-service communication strategies, and fault tolerance techniques. Covers synchronous and asynchronous messaging, database ownership models, and resilience patterns like circuit breakers and bulkheads.
Make informed architecture decisions for new systems or major refactors. This skill guides you through pattern selection, scalability design, resilience strategies, and data consistency models—with concrete technology recommendations and tradeoff analysis. Covers decomposition, service boundaries, observability planning, and migration from legacy systems.
Master three foundational backend architecture approaches—Clean Architecture, Hexagonal Architecture, and Domain-Driven Design—to structure systems for testability, maintainability, and scalability. Each pattern teaches dependency management, separation of concerns, and technology-agnostic core logic through practical examples and directory structures.
More skills design-system-patterns (MIT) · architecting-security (MIT) · architecture-designer (MIT)