The conventions for this Lambda function's contract - function names, one request record in and one response record out, offset paging with NextOffset, errors as Lambda function errors, the HTTP API routes and their problem details, and what is left to API Gateway or IAM. Use when naming a function, shaping its request or response, or deciding how a failure reaches the caller.
How to change the data model and add an EF Core migration for the SQLite database, including the namespace, folder and naming fixes the tools need. Use when adding a column, table, index or relationship.
How to put an Application use case on a Lambda function - a [LambdaFunction] method on Handler that sends the request through Mediator with a cancellation token from the remaining time, request and response records, the Mapperly mapper, the source-generated serializer context, the generated CloudFormation template and tests. Use when adding or changing a function in this Lambda template.
How this Lambda function reads and writes JSON - the assembly-level LambdaFunctionJsonSerializer with camelCase names, the source-generated LambdaFunctionJsonSerializerContext, which types it must list, and how JSON is shaped. Use when adding a request or response type, changing how JSON looks, or when a value serialises differently than expected.
How to try the function by hand with the Lambda runtime interface emulator in the AWS base image - docker compose, invoking with curl, choosing another function, sending an API Gateway HTTP API event, and reading errors. Use when you want to call the function as Lambda would, without deploying it.
How this Lambda function is tested end to end - calling Handler methods with a TestLambdaContext, services from Startup with a private in-memory database per test class, the generated handler classes, the HTTP API functions, and asserting exceptions. Use when writing or fixing a test in tests/Presentation.Tests.Integration.
How logging works with Serilog - registration with AddSerilog, configuration from appsettings, sinks per environment, logs over OTLP, the enrichers and properties on every event, the request log, the LoggingBehaviour, who logs an unexpected exception, levels, and source-generated log messages. Use when adding a log line, changing log configuration or levels, adding a property, or looking for where logs go.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.