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.

referencesnfr-checklist.md

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

Non-Functional Requirements Checklist

NFR Categories

Scalability

Question Common Targets
Expected concurrent users? 100 / 1K / 10K / 100K
Requests per second? 10 / 100 / 1000 / 10000
Data volume? GB / TB / PB
Growth rate? 10% / 50% / 100% per year
Peak vs average load? 2x / 5x / 10x

Performance

Question Common Targets
API response time? < 100ms / 200ms / 500ms p95
Page load time? < 1s / 2s / 3s
Database query time? < 10ms / 50ms / 100ms
Batch processing throughput? 1K / 10K / 100K records/hour

Availability

Target Downtime/Year Use Case
99% 3.65 days Internal tools
99.9% 8.76 hours Business apps
99.95% 4.38 hours E-commerce
99.99% 52.6 minutes Financial systems
99.999% 5.26 minutes Life-critical

Security

Question Considerations
Authentication required? JWT, OAuth, SAML, MFA
Authorization model? RBAC, ABAC, ACL
Data sensitivity? Public, internal, confidential, PII
Compliance requirements? GDPR, HIPAA, PCI DSS, SOC 2
Encryption needs? At rest, in transit, end-to-end

Reliability

Question Considerations
Acceptable data loss? RPO: 0 / 1hr / 24hr
Recovery time target? RTO: 1hr / 4hr / 24hr
Backup frequency? Real-time / hourly / daily
Disaster recovery? Single region / multi-region

Maintainability

Question Considerations
Deployment frequency? Daily / weekly / monthly
Deployment strategy? Blue-green, canary, rolling
Monitoring requirements? Logs, metrics, traces, alerts
On-call requirements? 24/7, business hours

Cost

Question Considerations
Infrastructure budget? $/month, $/user, $/request
Operational budget? FTE for maintenance
Cost optimization? Reserved instances, spot instances
Cost alerts? Thresholds for notification

Template

## Non-Functional Requirements

### Performance
- API response time: < 200ms p95
- Page load time: < 2s
- Database query time: < 50ms

### Scalability
- Concurrent users: 10,000
- Requests per second: 1,000
- Data volume: 1TB

### Availability
- Target: 99.9% (8.76 hours/year downtime)
- RPO: 1 hour
- RTO: 4 hours

### Security
- Authentication: JWT with refresh tokens
- Authorization: Role-based (admin, user, guest)
- Compliance: GDPR, SOC 2

### Observability
- Logging: Structured JSON to ELK
- Metrics: Prometheus + Grafana
- Tracing: OpenTelemetry
- Alerts: PagerDuty integration

Quick Reference

Category Key Metric
Performance Response time (p95)
Scalability Concurrent users, RPS
Availability Uptime percentage
Reliability RPO, RTO
Security Compliance requirements
Cost $/month budget

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.