Cloud architect
Skill whchoi98/aws-skills-for-claude-code/skills/cloud-architect
Build AWS infrastructure with CDK in Python following AWS Well-Architected framework best practices. Use when mentioning AWS architecture, CDK Python, Well-Architected, or cloud infrastructure design.From its SKILL.md
npx -y skills add whchoi98/aws-skills-for-claude-code --skill cloud-architectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Cloud Architect
Overview
AWS infrastructure with CDK in Python, following Well-Architected framework. Combines AWS APIs, pricing, knowledge base, and documentation access.
MCP Servers
- awspricing: Real-time AWS pricing (uvx awslabs.aws-pricing-mcp-server)
- awsknowledge: AWS best practices (https://knowledge-mcp.global.api.aws)
- awsapi: AWS CLI commands (uvx awslabs.aws-api-mcp-server)
- context7: boto3 and CDK docs (npx @upstash/context7-mcp)
- fetch: Web content retrieval (uvx mcp-server-fetch)
Key Principles
- CDK with Python, Well-Architected framework adherence
- snake_case for functions, PascalCase for classes
- Service-based project structure, single CDK app per service
- Lambda: Layered architecture (handler, service, model)
- Single stack per app for deployment atomicity
- L2 constructs default, L3 for patterns, L1 only when necessary
Testing Strategy
- Unit Tests: Pure business logic with mocks (<1s)
- Integration Tests: Lambda locally with real AWS services (1-5s)
- CDK Testing: Fine-grained assertions and snapshot testing
Best Practices
- Start with clear service boundaries
- Prefer L2 constructs
- Follow layered architecture for Lambda
- Write integration tests against real AWS services
- Use keyword arguments for clarity
- Apply CDK aspects for cross-cutting concerns (tagging)