architect

Design system architecture, APIs, and component interfaces using established patterns.

77|4|Updated Jun 20, 2022
One-click install
npx skills add https://github.com/htlin222/dotfiles --skill architect-htlin222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/htlin222/dotfiles/tree/main/claude.symlink/skills/architect
Command: npx skills add https://github.com/htlin222/dotfiles --skill architect-htlin222

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps in making critical architectural decisions, designing system components, and defining interfaces, ensuring scalable and maintainable software solutions.

Core Features & Use Cases

  • Architecture Design: Create blueprints for complex systems using various patterns like Layered, Microservices, and Event-Driven.
  • API & Interface Definition: Define clear component boundaries and interaction protocols.
  • Trade-off Analysis: Evaluate different design choices based on complexity, scalability, cost, and time-to-market.
  • Use Case: When starting a new project, use this Skill to outline the high-level architecture, choose between microservices or a monolith, and define the core APIs for each service.

Quick Start

Use the architect skill to design a scalable notification system architecture.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I design system architecture for a scalable application?

System architecture design for scalable applications involves creating blueprints using patterns like Layered, Microservices, or Event-Driven architectures. It defines clear component boundaries and interaction protocols to ensure maintainability.

What is the best way to evaluate trade-offs in system design?

Evaluating trade-offs in system design requires analyzing architectural choices based on complexity, scalability, cost, and time-to-market. It facilitates informed decisions by comparing different design patterns and component interactions.

When do I need event-driven architecture for my software?

Event-driven architecture is needed when designing scalable systems that require decoupled component interactions. It is one of several established patterns, alongside Microservices and Layered architectures, used to define clear interaction protocols.

How do I define APIs and component interfaces for microservices?

Defining APIs and interfaces for microservices involves establishing clear component boundaries and interaction protocols. This ensures scalable and maintainable software by dictating how independent services communicate and operate.

Can I use this to decide between a monolith or microservices architecture?

Yes, you can use it to decide between a monolith and microservices by evaluating trade-offs in complexity, scalability, and time-to-market. It helps outline high-level architecture and choose the most suitable pattern for your project.

What are the limitations of choosing microservices for system design?

Limitations of microservices in system design include increased complexity in component interaction and infrastructure management. Trade-off analysis helps evaluate if the scalability benefits outweigh the time-to-market and cost implications for your specific context.