Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

axum-agents-scaffold

Estrelas0

Forks0

Atualizado20 de maio de 2026 às 09:40

Use when the request is to build a complete Axum service from scratch rather than to fix one isolated piece: "build me an Axum API", "scaffold a Rust web service", "set up a new Axum project", or when a half-built service needs the missing production layers identified and ordered. Prevents scaffolding in the wrong order (layering before routes, choosing a framework before pinning a version), shipping a service with no graceful shutdown or permissive CORS, and reinventing decisions that a dedicated skill in this package already owns. Covers the ordered core to syntax to impl to errors build sequence, a service-type classifier, the Cargo.toml dependency baseline, the minimal-to-production checklist, and which of the other 28 Axum skills owns each decision. Keywords: axum scaffold, build axum service, new axum project, axum project structure, scaffold rust web service, axum boilerplate, where do I start with axum, how do I structure an axum app, axum service checklist, axum production checklist, axum Cargo.toml,

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Impertio-Studio

Impertio-Studio/Axum-Claude-Skill-Package

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

4 arquivos

SKILL.md

readonly

Mais deste repositório

mesmo repositório

axum-agents-api-review

Impertio-Studio/Axum-Claude-Skill-Package

Use when auditing or reviewing existing Axum code, a diff, or a single file for correctness, reliability, and security defects, when a code review must flag Axum-specific mistakes, or when checking an Axum service against the package best practices before a merge or a deploy. Prevents shipping the 16 known Axum anti-patterns: 0.7 path syntax on 0.8, body extractor not last, non-IntoResponse handler returns, blocking calls in async handlers, per-request database pools, hardcoded secrets, missing graceful shutdown, and more. Covers a 10-category review checklist, a three-level severity model (blocker, warning, suggestion), the structured findings output format, and cross-references to all 28 other Axum skills that own each fix. Keywords: axum code review, audit axum, review checklist, anti-pattern, severity, blocker warning suggestion, structured findings, is my axum code correct, what is wrong with this handler, find bugs in axum code, check an axum service before deploy, how do I review axum code.

2026-05-200

axum-errors-extractor-rejections

Impertio-Studio/Axum-Claude-Skill-Package

Use when an Axum extractor fails and you need control over the HTTP error: customizing a Json/Path/Query rejection, returning a JSON error body instead of Axum's plain text, building a unified API error type, or upgrading 0.7 to 0.8 and Option extractors suddenly return 4xx. Prevents the non-exhaustive match compile error on rejection enums, inventing a wrong status code instead of reusing the rejection's own, and the silent 0.8 behavior change where Option no longer swallows malformed input. Covers the Rejection associated type, the axum::extract::rejection module, Result handler arguments, axum-extra WithRejection, derive(FromRequest) with rejection(...), hand-written custom extractors, and OptionalFromRequest. Keywords: axum rejection, extractor rejection, JsonRejection, PathRejection, QueryRejection, FormRejection, WithRejection, from_request rejection, derive FromRequest, OptionalFromRequest, non_exhaustive match error, body_text, status, customize extractor error, 400 instead of JSON, plain text error b

2026-05-200

axum-errors-handler-trait

Impertio-Studio/Axum-Claude-Skill-Package

Use when the compiler rejects an Axum handler with "the trait bound ... Handler<_, _> is not satisfied", when a function will not register on a route, when the error block names Handler with inference placeholders and lists unrelated impls as help, or when a handler argument or return type silently breaks compilation. Prevents passing a non-extractor argument, placing a body extractor before a parts extractor, returning a type that is not IntoResponse, writing a plain synchronous fn, and producing a !Send future by holding a guard across await. Covers the opaque E0277 trait-bound error, the five root causes, the axum-macros #[debug_handler] diagnostic macro and its macros feature, the state= override, and a symptom-to-cause-to-fix decision tree. Keywords: Handler is not satisfied, trait bound is not satisfied, E0277, debug_handler, axum-macros, macros feature, FromRequestParts, FromRequest, IntoResponse, blanket impl, !Send future, MutexGuard across await, handlers must be async functions, cannot find __axum_

2026-05-200

axum-errors-handling

Impertio-Studio/Axum-Claude-Skill-Package

Use when a handler must return an error, when adding a custom error type to an Axum service, when the question mark operator will not compile inside a handler, when anyhow::Error does not implement IntoResponse, or when a fallible tower middleware Service is rejected by the Router. Prevents calling unwrap or panic in handlers, returning a 500 where a 404 or 422 belongs, leaking internal error text to clients, and trying to impl IntoResponse for anyhow::Error directly against the orphan rule. Covers the infallible-handler model, the AppError enum with IntoResponse and From impls, thiserror versus anyhow, combining a thiserror enum with an anyhow catch-all variant, and HandleError / HandleErrorLayer for fallible tower::Service middleware. Keywords: IntoResponse, AppError, thiserror, anyhow, HandleError, HandleErrorLayer, Infallible, From impl, question mark operator, orphan rule, the trait IntoResponse is not implemented, anyhow does not implement IntoResponse, handler panics instead of returning a response, 50

2026-05-200

axum-impl-deployment

Impertio-Studio/Axum-Claude-Skill-Package

Use when deploying an Axum service to production, containerizing it with Docker, or when a SIGTERM from Docker, Kubernetes, or systemd kills in-flight requests on every restart or rolling deploy. Prevents dropped requests on shutdown, 1.5 GB images from single-stage builds, a full dependency recompile on every source change, and binaries that fail to start in a scratch container. Covers release builds, static musl binaries, multi-stage Dockerfiles, cargo-chef dependency-layer caching, with_graceful_shutdown plus a SIGINT/SIGTERM signal future, closing the DB pool on shutdown, and container hygiene (bind 0.0.0.0, env-var config, non-root user). Keywords: axum deployment, Docker, with_graceful_shutdown, shutdown_signal, SIGTERM, SIGINT, graceful shutdown, cargo-chef, multi-stage build, musl, x86_64-unknown-linux-musl, scratch image, distroless, TimeoutLayer, release build, requests dropped on deploy, container exits immediately, image too big, how do I dockerize axum, why does my binary not run in scratch.

2026-05-200

axum-impl-openapi

Impertio-Studio/Axum-Claude-Skill-Package

Use when generating an OpenAPI 3 specification and a Swagger UI for an Axum service: documenting handlers, describing request and response schemas, or serving an interactive API explorer. Prevents the hand-written spec that silently drifts from the real handlers, the route registered on the Router but missing from the spec, the wrong {param} versus :id path syntax, and pinning three independently-versioned crates to mismatched releases. Covers utoipa derive macros ToSchema, OpenApi, IntoParams, IntoResponses, ToResponse, the #[utoipa::path] attribute, utoipa-swagger-ui SwaggerUi, and utoipa-axum OpenApiRouter with the routes! macro that registers a handler once for both routing and the spec. Keywords: axum openapi, utoipa, utoipa-axum, utoipa-swagger-ui, ToSchema, utoipa::path macro, derive OpenApi, OpenApiRouter, routes macro, split_for_parts, SwaggerUi, swagger ui, api documentation drift, spec out of date, route documented but returns 404, schema missing from spec, swagger ui blank page, how do I add swagg

2026-05-200

name	axum-agents-scaffold
description	Use when the request is to build a complete Axum service from scratch rather than to fix one isolated piece: "build me an Axum API", "scaffold a Rust web service", "set up a new Axum project", or when a half-built service needs the missing production layers identified and ordered. Prevents scaffolding in the wrong order (layering before routes, choosing a framework before pinning a version), shipping a service with no graceful shutdown or permissive CORS, and reinventing decisions that a dedicated skill in this package already owns. Covers the ordered core to syntax to impl to errors build sequence, a service-type classifier, the Cargo.toml dependency baseline, the minimal-to-production checklist, and which of the other 28 Axum skills owns each decision. Keywords: axum scaffold, build axum service, new axum project, axum project structure, scaffold rust web service, axum boilerplate, where do I start with axum, how do I structure an axum app, axum service checklist, axum production checklist, axum Cargo.toml, axum dependencies, missing graceful shutdown, service has no CORS, what skill do I need, build order, axum starter, full axum example, axum from requirement.
license	MIT
compatibility	Designed for Claude Code. Requires Axum 0.7,0.8.
metadata	{"author":"OpenAEC-Foundation","version":"1.0"}

axum-agents-scaffold

Overview

This is an orchestration skill. It does NOT teach an Axum API. It teaches the ordered sequence of decisions for building a complete Axum service and names the exact skill in this package that owns each decision.

Reach for this skill when the request is "build a service", not "fix this extractor". A single isolated question goes straight to the owning skill. A whole-service build runs the sequence below.

Core principle: an Axum service is built in the same order as the package dependency chain, core -> syntax -> impl -> errors -> agents. Building out of order produces rework. ALWAYS classify the service type first, ALWAYS pin the version second, then follow the sequence.

Quick Reference

The ordered build sequence. Each step names the skill that owns it.

Step	Decision	Owning skill(s)
0	Classify the service type	`axum-core-architecture`
1	Pin Axum 0.7 or 0.8 (new: 0.8)	`axum-core-version-migration`
2	Build the `Router`, method-routers, fallbacks	`axum-core-router`
3	Define shared `State` for long-lived resources	`axum-core-state`
4	Write handlers, pick extractors	`axum-syntax-extractors`, `axum-syntax-handlers`, `axum-syntax-responses`, `axum-syntax-custom-extractors`
5	Add middleware and the tower stack	`axum-impl-middleware`, `axum-impl-tower-stack`, `axum-impl-static-files`
6	Define `AppError`, wire `IntoResponse` and `From`	`axum-errors-handling`, `axum-errors-extractor-rejections`, `axum-errors-handler-trait`
7	Add authentication	`axum-impl-auth-jwt`, `axum-impl-auth-session`
8	Add authorization gates	`axum-impl-authorization`
9	Wire the database pool and validation	`axum-impl-database`, `axum-impl-validation`
10	Realtime (optional, type-dependent)	`axum-impl-websockets`, `axum-impl-sse`, `axum-impl-file-upload`
11	Observability and API docs	`axum-impl-tracing`, `axum-impl-openapi`
12	Tests against a shared `app()` constructor	`axum-impl-testing`
13	Release build, Docker, graceful shutdown	`axum-impl-deployment`
14	Self-review before declaring done	`axum-agents-api-review`

Skills that ALWAYS apply, regardless of service type: axum-core-architecture, axum-core-version-migration, axum-core-async-performance, axum-impl-middleware, axum-impl-tower-stack, axum-impl-tracing, axum-impl-deployment, axum-errors-handler-trait, axum-agents-api-review.

Core rules:

ALWAYS run the service-type decision tree before writing any code.
ALWAYS pin the Axum version before writing the first route. Path syntax, the WebSocket Message type, and custom-extractor syntax all diverge.
ALWAYS follow the sequence order. Routing precedes state precedes handlers precedes middleware precedes errors.
ALWAYS finish with the axum-agents-api-review checklist.
NEVER skip the "Hardened" tier before a deploy. It is not optional.
NEVER scaffold a database-backed service without also consulting axum-core-async-performance. A blocking query starves the runtime.

Decision Trees

Classify the service type

Run this FIRST. The branch determines which optional steps apply.

What does the service primarily do?

Stateless JSON CRUD API:
  axum-core-router, axum-core-state, axum-syntax-extractors,
  axum-syntax-handlers, axum-syntax-responses, axum-impl-database,
  axum-impl-validation, axum-errors-handling, axum-impl-auth-jwt,
  axum-impl-testing

Server-rendered browser app (cookies, sessions, forms):
  axum-core-router, axum-core-state, axum-syntax-responses,
  axum-impl-auth-session, axum-impl-static-files, axum-impl-validation,
  axum-errors-handling, axum-impl-testing

Realtime bidirectional (chat, live dashboard):
  axum-core-router, axum-core-state, axum-impl-websockets,
  axum-core-async-performance, axum-impl-auth-jwt, axum-errors-handling,
  axum-impl-testing

One-way server push (notifications, progress streams):
  axum-core-router, axum-core-state, axum-impl-sse,
  axum-core-async-performance, axum-impl-testing

File or media service (upload, static hosting):
  axum-core-router, axum-impl-file-upload, axum-impl-static-files,
  axum-impl-tower-stack, axum-core-async-performance, axum-errors-handling

Public API for third parties:
  everything in "Stateless JSON CRUD API" PLUS axum-impl-openapi,
  axum-impl-tracing, axum-impl-authorization, axum-impl-deployment

WebSockets or SSE for the realtime branch

Must the client also SEND messages over the live connection?
  YES: WebSockets. Consult axum-impl-websockets.
  NO (server push only): SSE. Consult axum-impl-sse.
       SSE is simpler and more proxy-friendly.

Single question or full build

Is the request about one isolated piece (an extractor, one error, one route)?
  YES: skip this skill. Go straight to the owning skill in the table above.
  NO (build or extend a whole service): run the full sequence here.

Patterns

Pattern: the orchestration workflow

ALWAYS run scaffolding as three explicit phases.

Classify. Run the service-type decision tree. Write down the branch and the skill list it produced. ALWAYS classify before scaffolding.
Sequence. Walk steps 0 to 14 in order. At each step, open the owning skill, apply it, then move on. NEVER jump ahead: a later step depends on the types fixed by an earlier one.
Review. Run the axum-agents-api-review checklist. NEVER declare a service done before this step.

Pattern: service-shape rules

These rules pull extra skills into the branch regardless of the base type.

ANY service touching a database pulls in axum-impl-database AND axum-core-async-performance. A blocking query on the async runtime starves every other request.
ANY service with non-public routes pulls in an auth skill (axum-impl-auth-jwt or axum-impl-auth-session) AND axum-impl-authorization.
ANY realtime branch ALWAYS pulls in axum-core-async-performance. Blocking the socket task or holding a !Send value across .await is the dominant realtime failure mode.
ANY public-facing API pulls in axum-impl-openapi and axum-impl-tracing.

Pattern: the minimal-to-production tiers

Build a service in tiers. ALWAYS complete the Hardened tier before any deploy. The full per-item checklist is in references/examples.md.

Tier	Goal	What it adds
Minimal	Proof of life	`#[tokio::main]`, one `Router` route, `axum::serve`
Functional	Does real work	Typed extractors, shared `State`, `AppError`, JSON bodies
Hardened	Before any deploy	`TraceLayer`, allowlist `CorsLayer`, `TimeoutLayer`, body limit, env secrets, auth, graceful shutdown, sized DB pool, tests
Operable	Production lifecycle	Multi-stage Docker, release build, health route, compression, OpenAPI

Pattern: the dependency baseline

Step 1 fixes the Axum version; the dependency set follows from the branch. Core dependencies (axum, tokio, tower, tower-http, serde, serde_json, thiserror, anyhow, tracing, tracing-subscriber) are always present. Database, auth, validation, and extras crates are pulled in per branch. The full annotated Cargo.toml with feature-flag notes is in references/methods.md.

ALWAYS pin minor versions and let the patch float. ALWAYS enable only the crate features the service uses; tokio feature full is acceptable for an application binary but NEVER for a library.

Reference Links

references/methods.md: the full 14-step build sequence with the precise action and owning skill for each step, plus the complete annotated Axum 0.8 Cargo.toml dependency baseline and feature-flag guidance.
references/examples.md: two end-to-end worked scaffolds (a stateless JSON CRUD API and a realtime WebSocket service), each walked step by step, plus the complete minimal-to-production checklist.
references/anti-patterns.md: real scaffolding mistakes with root-cause analysis: building before classifying, layering before routing, skipping the version pin, permissive CORS, no graceful shutdown, and skipping the self-review.

Related skills: every skill in this package. The Quick Reference table maps each build step to its owning skill. axum-agents-api-review is the companion agents skill that audits a finished service.