lambdakit-ts
A TypeScript (TS) toolkit for bootstrapping AWS Lambda functions with production-ready best practices.
What this skill does
# LambdaKit TS
Bootstrap a new TypeScript AWS Lambda using the instructions below.
If the desired event source is not specified, create a Lambda with API Gateway as the event source.
Start with:
1. If a name is not specified, generate an interactive prompt and ask the user what `what should the lambda be called?`, and pre-populate it with the name of the current directory in kebab-case.
2. Before proceeding further, present the user with an interactive prompt: `The Lambda will be created at ${path}. Please confirm`
Then give the user 2 options:
- Yes — proceed with creating the Lambda at this path
- Enter a directory name — a new subdirectory with this name will be created in the current directory
If a new directory name is entered, use this value in kebab-case, and create the lambda in the new directory.
3. create package.json with `npm init -y`
4. install dev dependencies `npm install -D @types/aws-lambda @types/node esbuild typescript prettier @eslint/js eslint-plugin-prettier eslint-plugin-check-file eslint-config-prettier @typescript-eslint/parser @typescript-eslint/eslint-plugin`
5. install runtime dependencies `npm install @aws-lambda-powertools/logger @middy/core`
6. run `mkdir -p src/functions src/interfaces` to create the directories
7. copy the provided `assets/tsconfig.json` file
8. copy the provided `assets/eslint.config.mjs` file
9. copy the provided `assets/index.ts` file and change the `serviceName` value according to the provided name or directory name
10. copy the provided `assets/local-invoke.ts` file and change the `functionName` value according to the provided name or directory name
11. copy the provided `assets/greet.ts` file and copy it to the `src/functions/` directory
12. copy the provided `build.sh` file and run `chmod + x` to assign execute permissions
13. copy the provided `.prettierrc` file
14. copy the provided `.gitignore` file
15. add scripts to `package.json` from the section `add package.json scripts` below
16. when done, add instructions to the output as per the `Final Instructions` section below
## Code Organization Principles
### add package.json scripts
add the following scripts in `package.json`:
```json
{
"scripts": {
"typecheck": "tsc --noEmit",
"build": "bash build.sh",
"invoke:local": "npx tsx src/local-invoke.ts",
"prettier": "prettier --check '**/*.{ts,json}'",
"prettier:fix": "prettier --write '**/*.{ts,json}'",
"lint": "eslint . --ext .ts",
"lint:fix": "eslint . --ext .ts --fix"
}
}
```
### Final Instructions
- To build the project, run `npm run build`
- To autoformat using prettier, run `npm run prettier:fix`
- To autofix lint issues, run `npm run lint:fix`
## Best Practices
1. Use async/await syntax instead of promises
2. Use import statements instead of require where possible
3. Use aliased imports as defined in `tsconfig.json`
4. Use Middy middleware for cross-cutting concerns
5. Use AWS Lambda Powertools for structured logging
6. Always include proper error handling with appropriate logging
7. When creating other functions, pass the instance of the logger to those functions so that the context and properties can be persisted across logs
8. Use the Single Responsibility Principle (SRP) to rnsure good separation of concerns.
9. SRP: Ensure a single export per file
10. SRP: Always create separate files for functions and store functions in `src/functions`
11. SRP: Prefer interfaces over types and store interfaces in `src/interfaces`
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.