glapi-backend-guidelines

What problem does it solve?

This guide removes guesswork from GLAPI backend services by enforcing a dual TRPC/REST pattern, shared services, and consistent Drizzle plus Clerk usage so internal and external clients stay type-safe and secure.

Core Features & Use Cases

• Dual API Architecture keeps internal TRPC procedures thin while REST routes reuse those procedures for external clients.
• Layered Services & Drizzle Access centralize business logic in services that call PostgreSQL via Drizzle while routers handle Zod validation and Clerk authentication.
• Checklists and Templates cover creating procedures, REST routes, services, testing, and OpenAPI documentation, with referenced examples under resources/ for quick reference.

Quick Start

Draft a TRPC procedure that delegates to a service, validates input with Zod, and exposes it via Clerk-protected REST per the GLAPI layered architecture.