Architecture Decision

The architecture-decision skill enables AI agents to evaluate, compare, and select optimal system design patterns based on specific project constraints and requirements. It assists in documenting these choices by generating structured records that capture the reasoning behind technical decisions for future reference.

When to use it

• Evaluating multiple microservices vs. monolithic approaches for a new application startup.
• Selecting database storage solutions (e.g., SQL vs. NoSQL) based on data consistency needs.
• Determining cloud infrastructure strategies when scaling an existing legacy system.
• Documenting trade-offs between security protocols and development speed during a sprint.

Key capabilities

• Compares distinct architectural patterns against defined criteria.
• Generates detailed decision records including context, options considered, and rationale.
• Identifies potential risks and long-term implications of chosen designs.
• Adapts recommendations based on team size, budget limits, and timeline constraints.

Example prompts

• "Analyze the pros and cons of event-driven architecture versus request-response for our real-time analytics platform."
• "Create an architecture decision record for migrating our monolith to a serverless environment, considering cost and latency."
• "Recommend a caching strategy for a high-traffic e-commerce site with strict data consistency requirements."

Tips & gotchas

Ensure you provide clear constraints such as budget, team expertise, and performance targets to get relevant recommendations. This skill focuses on strategic design choices rather than implementation details like specific coding syntax or library versions.