cdkd: Skill for Claude Code

New Provider Scaffold

You are scaffolding a new SDK Provider for cdkd.

Input

The user provides an AWS resource type like AWS::SES::EmailIdentity.

Steps

1. Parse the resource type to determine:

   • Service name (e.g., SES)
   • Resource name (e.g., EmailIdentity)
   • AWS SDK client package (e.g., @aws-sdk/client-ses)
   • Provider file name (e.g., ses-email-identity-provider.ts)

2. Check if provider already exists in src/provisioning/providers/ and src/provisioning/register-providers.ts.

3. Read an existing provider as reference for the pattern. Use a simple one like src/provisioning/providers/ssm-parameter-provider.ts or src/provisioning/providers/logs-log-group-provider.ts.

4. Read the AWS SDK docs or infer the API calls needed:

   • CREATE: Which API creates this resource? What does it return (physical ID, attributes)?
   • UPDATE: Which API updates this resource?
   • DELETE: Which API deletes this resource?
   • getAttribute: Which attributes might be needed for Fn::GetAtt?
   • import: Which API verifies a resource exists by physical id (Get* / Describe* / Head*), and which List* + ListTags* (or equivalent) lookup-by-tag pair lets you find a resource by its aws:cdk:path tag? See "Import method" under step 5 — most providers follow the same shape.

5. Create the provider file at src/provisioning/providers/{service}-{resource}-provider.ts:

   • Import the AWS SDK client and commands
   • Implement ResourceProvider interface (create, update, delete, getAttribute, import)
   • Take clients from getAwsClients(), or build your own SDK client with ...ambientClientDefaults() (../../utils/ambient-client-defaults.js) spread FIRST — a bare awsClientDefaults() drops a library caller's explicit credentials and fails ambient-client-defaults-fence.test.ts (#3588)
   • Follow ESM import conventions (.js extension)
   • Return proper physicalId and attributes from create

   Import method — copy the shape from a similar provider rather than writing it from scratch: s3-bucket-provider.ts for a tag-ARRAY service, lambda-function-provider.ts for a tag-MAP one, kms-provider.ts for a service with no template name property. The shape is: resolve an explicit physical id first (resolveExplicitPhysicalId(input, '<NameField>'), i.e. the --resource override or Properties.<NameField>) and verify it with a Get / Head / Describe call; otherwise, with input.cdkPath present, walk the service's List* paginator, fetch tags per resource and match aws:cdk:path through matchesCdkPath (CDK_PATH_TAG in ../import-helpers.js).