mcpField
A
architect

architect

github.com/htlin222Development7840 installsUpdated 3w ago
Repository

About architect

A system architecture skill for teams making design decisions, reviewing structures, or planning refactors. It guides work from requirements through validation and documentation, with patterns and trade-off analysis.

Key features

  1. 01Requirements-to-design process
  2. 02Layered, microservice, and event-driven patterns
  3. 03Architecture trade-off analysis
  4. 04ADR documentation template
  5. 05Scalability checklist

Use cases

  1. 01Design a notification system
  2. 02Evaluate whether to adopt microservices
  3. 03Plan a large-scale refactor

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/htlin222/dotfiles --skill architect

After installing, type/architectin Claude Code to confirm it loaded.

Details

From the project README

System Architecture

Design scalable, maintainable system architectures.

When to Use

  • Major architectural decisions
  • System design discussions
  • Evaluating trade-offs
  • Planning large refactors
  • Reviewing system structure

Design Process

  1. Understand - Clarify requirements and constraints
  2. Identify - Define components and boundaries
  3. Design - Create architecture with trade-offs
  4. Validate - Check against requirements
  5. Document - Record decisions and rationale

Architecture Patterns

Layered Architecture
┌─────────────────────────────┐
│      Presentation Layer     │  UI, API endpoints
├─────────────────────────────┤
│       Business Layer        │  Domain logic, services
├─────────────────────────────┤
│      Persistence Layer      │  Repositories, DAOs
├─────────────────────────────┤
│        Data Layer           │  Database, cache
└─────────────────────────────┘
Microservices
┌─────────┐  ┌─────────┐  ┌─────────┐
│ User    │  │ Order   │  │ Payment │
│ Service │  │ Service │  │ Service │
└────┬────┘  └────┬────┘  └────┬────┘
     │            │            │
     └────────────┼────────────┘
                  │
           ┌──────┴──────┐
           │ Message Bus │
           └─────────────┘
Event-Driven
Producer → Event Bus → Consumer(s)
              │
              ├→ Service A
              ├→ Service B
              └→ Analytics

Decision Framework

Trade-off Analysis
AspectOption AOption B
ComplexityLowHigh
ScalabilityLimitedHorizontal
Cost$$$$
Time to marketFastSlow
MaintenanceEasyComplex
ADR Template
# ADR-001: [Decision Title]

## Status

Accepted | Proposed | Deprecated

## Context

[Why we need to make this decision]

## Decision

[What we decided]

## Consequences

### Positive

- [Benefit 1]

### Negative

- [Trade-off 1]

### Risks

- [Risk 1]

Key Principles

  • Separation of Concerns - Each component has one responsibility
  • Loose Coupling - Minimize dependencies between components
  • High Cohesion - Related functionality grouped together
  • YAGNI - Don't build for hypothetical requirements
  • Fail Fast - Detect and report errors immediately

Scalability Checklist

  • Stateless services (session in Redis/DB)
  • Horizontal scaling capability
  • Database read replicas
  • Caching layer (Redis, CDN)
  • Async processing for heavy tasks
  • Rate limiting and circuit breakers

Examples

Input: "Design a notification system" Action: Define channels, queue architecture, delivery guarantees, scaling strategy

Input: "Should we use microservices?" Action: Analyze team size, complexity, scaling needs, recommend with trade-offs

Comments

Markdown supported