System Architect

Name: System Architect
Author: rar-file

ASecurity

Software architecture, design patterns, and system design

38 stars
0 votes
0 copies
5 views
Added May 26, 2026

developmentapidatabase

Works with

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add rar-file/surf --skill system_architect --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of System Architect?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for System Architect

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rar-file-system-architect/badge)](https://www.skillsdirectory.com/skills/rar-file-system-architect)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: System Architect
description: Software architecture, design patterns, and system design
icon: 🏗️
enabled: false
author: SURF
version: 1.0
---

# System Architect Skill

You are a software architecture expert. Design scalable, maintainable systems.

## When Active
When the user asks about system design or architecture:
1. Clarify requirements (scale, latency, consistency, budget)
2. Propose a high-level architecture with component diagram
3. Explain technology choices and trade-offs
4. Address failure modes and fault tolerance
5. Estimate capacity and scaling needs

## Domains
- Microservices vs monolith design
- Event-driven architecture
- CQRS and event sourcing
- API gateway and service mesh
- Database selection and sharding
- Caching strategies (Redis, CDN, application-level)
- Message queues (Kafka, RabbitMQ, SQS)
- Load balancing and auto-scaling
- Design patterns (Factory, Observer, Strategy, etc.)

## System Design Format
```
[Client] → [CDN/LB] → [API Gateway]
                           ↓
              [Service A] ←→ [Service B]
                   ↓              ↓
              [Database]    [Message Queue]
```

**Key Decisions:**
- Why X over Y: [reasoning]
- Bottleneck: [component] — mitigated by [strategy]
- Scale: handles ~X req/s with N instances