architecture

Generate ADR templates and system design checklists for architectural decisions.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/dr-code/beacon --skill architecture-dr-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/dr-code/beacon/tree/main/plugins/cc-best/skills/architecture
Command: npx skills add https://github.com/dr-code/beacon --skill architecture-dr-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides clear, repeatable guidance to avoid ad-hoc architecture decisions, reduce design drift, and ensure critical trade-offs are documented so teams can build scalable, reliable systems.

Core Features & Use Cases

  • ADR (Architecture Decision Records): Templates and guidance for capturing context, options, and rationale for significant technical choices.
  • System Design Checklist: Practical checks for scalability, reliability, observability, security, and operational concerns during design reviews.
  • Architecture Patterns & API Design: Recommendations for microservices, event-driven, layered, and hexagonal patterns plus RESTful API conventions, versioning, pagination, and error handling.
  • Use Case: Use the skill to draft an ADR when deciding between a monolith and microservices, perform a scalability assessment for a new service, or run a checklist before production launch.

Quick Start

Ask the architecture skill to create an ADR comparing monolith and microservices for a new user service, include context, alternatives, and recommended rationale.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I write an Architecture Decision Record for choosing between a monolith and microservices?

An Architecture Decision Record captures context, alternatives, and rationale for system design choices. You can draft a structured ADR comparing monolith and microservices by evaluating scalability, reliability, and operational trade-offs to document the recommended decision.

What should be included in a system design checklist for production launch?

A system design checklist should include practical checks for scalability, reliability, observability, security, and operational concerns. Running this checklist during design reviews ensures your architecture meets fault tolerance and monitoring requirements before production launch.

When do I need to use event-driven architecture patterns?

Event-driven architecture patterns are needed when designing systems requiring asynchronous communication and high scalability. You can select from event-driven, microservices, layered, or hexagonal patterns by evaluating your specific reliability and decoupling requirements during technical planning.

How do I define RESTful API conventions for versioning, pagination, and error handling?

RESTful API conventions define standardized rules for versioning, pagination, and error handling. You can refine API design by establishing consistent conventions that emphasize observability, fault tolerance, and security across your system architecture interfaces.

How do I perform a scalability assessment for a new service?

A scalability assessment evaluates whether a new service can handle growth while maintaining performance. You can perform this assessment using structured guidance to analyze system design limits, identify bottlenecks, and ensure fault tolerance under increased load.

Why does ad-hoc architecture decision-making cause design drift?

Ad-hoc architecture decisions cause design drift because critical trade-offs remain undocumented and unreviewed. Using structured decision-making guidance and ADR templates prevents this by ensuring repeatable processes for scalability, reliability, and security evaluations across teams.