| name | aws-cdk-development |
| description | AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python. Use when creating CDK stacks, defining CDK constructs, implementing infrastructure as code, or when the user mentions CDK, CloudFormation, IaC, cdk synth, cdk deploy, or wants to define AWS infrastructure programmatically. Covers CDK app structure, construct patterns, stack composition, and deployment workflows. |
| disable-model-invocation | false |
| context | fork |
| skills | ["aws-mcp-setup"] |
| allowed-tools | ["mcp__cdk__*","mcp__aws-mcp__*","mcp__awsdocs__*","Bash(cdk *)","Bash(npm *)","Bash(npx *)","Bash(aws cloudformation *)","Bash(aws sts get-caller-identity)"] |
| hooks | {"PreToolUse":[{"matcher":"Bash(cdk deploy*)","command":"aws sts get-caller-identity --query Account --output text","once":true}]} |
AWS CDK Development
This skill provides comprehensive guidance for developing AWS infrastructure using the Cloud Development Kit (CDK), with integrated MCP servers for accessing latest AWS knowledge and CDK utilities.
AWS Documentation Requirement
Always verify AWS facts using MCP tools (mcp__aws-mcp__* or mcp__*awsdocs*__*) before answering. The aws-mcp-setup dependency is auto-loaded — if MCP tools are unavailable, guide the user through that skill's setup flow.
Integrated MCP Servers
This skill includes the CDK MCP server automatically configured with the plugin:
AWS CDK MCP Server
When to use: For CDK-specific guidance and utilities
- Get CDK construct recommendations
- Retrieve CDK best practices
- Access CDK pattern suggestions
- Validate CDK configurations
- Get help with CDK-specific APIs
Important: Leverage this server for CDK construct guidance and advanced CDK operations.
When to Use This Skill
Use this skill when:
- Creating new CDK stacks or constructs
- Refactoring existing CDK infrastructure
- Implementing Lambda functions within CDK
- Following AWS CDK best practices
- Validating CDK stack configurations before deployment
- Verifying AWS service capabilities and regional availability
Core CDK Principles
Resource Naming
CRITICAL: Do NOT explicitly specify resource names when they are optional in CDK constructs.
Why: CDK-generated names enable:
- Reusable patterns: Deploy the same construct/pattern multiple times without conflicts
- Parallel deployments: Multiple stacks can deploy simultaneously in the same region
- Cleaner shared logic: Patterns and shared code can be initialized multiple times without name collision
- Stack isolation: Each stack gets uniquely identified resources automatically
Pattern: Let CDK generate unique names automatically using CloudFormation's naming mechanism.
new lambda.Function(this, , {
: ,
});
lambda.(, , {
});