{"enrichment":{"faq":[{"a":"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.","q":"How to design a scalable system architecture?"},{"a":"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\u2014deployment simplicity, team autonomy, data consistency, operational overhead\u2014and choose based on your system's requirements, team size, and growth trajectory.","q":"What are the main differences between microservices vs monolithic architecture?"},{"a":"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.","q":"How does Architecture help with system design interview preparation?"},{"a":"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.","q":"What design patterns and best practices does Architecture cover?"},{"a":"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.","q":"How do I choose between REST, GraphQL, and gRPC for my system?"},{"a":"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.","q":"What's included in Architecture's approach to documenting decisions?"}],"shadow_tags":["system-design","distributed-systems","design-patterns","scalability","infrastructure-planning","technology-stack","resilience-engineering","capacity-modeling","api-design","architectural-decisions"],"summary_rewrite":"Architecture guides you through designing complete system architectures\u2014from 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."},"files":[{"bytes":17715,"path":"skills/architecture/SKILL.md","sha256":"5edafddebcb3a9357dc5303894aa15f46c77002266a01d5ed4ecb72b2cef9a64","url":"https://skillfed.io/files/josavicentevw/ai-agent-skills/architecture/0625b9b0/SKILL.md"}],"id":"josavicentevw/ai-agent-skills/architecture","links":{"html":"https://skillfed.io/josavicentevw/ai-agent-skills/architecture","md":"https://skillfed.io/josavicentevw/ai-agent-skills/architecture.md","repo":"https://github.com/josavicentevw/ai-agent-skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":0,"language":"Python","last_updated":"2026-02-05","license":"MIT","name":"architecture","publisher":"josavicentevw","stars":1},"relations":{"categories":["software-architecture","system-design","devops"],"similar":[{"id":"personamanagmentlayer/pcl/design-expert"},{"id":"organvm/a-i--skills/resilience-patterns"},{"id":"Aradotso/ai-agent-skills/production-grade-agentic-system"},{"id":"HermeticOrmus/LibreUIUX-Claude-Code/error-handling-patterns"},{"id":"secondsky/claude-skills/microservices-patterns"},{"id":"eyadsibai/ltk/microservices-patterns"},{"id":"HermeticOrmus/LibreUIUX-Claude-Code/microservices-patterns"},{"id":"BagelHole/DevOps-Security-Agent-Skills/ai-agent-security"},{"id":"foryourhealth111-pixel/Vibe-Skills/architecture-patterns"},{"id":"HermeticOrmus/LibreUIUX-Claude-Code/architecture-patterns"}]},"slug":{"owner":"josavicentevw","repo":"ai-agent-skills","skill":"architecture"},"version":"0625b9b0"}