skilld
All skills
jeffallan avatar

/architecture-designer

@efebc44
by jeffallanjeffallan/claude-skills12k stars
1,124

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

Ask your Agent

Use this Skill: https://skilld.dev/gh/jeffallan/claude-skills/architecture-designer

This session only. Nothing lands on disk.

referencesdatabase-selection.md

≈643 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Database Selection

Database Types

Type Examples Best For
Relational PostgreSQL, MySQL Transactions, complex queries, relationships
Document MongoDB, Firestore Flexible schemas, rapid iteration
Key-Value Redis, DynamoDB Caching, sessions, high throughput
Time-Series TimescaleDB, InfluxDB Metrics, IoT, analytics
Graph Neo4j, Neptune Relationships, social networks
Search Elasticsearch, Meilisearch Full-text search, logs

Relational (PostgreSQL, MySQL)

Best For:
- Financial transactions (ACID compliance)
- Complex queries with joins
- Data integrity requirements
- Structured, predictable schemas

When to Avoid:
- Highly variable schemas
- Massive horizontal scaling needs
- Simple key-value access patterns
Feature PostgreSQL MySQL
JSON support Excellent (JSONB) Good (JSON)
Full-text search Built-in Basic
Extensions Rich ecosystem Limited
Replication Streaming, logical Statement, row-based

Document (MongoDB, Firestore)

Best For:
- Flexible, evolving schemas
- Hierarchical data (nested documents)
- Rapid prototyping
- Content management

When to Avoid:
- Complex transactions across documents
- Heavy relational queries
- Strict schema requirements

Key-Value (Redis, DynamoDB)

Best For:
- Session storage
- Caching layer
- Real-time leaderboards
- Rate limiting counters

When to Avoid:
- Complex queries
- Relational data
- Large value sizes (>1MB)

Time-Series (TimescaleDB, InfluxDB)

Best For:
- Metrics and monitoring
- IoT sensor data
- Financial tick data
- Event logging with timestamps

When to Avoid:
- Frequent updates to existing records
- Complex relational queries
- Non-time-based access patterns

Decision Matrix

Requirement Recommended
ACID transactions PostgreSQL, MySQL
Flexible schema MongoDB, Firestore
High-speed caching Redis
Time-series data TimescaleDB, InfluxDB
Social relationships Neo4j
Full-text search Elasticsearch
Serverless scale DynamoDB, Firestore

Quick Reference

Question If Yes →
Need ACID transactions? Relational (PostgreSQL)
Schema changes frequently? Document (MongoDB)
Sub-millisecond reads? Key-Value (Redis)
Time-based queries? Time-Series
Traversing relationships? Graph (Neo4j)
Full-text search primary? Elasticsearch

Source: SKILL.md on GitHub

Third-party checks

1 alert16d5 checks · Risk CRITICAL
  • Gen Agent Trust Hub16d

    The skill provides a framework for system architecture design and documentation. It contains no executable code, persistence mechanisms, or data exfiltration logic. The documentation link flagged by external scanners is a plain-text reference to the author's official project page on a well-known hosting service.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    6 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at efebc44. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Steadyupdated 5 months ago

Capability

Other metadata
metadata
{
  "author": "https://github.com/Jeffallan",
  "version": "1.1.1",
  "domain": "api-architecture",
  "triggers": "architecture, system design, design pattern, microservices, scalability, ADR, technical design, infrastructure",
  "role": "expert",
  "scope": "design",
  "output-format": "document",
  "related-skills": "fullstack-guardian, devops-engineer, secure-code-guardian, microservices-architect, code-reviewer"
}

Topics

  • Infrastructure
  • architecture
  • system-design
  • adr
  • microservices
  • scalability
  • design-patterns
  • distributed-systems

README badge

README badge for jeffallan/claude-skills/architecture-designer

What it does

Guides system architecture design by creating diagrams, writing Architecture Decision Records, and evaluating trade-offs across patterns like microservices versus monoliths. Targets high-level design decisions, scalability planning, and technology selection—not code-level design patterns or isolated database choices.

Generated from the current SKILL.md.

Frequently asked

Does this skill help with code-level design patterns or just system architecture?
This skill focuses on high-level system architecture, microservices structuring, and infrastructure patterns. It is distinct from code-level design patterns or database-only design tasks.
What output formats does this skill produce?
The skill generates requirements summaries, architecture diagrams in Mermaid format, Architecture Decision Records (ADRs) documenting trade-offs, technology recommendations with rationale, and risk mitigation strategies.
Can this skill help evaluate technology choices?
Yes. The skill evaluates trade-offs across alternative technologies, considers operational costs and complexity, and provides rationale for technology recommendations rather than selecting options in isolation.
Does this skill address non-functional requirements?
Yes. The skill explicitly considers non-functional requirements as part of the design process, includes an NFR checklist reference, and factors scalability, failure modes, and operational complexity into architecture decisions.

Generated from the current SKILL.md. These answers refresh after source changes.