RE
refit
Use Refit to define type-safe REST clients in .NET as C# interfaces backed by HttpClient — covering interface definition (HTTP verb attributes, parameter binding, return types), DI registration with AddRefitClient, DelegatingHandler pipelines for auth/headers/logging, error handling with IApiRespons
Install
mkdir -p .claude/skills/refit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14276" && unzip -o skill.zip -d .claude/skills/refit && rm skill.zipInstalls to .claude/skills/refit
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use Refit to define type-safe REST clients in .NET as C# interfaces backed by HttpClient — covering interface definition (HTTP verb attributes, parameter binding, return types), DI registration with AddRefitClient, DelegatingHandler pipelines for auth/headers/logging, error handling with IApiResponse, RefitSettings, and multipart uploads. Trigger whenever the user writes, reviews, or asks about Refit clients, REST API interfaces, AddRefitClient, IApiResponse, ApiException, DelegatingHandler for HTTP, typed HTTP clients, RestService.For, or consuming HTTP APIs in .NET — even if they don't mention "Refit" by name. Always prefer this skill over guessing; Refit's attribute model, IApiResponse vs throws-by-default behavior, handler chain ordering, and scoped-client lifetime rules all have non-obvious failure modes that are easy to get wrong.848 charsno explicit “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
About this skill
Refit
Refit turns a C# interface you annotate with HTTP verb attributes into a working client backed by HttpClient. You write the contract; Refit generates the implementation at compile time (source generator) or runtime.
NuGet packages
Refit— core (always required)Refit.HttpClientFactory—AddRefitClient<T>()DI integration (add for ASP.NET Core / DI apps)
Quick reference
| Topic | See |
|---|---|
| HTTP verbs, parameter binding, return types, headers | interface-design.md |
DI registration, AddRefitClient, RefitSettings, scoped clients | di-registration.md |
| Auth handlers, Bearer tokens, per-request and static headers | authentication.md |
IApiResponse, ApiException, non-throwing error handling | error-handling.md |
The golden path
// 1. Define the interface
public interface IProductsClient
{
[Get("/api/products/{id}")]
Task<ProductDto> GetProductAsync(Guid id, CancellationToken cancellationToken = default);
[Post("/api/products")]
Task<IApiResponse<ProductDto>> CreateProductAsync([Body] CreateProductRequest body, CancellationToken cancellationToken = default);
}
// 2. Register with DI
services.AddRefitClient<IProductsClient>()
.ConfigureHttpClient(c => c.BaseAddress = new Uri("https://api.example.com"))
.AddHttpMessageHandler<AuthHandler>()
.AddStandardResilienceHandler();
// 3. Use via injection
public class ProductsPage(IProductsClient client)
{
async Task LoadAsync()
{
var product = await client.GetProductAsync(id);
}
}
Critical rules
- Always include
CancellationToken cancellationToken = defaultas the last parameter on every method. - Handler chain order matters: the first
AddHttpMessageHandlercall is outermost (executes first on send, last on receive). Typical order: Resilience → Auth → Correlation → Network. - Never register scoped DelegatingHandlers as singletons — they'll capture scoped services and cause stale state. Register handlers as
AddTransient. IApiResponse<T>suppresses throwing on non-2xx; rawTask<T>throwsApiException. Choose at the interface level per method.InnerHandlermust benullwhen registering handlers via DI (AddHttpMessageHandler); assign it only when constructing manually withRestService.For<T>.