AWS CDK Naming Conventions

About

This skill enforces a type-driven development approach for AWS CDK projects by providing strict naming conventions for types, functions, files, and cloud resources. It helps developers maintain a clean, professional codebase by favoring type declarations over interfaces, implementing environment-aware resource naming to avoid naming collisions across regions, and standardizing export patterns for better modularity in CDK construct libraries.

Key Features

• 6 GitHub stars
• Implements environment-based naming patterns to prevent AWS resource collisions
• Organizes project structure with kebab-case file naming conventions
• Standardizes naming cases for types, enums, functions, and variables
• Enforces type-driven development using type declarations instead of interfaces
• Promotes clean module exports using named export patterns

Use Cases

• Refactoring TypeScript infrastructure code to follow type-driven patterns
• Automating code reviews to ensure naming consistency across large CDK libraries
• Bootstrapping new AWS CDK projects with production-ready naming standards