skills.rest
erikshafer
erikshaferCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

wolverine-http-handlers

Create and review Wolverine HTTP endpoints with OpenAPI inference in CritterCab.

Updated Apr 21, 2026
Search Tags:#openapi#http endpoints#wolverine#http handlers#crittercab
One-click install
npx skills add https://github.com/erikshafer/CritterCab --skill wolverine-http-handlers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wolverine-http-handlers
Source: https://github.com/erikshafer/CritterCab/tree/main/docs/skills/wolverine-http-handlers
Command: npx skills add https://github.com/erikshafer/CritterCab --skill wolverine-http-handlers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers master HTTP endpoint patterns in the CritterCab architecture, using Wolverine's HTTP integration.

Core Features & Use Cases

  • HTTP Endpoint Patterns: Offers guidance on route binding, mixed route+body shapes, OpenAPI inference, and silent-failure footguns.
  • Use Case: When creating or reviewing HTTP endpoints in CritterCab, this Skill provides best practices and anti-patterns to avoid common pitfalls.

Quick Start

Load the wolverine-http-handlers skill and apply it when authoring or reviewing any Wolverine HTTP endpoint.

Frequently Asked Questions about wolverine-http-handlers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create HTTP endpoints in Wolverine?▼

Wolverine HTTP endpoints require understanding route binding patterns, mixed route and body shapes, and OpenAPI inference. Following these endpoint patterns prevents common silent-failure footguns during development.

How does OpenAPI inference work with Wolverine HTTP handlers?▼

OpenAPI inference in Wolverine HTTP handlers generates API documentation automatically from your route binding and body shape patterns. Structuring endpoints correctly ensures accurate inference without manual schema configuration.

What are common pitfalls when building HTTP endpoints with Wolverine?▼

Common Wolverine HTTP endpoint pitfalls include silent failure footguns caused by improper route binding and mixed route and body shapes. Reviewing established anti-patterns helps developers avoid these architectural issues.

Do I need to understand the CritterCab architecture to use Wolverine HTTP handlers?▼

Yes, using Wolverine HTTP handlers effectively requires basic knowledge of the CritterCab architecture and Wolverine HTTP integration. This prerequisite understanding is necessary to apply endpoint patterns correctly.

What is the best way to structure mixed route and body shapes in Wolverine?▼

The best way to structure mixed route and body shapes in Wolverine is to follow established endpoint patterns supporting both route binding and body deserialization. This ensures correct OpenAPI inference and avoids silent failures.

Related Skills

Explore More Software Engineering Skills→
erikshafererikshafer

polecat-event-sourcing

Implement event sourcing and document database management with Polecat in CritterCab.

Community
Advanced
0xHoneyJar0xHoneyJar

defining-actions

Generate JSON Schemas and OpenAPI documentation for x402 API endpoints.

Official
Intermediate
rudironsonirudironsoni

dotnet-minimal-apis

Develop ASP.NET Core Minimal APIs with lambda-based endpoints and TypedResults.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

openapi-scalar

Generate OpenAPI specifications and Scalar UI documentation for .NET 9+ applications.

Community
Intermediate