- Home
- Skills
- Zxkane
- Aws Skills
- Aws Cdk Development
aws-cdk-development_skill
- Shell
101
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill zxkane/aws-skills --skill aws-cdk-development- SKILL.md10.1 KB
Overview
This skill is an AWS CDK development expert for building and validating cloud infrastructure with TypeScript and Python. It guides CDK app structure, construct patterns, stack composition, and deployment workflows while integrating MCP servers for up-to-date AWS and CDK guidance. Use this skill to design, validate, synthesize, and deploy reliable CDK stacks.
How this skill works
The skill inspects CDK apps, construct choices, and stack configurations and recommends patterns, APIs, and deployment steps. It leverages an AWS Documentation MCP to verify service features and regional availability and a CDK MCP server for construct-level recommendations and best practices. When MCP tools are unavailable, it helps configure MCP options or prompts for the preferred verification path.
When to use it
- Creating new CDK stacks or constructing reusable constructs
- Refactoring or modularizing existing CDK infrastructure
- Implementing Lambda functions and packaging strategies in CDK
- Verifying service availability, quotas, or API changes before coding
- Running pre-deployment validation, synthesis, and CI checks
Best practices
- Avoid explicitly specifying optional resource names; let CDK generate unique names for reusability and parallel deployments
- Use language-specific constructs (NodejsFunction, PythonFunction) to automate bundling and dependency management
- Apply multi-layer validation: IDE/synthesis checks (cdk-nag), synthesis-time validation, and pre-commit tests
- Check AWS Documentation MCP for regional availability and API changes before implementation
- Organize stacks with clear construct boundaries and nested stacks for complex apps; export values only when needed
Example use cases
- Recommend the appropriate CDK construct for an API Gateway + Lambda integration
- Validate that a new AWS feature is available in the target region before coding
- Create a pre-deploy pipeline that runs cdk synth, cdk-nag checks, builds, and tests
- Refactor a monolithic stack into logical constructs with nested stacks and exported values
- Help configure Lambda bundling and dependency handling for TypeScript or Python functions
FAQ
Yes. I use AWS MCP servers for current service details and CDK guidance. If MCP is unavailable, I’ll guide you to configure the AWS MCP or choose the documentation-only MCP option.
Should I ever name resources explicitly in CDK?
Avoid naming optional resources. Explicit names reduce reusability and cause collisions. Use explicit names only when an external system requires a fixed name and document why.