pywf AWS Lambda Project Conventions

VerifiedSafe

Reference for pywf AWS Lambda template conventions: code, configuration, CDK, deployment, and tests. Consult before making changes or deploying.

Sby Skills Guide Bot
DevOpsAdvanced
11/6/2026
Claude Code
#aws-lambda#aws-cdk#project-conventions#deployment#infrastructure-as-code

Recommended for

Automated summary

Documents the conventions of the pywf AWS Lambda project template v0.2.1, from Lambda handlers and configuration through CDK stacks and deployment.

Strengths

  • Organized as one focused reference per topic, with guidance on which file to read for a given change.
  • Establishes precedence rules for stack layout and defers library APIs to dedicated skills.
  • Covers the full path from Lambda code and tests to SSM config, CDK stacks, and deploy recipes.
  • Pins links to template version 0.2.1 and tells the user to prefer the actual project when it differs.

Limitations

  • Only relevant to projects generated from this specific pywf template and its dependencies.
  • Depends on several external skills and linked upstream repositories for complete API details.
  • Assumes familiarity with AWS Lambda and CDK; it is a conventions reference, not a tutorial.
When to use it

Use it before modifying Lambda code, config, dependencies, CDK stacks, mise tasks, or tests in a pywf-generated project, or before deploying.

When not to use it

Do not use it for unrelated AWS Lambda projects or as a general AWS CDK tutorial.

Security analysis

Safe
Quality score78/100

The skill is a documentation index describing conventions for a Lambda/CDK project template. It declares no tools and contains no executable instructions, destructive commands, credential handling, or network/exfiltration behavior. External GitHub references are informational only.

No concerns found

How this analysis is made

Examples

Add a config field
I need to add a new config field for a Lambda queue URL in this pywf project. Which reference should I follow, and which files need to change?
Review CDK stack changes
Review my CDK stack changes against the pywf AWS Lambda template conventions, especially StackCtxEnum and StackEnum usage and the synth-only tests.
Prepare a deployment
I'm about to deploy this Lambda function. Walk me through the pywf deploy flow and the change recipes for the source asset and the layer.

name: pywf-aws-lbd-base description: "Conventions of the pywf AWS Lambda project template (v0.2.1), one topic per reference: runtime, environment, the config model, names, and loading, the boto session, the one singleton; then the Lambda code (handlers, dependencies, tests), the devops environment, the config in SSM; the CDK part (layout, StackCtxEnum / StackEnum, stack exports, generated mise tasks, synth-only tests, change recipes); and shipping (source asset, layer, stacks, deploy flow, Lambda change recipes). Load it before changing a Lambda function, a dependency, config, credentials, a stack, a mise task, or a test in such a project, before deploying, or for a question about how it is organized."

The conventions of a multi-environment AWS Lambda project generated from the pywf AWS Lambda template, which extends the pywf AWS CDK template. A generated project already follows all of them; this skill says what they are, so changes keep them.

Version

Template 0.2.1, the version in the seed repo's pyproject.toml. Every link points to the git tag of that version: MacHu-GWU/cookiecutter_aws_lbd_demo-project at 0.2.1. If the project in front of you differs from the linked files, the project wins; tell the user.

Precedence

For the layout of stacks, follow references/15-cdk-stack-enums.md, not the multi-stack best practice of cdk_mate. For a library's API, use its own skill: pypi-cdk_mate, pypi-aws_lbd_art_builder_uv and pypi-aws_lbd_art_builder_core (layer and source build), pypi-simple_aws_ssm_parameter_store (config deploy), pypi-boto_session_manager, pypi-s3pathlib; and the aws-cdk-cli-ref skill for a cdk CLI option.

References

00 is how this skill is written. 01–08 are general and never mention Lambda or CDK. Then, from code to deployment: 09–13 the Lambda code, the devops environment, and the config in SSM (lbd-); 14–19 the CDK part (cdk-); 20–24 shipping the functions (lbd-). For a question, read only the file that covers it.

<!-- BEGIN references index: generated by scripts/update_skill_index.py, do not edit by hand -->
  • Authoring This Skill (references/00-authoring.md): Read before adding, editing, or renaming any file of this skill, or copying it to another template.
  • Project Layout (references/01-project-layout.md): Read when looking for where a general concern lives, or deciding where a new one goes.
  • Runtime (references/02-runtime.md): Read when code must behave differently on a developer machine and in CI, or when adding a runtime.
  • Environment (references/03-env.md): Read when code depends on the environment, when switching environments, or when adding one.
  • Config Model (references/04-config-model.md): Read before adding or changing a config field, or when deciding whether a value belongs in the config.
  • Names in the Config (references/05-config-names.md): Read before naming any AWS resource, or before writing a name, ARN, or URL as a string anywhere else.
  • Boto Session (references/06-boto-session.md): Read when code needs AWS credentials or a boto3 client, when setting up profiles, or when credentials go to the wrong account.
  • Config Loading (references/07-config-load.md): Read when loading the config, adding or changing a config file, adding a config source, or when a config value is missing.
  • The one Singleton (references/08-one-singleton.md): Read before adding a project-level object, a client, or anything environment specific, or when code imports a singleton from somewhere other than one.
  • Lambda Handlers (references/09-lbd-handlers.md): Read before writing, renaming, or reviewing a Lambda function.
  • Lambda Dependencies and Imports (references/10-lbd-dependencies.md): Read before adding a dependency, importing a library, or reading the package version.
  • Lambda Tests (references/11-lbd-tests.md): Read when writing or fixing a test of a Lambda function.
  • The devops Environment (references/12-lbd-devops-env.md): Read before code or a task touches the devops account, or when setting up a machine to deploy.
  • Lambda Config in SSM (references/13-lbd-config-ssm.md): Read before adding a config field a function reads, changing how a function loads its config, or running a config task.
  • CDK Layout (references/14-cdk-layout.md): Read before writing or reviewing a stack, or when deciding where CDK code goes.
  • Stack Enums (references/15-cdk-stack-enums.md): Read before adding, removing, or reordering a stack, or wiring one stack to another.
  • Stack Exports (references/16-cdk-stack-exports.md): Read before adding or changing a stack output, or when another project needs a stack's values.
  • CDK mise Tasks (references/17-cdk-mise-tasks.md): Read before running any cdk command or task, after changing the stacks or environments, or when editing mise.toml.
  • CDK Tests (references/18-cdk-tests.md): Read when writing or fixing a CDK test.
  • CDK Change Recipes (references/19-cdk-change-recipes.md): Read before adding or removing a stack, a resource, an output, a stack dependency, or an environment, or when checking that such a change is complete.
  • Lambda Source Asset (references/20-lbd-source-asset.md): Read before changing which files are deployed, how the source is built, or when a deploy updates a function that did not change.
  • Lambda Layer (references/21-lbd-layer.md): Read before building, publishing, granting, pinning, or deleting a layer version, or when a deploy fails on a layer.
  • Lambda Stacks (references/22-lbd-stacks.md): Read before changing a Lambda function's infrastructure, its permissions, or its triggers.
  • Lambda Deploy Flow (references/23-lbd-deploy-flow.md): Read before deploying, or when deciding which task a change needs.
  • Lambda Change Recipes (references/24-lbd-change-recipes.md): Read before adding or removing a Lambda function, a trigger, a permission, a runtime dependency, a config field a function reads, or a workload environment, or when checking that such a change is complete.
<!-- END references index -->

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pywf-aws-lambda-project-conventions-mvj1oc5r/download' --output '.skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r/SKILL.md.part' && mv '.skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r/SKILL.md.part' '.skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r/SKILL.md' && test -s '.skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pywf-aws-lbd-base' && cp -R '.skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r' '.claude/skills/pywf-aws-lbd-base'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r'

openskills read 'pywf-aws-lambda-project-conventions-mvj1oc5r'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/pywf-aws-lambda-project-conventions-mvj1oc5r/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills