What problem does it solve? Building a multi-tenant Next.js 14 application requires consistent conventions for route groups, API handlers, server actions, and middleware. This Skill codifies DropFlow's App Router patterns so generated code follows the same structure, response shapes, and naming conventions every time. ## Core Features & Use Cases - Route Group Conventions: Defines the (auth), (dashboard), (storefront), and (supplier) route groups plus the app/api/v1 REST structure. - API Route Pattern: Standard POST handler using requireAuth, tenant-scoped Prisma, Zod validation, and ok/err response helpers. - Server Action Pattern: Typed server actions via authAction with schema validation in actions/[domain]/verb-noun.ts files. - Middleware Setup: Clerk middleware resolving tenant subdomains, applying rate limits, and injecting x-tenant-id headers. - Use Case: When adding a new orders endpoint, generate app/api/v1/orders/route.ts that authenticates the tenant, validates input with Zod, and returns the standard { success, data, error } response shape. ## Quick Start Create a new API route for products in the DropFlow app following the standard tenant-scoped pattern.