Compose type-safe middleware for Next-safe-action with immutable chains.
npx skills add https://github.com/gepetojj/umo --skill safe-action-middleware
Please help me install this Agent Skill. Skill: safe-action-middleware Source: https://github.com/gepetojj/umo/tree/main/.agents/skills/safe-action-middleware Command: npx skills add https://github.com/gepetojj/umo --skill safe-action-middleware
This Skill provides a framework to implement and compose middleware for Next-safe-action, enabling authentication, authorization, logging, rate limiting, error interception, context extension, and reusable standalone middleware via createMiddleware() or createValidatedMiddleware().
Create a Safe Action client with a simple authentication middleware using .use(), then add input validation with .inputSchema() and attach a post-validation middleware with .useValidated().
High-intent search queries and answers about installing and using this skill.
You can add authentication and authorization middleware to Next-safe-action server actions by using .use() for pre-validation tasks like authentication and .useValidated() for post-validation tasks like authorization, ensuring predictable flows.
Yes, you can create reusable middleware patterns for multiple Next-safe-action clients by utilizing the createMiddleware() and createValidatedMiddleware() functions, enabling standalone middleware to be applied across different server action implementations.
The best way to compose rate limiting and logging middleware in Next.js server actions is by applying an immutable middleware framework that chains these functions securely, merging context and ensuring errors propagate correctly.
Yes, the middleware framework supports both inputSchema and bindArgs schemas for Next-safe-action, allowing you to apply pre-validation and post-validation middleware while maintaining strict type safety across your server actions.
Context extension works by merging contexts immutably as you chain middleware via .use() or .useValidated(), ensuring that data enriched in earlier middleware layers is predictably accessible in subsequent server action steps.
yutnaImplement type-safe Next.js server actions with next-safe-action and Effect.
gepetojjCreate next-safe-action clients with input/output validation and centralized error handling.
g-bastianelliValidates TypeScript data with Zod schemas at trust boundaries.
Ai-WhisperersHarden Next.js 15 apps with CSRF protection, rate limiting, and RLS policies.
