cdk-infrastructure

Standardize AWS CDK infrastructure with VPC, ECS, Lambda, DynamoDB, S3, and IAM patterns.

16|27|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/Boise-State-Development/agentcore-public-stack --skill cdk-infrastructure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdk-infrastructure
Source: https://github.com/Boise-State-Development/agentcore-public-stack/tree/main/.claude/skills/cdk-infrastructure
Command: npx skills add https://github.com/Boise-State-Development/agentcore-public-stack --skill cdk-infrastructure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AWS CDK infrastructure development often suffers from fragmentation across projects; this Skill consolidates patterns for scalable, maintainable infrastructure using TypeScript and CDK, including naming conventions, cross-stack references, and deployment guidance.

Core Features & Use Cases

  • Standardized project layouts for infrastructure (infrastructure/bin, infrastructure/lib) and configuration patterns.
  • Cross-stack reference strategies via SSM, consistent naming conventions, and reusable patterns for common resources (VPC, ECS/Fargate, Lambda, DynamoDB, S3, IAM).
  • Real-world use cases and onboarding guidance for teams adopting CDK best practices.

Quick Start

Refactor your CDK projects to adopt the folder structure, naming, and cross-stack references described in this Skill.

Frequently Asked Questions about cdk-infrastructure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best practices for AWS CDK cross-stack references in TypeScript?

AWS CDK cross-stack references are standardized using SSM parameters to securely share resources across stacks. This pattern avoids direct stack dependencies and maintains scalable infrastructure configurations for resources like VPCs and DynamoDB.

How do I structure a scalable AWS CDK infrastructure project?

A scalable AWS CDK project structure uses infrastructure/bin for app entry points and infrastructure/lib for construct definitions. This layout enforces consistent naming conventions and reusable patterns for maintainable infrastructure.

Does this AWS CDK skill provide reusable patterns for ECS and Lambda?

Yes, the skill provides reusable configuration patterns for ECS/Fargate and Lambda. It enforces standardized naming conventions and deployment guidance to ensure consistent infrastructure provisioning across your AWS CDK stacks.

How do I standardize naming conventions across multiple AWS CDK stacks?

Standardize naming conventions across AWS CDK stacks by applying consistent configuration patterns for VPC, ECS, Lambda, DynamoDB, S3, and IAM. This ensures maintainable infrastructure and reliable cross-stack references.

Can I use these AWS CDK patterns for refactoring existing infrastructure code?

Yes, you can refactor existing AWS CDK projects to adopt the standardized folder structure, naming conventions, and cross-stack references. This streamlines fragmented infrastructure into maintainable patterns.