What problem does it solve? Backend work often drifts into inconsistent layering, framework-coupled controllers, ad-hoc error handling, and unsafe transaction or authorization patterns. This Skill applies a repository-aware server architecture so controllers, services, use cases, repositories, contracts, and adapters stay correctly separated across any runtime or framework. ## Core Features & Use Cases - Slice-based routing: Loads only the relevant architecture references (contracts, data-flow, operations, security, telemetry, testing, runtimes, workspace, scaffolding) for the task at hand. - Repository-aware scaffolding: The $server scaffold command bootstraps foundations or vertical capabilities with preflight evidence checks, dependency approval, and atomic writes. - Framework specializations: Provides concrete guidance for Next.js, Express, Hono, NestJS, tRPC, OpenAPI, Drizzle, Supabase, and Better Auth while remaining framework-neutral at the core. - Use Case: When adding a Stripe webhook to a Next.js app, the Skill loads contracts, operations, security, telemetry, testing, and runtimes slices to enforce signature verification, idempotent writes, and typed error mapping. ## Quick Start Ask the assistant to use $server to design, review, or scaffold your backend feature, for example: use $server scaffold users/create in this repository.
