jeff-skill-aws-cdk-project

Structure your AWS CDK TypeScript project by placing a single CDK app in a dedicated cdk/ directory with bin, lib, and test subdirectories. This opinionated layout enforces per-construct file organization and environment management for repeatable builds.

The best way to manage environment variables in an AWS CDK project is by standardizing through cdk/.env and cdk/.env.example files. This approach keeps environment configurations consistent and documented within the cdk directory structure.

Yes, this AWS CDK project setup requires Vitest for unit testing. It mandates a dedicated test directory with coverage goals to ensure repeatable builds and maintain infrastructure code quality audits.

No, you cannot maintain multiple CDK apps with this structure. It enforces a canonical repository layout designed for a single CDK app at the repo root inside a cdk/ directory with a single stack and per-construct files.

Organize CDK constructs and stacks by keeping the app entrypoint in cdk/bin and defining a single stack with per-construct files in cdk/lib. This sample structure provides guidance for maintaining clear separation of infrastructure components.

Use an opinionated AWS CDK project layout to enforce strict dependency and file structure conventions beyond default initialization. It standardizes environment configuration, testing, and workflows to enable repeatable synth, deploy, and CI integration processes.