Results for “route-handlers”

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Provides Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.

Routes rendered UI testing, visual regression, browser QA, accessibility, responsive, performance, or frontend review to a leaf skill.

Provides best practices for Vue Router 4, including navigation guards, route params, and route-component lifecycle interactions.

Routes frontend design tasks to 48 specific UI styles, providing color palettes and implementation guidance for websites, app screens, or UI components.

Next.js App Router — Agent Arena Patterns

Designs REST and GraphQL APIs following production best practices for resource naming, error handling, versioning, authentication, and documentation. Use this skill when designing new API endpoints, reviewing API contracts, implementing GraphQL schemas, establishing API conventions for a project, or writing API documentation. Apply when creating any route in Next.js API routes or route handlers, any Supabase Edge Function, or any backend endpoint — even if it starts small, these patterns prevent painful rewrites later.

Use when building APIs on Hono (Cloudflare Workers, Bun, Deno, Node), debugging route ordering, wiring middleware, validating with @hono/zod-validator, returning streaming responses, configuring CORS with credentials, handling errors via app.onError, or composing typed RPC clients. Triggers: c.env binding types, c.header + c.redirect interaction, missing await next() bugs, Set-Cookie not attaching to redirect, route-precedence surprises, JWT middleware setup, hono/client typed RPC end-to-end. NOT for Express/Fastify/Koa idioms, tRPC/GraphQL paradigms, or Next.js Route Handlers.