mirror of
https://github.com/wshobson/agents.git
synced 2026-03-18 09:37:15 +00:00
feat: add Agent Skills and restructure documentation
- Add 47 Agent Skills across 14 plugins following Anthropic's specification - Python (5): async patterns, testing, packaging, performance, UV package manager - JavaScript/TypeScript (4): advanced types, Node.js patterns, testing, modern JS - Kubernetes (4): manifests, Helm charts, GitOps, security policies - Cloud Infrastructure (4): Terraform, multi-cloud, hybrid networking, cost optimization - CI/CD (4): pipeline design, GitHub Actions, GitLab CI, secrets management - Backend (3): API design, architecture patterns, microservices - LLM Applications (4): LangChain, prompt engineering, RAG, evaluation - Blockchain/Web3 (4): DeFi protocols, NFT standards, Solidity security, Web3 testing - Framework Migration (4): React, Angular, database, dependency upgrades - Observability (4): Prometheus, Grafana, distributed tracing, SLO - Payment Processing (4): Stripe, PayPal, PCI compliance, billing - API Scaffolding (1): FastAPI templates - ML Operations (1): ML pipeline workflow - Security (1): SAST configuration - Restructure documentation into /docs directory - agent-skills.md: Complete guide to all 47 skills - agents.md: All 85 agents with model configuration - plugins.md: Complete catalog of 63 plugins - usage.md: Commands, workflows, and best practices - architecture.md: Design principles and patterns - Update README.md - Add Agent Skills banner announcement - Reduce length by ~75% with links to detailed docs - Add What's New section showcasing Agent Skills - Add Popular Use Cases with real examples - Improve navigation with Core Guides and Quick Links - Update marketplace.json with skills arrays for 14 plugins All 47 skills follow Agent Skills Specification: - Required YAML frontmatter (name, description) - Use when activation clauses - Progressive disclosure architecture - Under 1024 character descriptions
This commit is contained in:
Seth Hobson
@@ -0,0 +1,177 @@
|
||||
---
|
||||
name: multi-cloud-architecture
|
||||
description: Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services from multiple providers.
|
||||
---
|
||||
|
||||
# Multi-Cloud Architecture
|
||||
|
||||
Decision framework and patterns for architecting applications across AWS, Azure, and GCP.
|
||||
|
||||
## Purpose
|
||||
|
||||
Design cloud-agnostic architectures and make informed decisions about service selection across cloud providers.
|
||||
|
||||
## When to Use
|
||||
|
||||
- Design multi-cloud strategies
|
||||
- Migrate between cloud providers
|
||||
- Select cloud services for specific workloads
|
||||
- Implement cloud-agnostic architectures
|
||||
- Optimize costs across providers
|
||||
|
||||
## Cloud Service Comparison
|
||||
|
||||
### Compute Services
|
||||
|
||||
| AWS | Azure | GCP | Use Case |
|
||||
|-----|-------|-----|----------|
|
||||
| EC2 | Virtual Machines | Compute Engine | IaaS VMs |
|
||||
| ECS | Container Instances | Cloud Run | Containers |
|
||||
| EKS | AKS | GKE | Kubernetes |
|
||||
| Lambda | Functions | Cloud Functions | Serverless |
|
||||
| Fargate | Container Apps | Cloud Run | Managed containers |
|
||||
|
||||
### Storage Services
|
||||
|
||||
| AWS | Azure | GCP | Use Case |
|
||||
|-----|-------|-----|----------|
|
||||
| S3 | Blob Storage | Cloud Storage | Object storage |
|
||||
| EBS | Managed Disks | Persistent Disk | Block storage |
|
||||
| EFS | Azure Files | Filestore | File storage |
|
||||
| Glacier | Archive Storage | Archive Storage | Cold storage |
|
||||
|
||||
### Database Services
|
||||
|
||||
| AWS | Azure | GCP | Use Case |
|
||||
|-----|-------|-----|----------|
|
||||
| RDS | SQL Database | Cloud SQL | Managed SQL |
|
||||
| DynamoDB | Cosmos DB | Firestore | NoSQL |
|
||||
| Aurora | PostgreSQL/MySQL | Cloud Spanner | Distributed SQL |
|
||||
| ElastiCache | Cache for Redis | Memorystore | Caching |
|
||||
|
||||
**Reference:** See `references/service-comparison.md` for complete comparison
|
||||
|
||||
## Multi-Cloud Patterns
|
||||
|
||||
### Pattern 1: Single Provider with DR
|
||||
|
||||
- Primary workload in one cloud
|
||||
- Disaster recovery in another
|
||||
- Database replication across clouds
|
||||
- Automated failover
|
||||
|
||||
### Pattern 2: Best-of-Breed
|
||||
|
||||
- Use best service from each provider
|
||||
- AI/ML on GCP
|
||||
- Enterprise apps on Azure
|
||||
- General compute on AWS
|
||||
|
||||
### Pattern 3: Geographic Distribution
|
||||
|
||||
- Serve users from nearest cloud region
|
||||
- Data sovereignty compliance
|
||||
- Global load balancing
|
||||
- Regional failover
|
||||
|
||||
### Pattern 4: Cloud-Agnostic Abstraction
|
||||
|
||||
- Kubernetes for compute
|
||||
- PostgreSQL for database
|
||||
- S3-compatible storage (MinIO)
|
||||
- Open source tools
|
||||
|
||||
## Cloud-Agnostic Architecture
|
||||
|
||||
### Use Cloud-Native Alternatives
|
||||
|
||||
- **Compute:** Kubernetes (EKS/AKS/GKE)
|
||||
- **Database:** PostgreSQL/MySQL (RDS/SQL Database/Cloud SQL)
|
||||
- **Message Queue:** Apache Kafka (MSK/Event Hubs/Confluent)
|
||||
- **Cache:** Redis (ElastiCache/Azure Cache/Memorystore)
|
||||
- **Object Storage:** S3-compatible API
|
||||
- **Monitoring:** Prometheus/Grafana
|
||||
- **Service Mesh:** Istio/Linkerd
|
||||
|
||||
### Abstraction Layers
|
||||
|
||||
```
|
||||
Application Layer
|
||||
↓
|
||||
Infrastructure Abstraction (Terraform)
|
||||
↓
|
||||
Cloud Provider APIs
|
||||
↓
|
||||
AWS / Azure / GCP
|
||||
```
|
||||
|
||||
## Cost Comparison
|
||||
|
||||
### Compute Pricing Factors
|
||||
|
||||
- **AWS:** On-demand, Reserved, Spot, Savings Plans
|
||||
- **Azure:** Pay-as-you-go, Reserved, Spot
|
||||
- **GCP:** On-demand, Committed use, Preemptible
|
||||
|
||||
### Cost Optimization Strategies
|
||||
|
||||
1. Use reserved/committed capacity (30-70% savings)
|
||||
2. Leverage spot/preemptible instances
|
||||
3. Right-size resources
|
||||
4. Use serverless for variable workloads
|
||||
5. Optimize data transfer costs
|
||||
6. Implement lifecycle policies
|
||||
7. Use cost allocation tags
|
||||
8. Monitor with cloud cost tools
|
||||
|
||||
**Reference:** See `references/multi-cloud-patterns.md`
|
||||
|
||||
## Migration Strategy
|
||||
|
||||
### Phase 1: Assessment
|
||||
- Inventory current infrastructure
|
||||
- Identify dependencies
|
||||
- Assess cloud compatibility
|
||||
- Estimate costs
|
||||
|
||||
### Phase 2: Pilot
|
||||
- Select pilot workload
|
||||
- Implement in target cloud
|
||||
- Test thoroughly
|
||||
- Document learnings
|
||||
|
||||
### Phase 3: Migration
|
||||
- Migrate workloads incrementally
|
||||
- Maintain dual-run period
|
||||
- Monitor performance
|
||||
- Validate functionality
|
||||
|
||||
### Phase 4: Optimization
|
||||
- Right-size resources
|
||||
- Implement cloud-native services
|
||||
- Optimize costs
|
||||
- Enhance security
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. **Use infrastructure as code** (Terraform/OpenTofu)
|
||||
2. **Implement CI/CD pipelines** for deployments
|
||||
3. **Design for failure** across clouds
|
||||
4. **Use managed services** when possible
|
||||
5. **Implement comprehensive monitoring**
|
||||
6. **Automate cost optimization**
|
||||
7. **Follow security best practices**
|
||||
8. **Document cloud-specific configurations**
|
||||
9. **Test disaster recovery** procedures
|
||||
10. **Train teams** on multiple clouds
|
||||
|
||||
## Reference Files
|
||||
|
||||
- `references/service-comparison.md` - Complete service comparison
|
||||
- `references/multi-cloud-patterns.md` - Architecture patterns
|
||||
|
||||
## Related Skills
|
||||
|
||||
- `terraform-module-library` - For IaC implementation
|
||||
- `cost-optimization` - For cost management
|
||||
- `hybrid-cloud-networking` - For connectivity
|
||||
Reference in New Issue
Block a user