โ† Back to list
georgekhananaev

system-architect

by georgekhananaev

A curated collection of high impact skills for Claude Code designed to supercharge the senior full stack workflow. This vault automates the repetitive parts of development like architectural reviews, TDD cycles, and PR management so you can stay in flow. It is a force multiplier for shipping clean, production ready code at scale. ๐Ÿš€โšก๏ธ

โญ 5๐Ÿด 5๐Ÿ“… Jan 14, 2026

SKILL.md


name: system-architect description: System architecture skill for designing scalable, maintainable software systems. Covers microservices/monolith decisions, API design, DB selection, caching, security, and scalability planning.

System Architect Skill

Design scalable, maintainable software systems.

When to Use

  • Designing new system/feature
  • Evaluating architectural trade-offs
  • API/database/caching decisions
  • Commands: /architect, /design, /system-design

Capabilities

1. System Design

  • Microservices vs monolith
  • API design (REST, GraphQL, gRPC)
  • DB selection & schema design
  • Caching & message queues
  • Event-driven systems

2. Scalability

  • Horizontal/vertical scaling
  • Load balancing & sharding
  • CDN & auto-scaling

3. Reliability

  • HA patterns & DR planning
  • Circuit breaker & retry
  • Graceful degradation

4. Security

  • Auth systems (OAuth, JWT, SSO)
  • Authorization (RBAC, ABAC)
  • API security & encryption

Architecture Decision Process

Step 1: Requirements

1. Functional: Core features, workflows, integrations
2. Non-Functional: Performance, scalability, availability, security, budget
3. Constraints: Tech stack, team expertise, timeline, existing systems

Step 2: Pattern Selection

Reference patterns.json for patterns, tech recommendations, trade-offs.

Step 3: Design Doc Template

# Architecture Design Document

## 1. Overview
[High-level description]

## 2. Goals & Non-Goals

## 3. Architecture
### System Diagram
### Components
| Component | Responsibility | Technology |
|-----------|---------------|------------|

### Data Flow

## 4. Technical Decisions
### Decision 1: [Title]
- Context | Options | Decision | Rationale

## 5. API Design
## 6. Data Model
## 7. Security
## 8. Scalability
## 9. Monitoring & Observability
## 10. Risks & Mitigations

Pattern Reference

Communication

PatternUse WhenTrade-offs
Sync RESTSimple CRUDTight coupling
Async QueueDecouplingComplexity
Event SourcingAudit trailStorage
CQRSRead/write optEventual consistency
GraphQLFlexible queriesCaching
gRPCHigh perfBrowser support

Data

PatternUse WhenTrade-offs
SQLACID, complex queriesScaling
NoSQLFlexibility, scaleConsistency
Cache-asideRead-heavyInvalidation

Resilience

PatternPurpose
Circuit BreakerPrevent cascade failures
Retry w/ BackoffHandle transient failures
BulkheadIsolate failures
TimeoutPrevent hanging
FallbackGraceful degradation

Project Structures

Reference structures.json for:

  • Python: FastAPI, Django
  • TypeScript: Next.js, React, Express
  • Java: Spring Boot
  • Go: Standard Layout

Tech Stack Recommendations

Web Apps

Frontend: React/Next.js, Vue/Nuxt, Angular
Backend: Node.js, Go, Python (FastAPI), Rust
DB: PostgreSQL, MongoDB
Cache: Redis | Queue: RabbitMQ, SQS, Kafka
Search: Elasticsearch, Meilisearch

Real-time

WebSocket: Socket.io, ws
Pub/Sub: Redis, Kafka

Data-Intensive

Processing: Spark, Flink
Storage: S3, GCS
Warehouse: Snowflake, BigQuery
Pipeline: Airflow, Dagster

Diagramming

ASCII Component

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”     โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”     โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚   Client    โ”‚โ”€โ”€โ”€โ”€โ–ถโ”‚ API Gateway โ”‚โ”€โ”€โ”€โ”€โ–ถโ”‚  Services   โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜     โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜     โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                           โ”‚                   โ”‚
                           โ–ผ                   โ–ผ
                    โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”     โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
                    โ”‚    Auth     โ”‚     โ”‚  Database   โ”‚
                    โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜     โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Mermaid Sequence

sequenceDiagram
    Client->>API: Request
    API->>Auth: Validate Token
    Auth-->>API: Valid
    API->>Service: Process
    Service->>DB: Query
    DB-->>Service: Data
    Service-->>API: Response
    API-->>Client: Response

Evaluation Criteria

CriterionWeightDescription
ScalabilityHighCan it handle growth?
MaintainabilityHighEasy to modify/debug?
PerformanceMed-HighMeets latency/throughput?
CostMediumInfra + dev cost
SecurityHighMeets requirements?
ComplexityMediumTeam can build/operate?

Output Templates

Quick Decision

**Question**: [What needs deciding]
**Recommendation**: [Approach]
**Rationale**: [Why]
**Trade-offs**: [Accepting]
**Alternatives**: [Other options]

Integration

  • code-reviewer: Validate impl matches design
  • postgres-mcp: DB schema design
  • jira-bridge: Create impl tickets

Score

Total Score

75/100

Based on repository quality metrics

โœ“SKILL.md

SKILL.mdใƒ•ใ‚กใ‚คใƒซใŒๅซใพใ‚Œใฆใ„ใ‚‹

+20
โœ“LICENSE

ใƒฉใ‚คใ‚ปใƒณใ‚นใŒ่จญๅฎšใ•ใ‚Œใฆใ„ใ‚‹

+10
โœ“่ชฌๆ˜Žๆ–‡

100ๆ–‡ๅญ—ไปฅไธŠใฎ่ชฌๆ˜ŽใŒใ‚ใ‚‹

+10
โ—‹ไบบๆฐ—

GitHub Stars 100ไปฅไธŠ

0/15
โœ“ๆœ€่ฟ‘ใฎๆดปๅ‹•

1ใƒถๆœˆไปฅๅ†…ใซๆ›ดๆ–ฐ

+10
โ—‹ใƒ•ใ‚ฉใƒผใ‚ฏ

10ๅ›žไปฅไธŠใƒ•ใ‚ฉใƒผใ‚ฏใ•ใ‚Œใฆใ„ใ‚‹

0/5
โœ“Issue็ฎก็†

ใ‚ชใƒผใƒ—ใƒณIssueใŒ50ๆœชๆบ€

+5
โœ“่จ€่ชž

ใƒ—ใƒญใ‚ฐใƒฉใƒŸใƒณใ‚ฐ่จ€่ชžใŒ่จญๅฎšใ•ใ‚Œใฆใ„ใ‚‹

+5
โœ“ใ‚ฟใ‚ฐ

1ใคไปฅไธŠใฎใ‚ฟใ‚ฐใŒ่จญๅฎšใ•ใ‚Œใฆใ„ใ‚‹

+5

Reviews

๐Ÿ’ฌ

Reviews coming soon