How Hot Chocolate DataLoaders batch the reviews asked for by every movie or author in a response into one Application query - source-generated DataLoaders, batching under the paging limit, and using them from a type. Use when a field on a list item needs data from another query, or when a query makes one database call per item.
1312d agoReviewMountCreate a free account to mount
How to put an Application use case on the Hot Chocolate GraphQL schema - static partial query and mutation classes, source-generated types, mutation conventions with typed errors, Relay connections, authorization, XML comments as schema descriptions, and tests. Use when adding or changing a query, mutation, field or type in this GraphQL API.
1312d agoReviewMountCreate a free account to mount
How to try the GraphQL API by hand in Nitro, the GraphQL IDE served embedded at /graphql - where it runs, sending a token when authentication is on, and what to check before calling a schema change done. Use when you want to explore the schema, run a query by hand, or see the descriptions clients see.
How this GraphQL API is tested end to end with WebApplicationFactory - the GraphQLApplication host, one app and database per test class, sending queries and mutations over HTTP, reading data and errors with typed test models, the schema snapshot, and testing with authentication on. Use when writing or fixing a test in tests/Presentation.Tests.Integration.
1312d agoReviewMountCreate a free account to mount
How the GraphQL schema is pinned by a snapshot test - schema.graphql in the integration tests, comparing it with /graphql?sdl, and updating it on purpose when the schema changes. Use when the schema snapshot test fails, or after adding or changing a query, mutation, type, field or description.
1312d agoReviewMountCreate a free account to mount
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.
The REST conventions for this API - plural lowercase routes, status codes per operation, problem details for errors, JSON casing and paging parameters. Use when choosing a route, a status code or a response shape.
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 Web API controller action - controllers on ApiControllerBase, the injected ISender, ActionResult return types, ProducesResponseType metadata, XML docs for Scalar and integration tests. Use when adding or changing an action in this Web API.
How this Web API reads and writes JSON with System.Text.Json - the one set of options in UseApiDefaults, applied to both the controllers and the HTTP JSON options, and how tests use the same options. Use when adding a request or response type, changing how JSON looks, or when a value serialises differently than expected.
How this Web API builds its OpenAPI document and serves the Scalar API reference - AddOpenApi, the document and operation transformers, the bearer scheme when authentication is on, the Scalar options, and the tests that read the generated document. Use when changing the API description, tags, security scheme, Scalar settings, or when the API reference looks wrong.
How this Web API is tested end to end with WebApplicationFactory - the WebApiApplication host, a private database per test class, overriding settings and services, the JSON helper, asserting problem details, and testing with authentication on and off. 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.
How this MCP server's tools, resources and prompts are named and shaped - snake_case noun_verb tool names, titles and annotations, structured results with nextOffset paging, error results versus protocol errors, and keeping the server instructions current. Use when naming or changing a tool, resource or prompt, deciding what a tool returns, or changing how errors reach the model.
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 the MCP server as a tool, resource or prompt - partial static methods with McpServer attributes, XML comments that become the descriptions, result models, completions and tests. Use when adding or changing a tool, resource or prompt on this MCP server.
How this MCP server reads tool arguments and writes results with System.Text.Json - McpSerializer.Options built on the SDK defaults, the source-generated AppJsonSerializerContext and which types it lists, and how tests use the same options. Use when adding a result model, changing how JSON looks, or when a value serialises differently than expected.
How to try the MCP server by hand with the official MCP Inspector that docker compose starts beside it - where it runs, how it connects, and what to check before calling a tool, resource or prompt change done. Use when you want to see tools, resources or prompts as a client sees them, or debug what the model receives.
How this MCP server is tested end to end - the ModelContextProtocolApplication host, BaseToolTests with a real MCP client over HTTP, calling tools, reading resources and getting prompts, asserting error results and protocol errors, and testing with authentication on. 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.