From website-deployment
Creates the CDK TypeScript infrastructure project alongside the existing app. Use when setting up infrastructure or the CDK project.
npx claudepluginhub schuettc/website-deployment-plugin --plugin website-deploymentThis skill uses the workspace's default tool permissions.
You are creating the AWS CDK TypeScript project that defines the cloud infrastructure for the user's app.
Defines, validates, and deploys AWS infrastructure as code using AWS CDK TypeScript patterns for apps, stacks, constructs, serverless/VPC architectures, IAM/encryption, and CDK synth/diff/deploy.
Develops AWS infrastructure as code with CDK in TypeScript/Python. Guides stacks, constructs, patterns, deployments, and best practices using MCP tools and CDK CLI.
Authors, deploys, and troubleshoots AWS infrastructure using CDK in TypeScript or Python. Handles constructs, bootstrapping, synth/diff/deploy, CloudFormation errors, drift detection, resource imports, and safe refactoring.
Share bugs, ideas, or general feedback.
You are creating the AWS CDK TypeScript project that defines the cloud infrastructure for the user's app.
.migration/plan.md exists (from analyze step)Before creating the CDK project, verify the user's environment can support it. Catching these issues now saves confusing errors later.
Check Node.js version — Run node --version. CDK and TypeScript compilation require Node.js 18+. If older:
"CDK needs Node.js 18 or newer to work properly. You're on [version]. I'd recommend upgrading first — you can use nvm (nvm install 20) or download from nodejs.org."
Check AWS CLI is installed — Run aws --version. If not found:
"We'll need the AWS CLI to deploy later. You don't need it right now for scaffolding, but let's get it installed so you're ready. Here's how: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html"
Check AWS credentials — Run aws sts get-caller-identity. If it fails, don't block — just note it:
"AWS credentials aren't configured yet. That's fine for now — we can set those up before we deploy. Just keep in mind you'll need an AWS account and credentials before the deploy step."
If all checks pass (or the user acknowledges the warnings), proceed.
Show the proposed directory layout:
infrastructure/
├── bin/
│ └── app.ts ← CDK app entry point
├── lib/
│ └── api-stack.ts ← Lambda + API Gateway (next step)
├── lambda/
│ ├── handlers/ ← Lambda function code (next step)
│ └── shared/ ← Shared utilities
├── cdk.json
├── tsconfig.json
└── package.json
Ask the user:
infrastructure/ directoryinfrastructure/package.json with:
aws-cdk-lib and constructs as dependenciestypescript, ts-node, @types/node as dev dependenciescdk script pointing to npx cdkinfrastructure/cdk.json with standard CDK configinfrastructure/tsconfig.json with strict TypeScript configinfrastructure/bin/app.ts — CDK app entry point
infrastructure/lib/api-stack.ts — Empty stack skeleton (resources come in create-api)infrastructure/lambda/handlers/ and infrastructure/lambda/shared/ (empty, with .gitkeep)After creating files:
cd infrastructure && npm installcd infrastructure && npx cdk synth to verify the project compiles.migration/plan.md to mark scaffold as completeRemovalPolicy.DESTROY for development — explain what this means: "When you delete the stack, all resources get deleted too. For a learning project this is what you want — no leftover resources running up charges. For production, you'd use RETAIN so your database survives even if you accidentally delete the stack."env in the stack to use the user's preferred region