AWS CDK Naming Conventions FAQs

Question 1

Why does this skill prefer types over interfaces?

Accepted Answer

This skill promotes type-driven development, where type declarations are preferred for their consistency and better integration with complex AWS CDK construct definitions.

Question 2

What is the recommended function naming pattern?

Accepted Answer

The skill enforces a 'verbNoun' pattern in camelCase, such as 'createBucket' or 'getVpcConfig', to improve code readability and intent.

Question 3

How does it prevent AWS resource naming collisions?

Accepted Answer

It implements a specific pattern that appends the environment name and region to resource IDs, such as 'bucket-dev-use1', ensuring uniqueness across multi-region deployments.

Question 4

Can this be used for non-AWS TypeScript projects?

Accepted Answer

While optimized for AWS CDK and infrastructure-as-code, its type-driven conventions and export patterns are applicable to any modern TypeScript project.

Question 5

Does this skill help with file organization?

Accepted Answer

Yes, it provides specific kebab-case naming rules for constructs, types, enums, and utility files to keep the repository organized and searchable.

AWS CDK Naming Conventions

Key Features

Use Cases

AWS CDK Naming Conventions

Key Features

Use Cases