skills.rest
phillippelevidad
phillippelevidadCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-designer

Design scalable distributed systems and document architectural decisions with ADRs.

Updated Jun 12, 2026
Search Tags:#architecture#scalability#system design#microservices#adr#technical design
One-click install
npx skills add https://github.com/phillippelevidad/ai-led-engineering --skill architecture-designer-phillippelevidad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/phillippelevidad/ai-led-engineering/tree/main/.agents/skills/architecture-designer
Command: npx skills add https://github.com/phillippelevidad/ai-led-engineering --skill architecture-designer-phillippelevidad

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the complexity of designing scalable, maintainable systems by providing a structured framework for architectural decision-making, trade-off analysis, and technical documentation.

Core Features & Use Cases

  • ADR Authoring: Standardizes the creation of Architecture Decision Records to ensure long-term project clarity.
  • System Design & Review: Facilitates the design of distributed systems, microservices, and infrastructure patterns with a focus on non-functional requirements.
  • Trade-off Analysis: Guides the evaluation of technology choices (e.g., database selection, pattern adoption) by weighing pros, cons, and operational impacts.

Quick Start

Invoke the architecture-designer skill to create a new system design proposal for a microservices-based order processing system including an ADR for the database choice.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I write an Architecture Decision Record for a distributed system?▼

To write an Architecture Decision Record (ADR), standardize your architectural decision documentation to ensure long-term project clarity, capturing context, decisions, and trade-offs for stakeholder alignment and maintainability.

What is the best way to design scalable microservices architecture?▼

Designing scalable microservices architecture involves selecting appropriate distributed system patterns, analyzing technology trade-offs, and planning non-functional requirements to ensure long-term maintainability for complex software projects.

How do I evaluate technology trade-offs for database selection in system design?▼

Evaluating database selection trade-offs requires weighing the pros, cons, and operational impacts of technology choices against your specific non-functional requirements and architectural patterns to guide rigorous technical design.

How does non-functional requirement planning work for distributed systems?▼

Non-functional requirement planning for distributed systems works by defining scalability, reliability, and maintainability constraints early, guiding architectural pattern selection and technology trade-off analysis during technical design.

When do I need to document architectural decisions for a software project?▼

You need to document architectural decisions when tackling complex software projects requiring rigorous technical design, stakeholder alignment, and long-term maintainability, ensuring clarity through standardized ADR authoring.

Related Skills

Explore More Software Engineering Skills→
codeApe-7codeApe-7
17

architecture-designer

Creates architectural system designs and generates BSDs from high-level specifications.

Community
Advanced
larus-perituslarus-peritus

Technical Design

Translate approved requirements into technical designs with data models and testing strategy.

Community
Advanced
RebornQRebornQ
52

trellis-update-spec

Update executable contracts and coding conventions into .trellis/spec/ documents.

Community
Advanced
jungmini0601jungmini0601

planning

Plan technical implementations and design system architectures with roadmaps.

Community
Advanced