presentation-layer

What problem does it solve?

This Skill eliminates inconsistent implementation of the presentation (API) layer in this Rust DDD book manager project by enforcing the repository's established Axum-based conventions, reducing architectural drift and boilerplate when adding or modifying API endpoints.

Core Features & Use Cases

• Standardized Handler Implementation: Guides you to keep handlers free of business logic, only interacting with the AppRegistry to call application use cases and pass DTOs.
• Consistent Auth and Error Handling: Provides patterns for implementing both required and optional OIDC authentication, plus centralized API error mapping to consistent HTTP responses.
• Reference Implementation Templates: Includes concrete examples of existing book and user endpoint patterns to use as templates for new features. Use case: When adding a new endpoint to allow users to reserve books, this Skill ensures your implementation matches the existing patterns for routing, authentication, and error handling used by other endpoints like POST /api/books/{id}/checkouts.

Quick Start

Use the presentation-layer skill to implement a new authenticated endpoint for reserving books in the api crate following the repository's existing Axum and auth patterns.