mds-axum-integration

Standardizes Axum integration patterns for backend contracts, routing, request extraction, and SSE endpoints.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/eboody/eran.codes --skill mds-axum-integration
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: mds-axum-integration
Source: https://github.com/eboody/eran.codes/tree/main/.codex/skills/mds-axum-integration
Command: npx skills add https://github.com/eboody/eran.codes --skill mds-axum-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for consistent and standardized approaches to integrating with the Axum web framework, ensuring clarity in backend contracts, routing, request extraction, and Server-Sent Events (SSE) transport.

Core Features & Use Cases

  • Routing Standardization: Defines patterns for setting up Axum routers and handling method-specific routes.
  • Extractor Usage: Provides guidance on effectively using Axum's extractors for request data.
  • SSE Endpoints: Details patterns for implementing Server-Sent Events for real-time data streaming.
  • Response Mapping: Offers strategies for mapping application responses to HTTP responses.
  • Use Case: When building new API endpoints in the project, consult this Skill to ensure routing, data extraction, and SSE implementations align with established project conventions.

Quick Start

Refer to this skill before defining new backend contracts and routing configurations in Axum.

Frequently Asked Questions about mds-axum-integration

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

FAQPage Schema
How do I standardize Axum routing and request extraction patterns?โ–ผ

Standardize Axum routing and request extraction by applying established conventions for method-specific routes and data extractors. This ensures backend contracts remain maintainable and consistent across new API endpoints.

What is the best way to implement Server-Sent Events in an Axum backend?โ–ผ

Implementing Server-Sent Events in an Axum backend requires following specific SSE endpoint patterns for real-time data streaming. This approach standardizes real-time communication transport within the project.

How does Axum handle mapping application responses to HTTP responses?โ–ผ

Mapping application responses to HTTP responses in Axum involves applying specific response mapping strategies. This ensures backend contract clarity and consistent HTTP response formatting across routing configurations.

Can I use Axum extractors for managing incoming request data?โ–ผ

Axum extractors can be used for managing incoming request data by adhering to established project conventions. This provides guidance on effectively handling request data extraction for new API endpoints.

When do I need to consult Axum integration conventions for backend contracts?โ–ผ

You need to consult Axum integration conventions when defining new backend contracts, routing configurations, or SSE endpoints. This ensures routing, data extraction, and real-time implementations align with project standards.