backend

Design layered HTTP APIs with Zod validation and typed JWT auth.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/nsvk13/skills --skill backend-nsvk13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend
Source: https://github.com/nsvk13/skills/tree/main/backend
Command: npx skills add https://github.com/nsvk13/skills --skill backend-nsvk13

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The backend skill helps you build reliable, maintainable HTTP APIs end-to-end by enforcing validation, layered architecture, consistent error handling, and pragmatic database/cache/async patterns.

Core Features & Use Cases

  • API design & project structure: Clean routers/handlers, services, repositories, config, and middleware with a production-first style.
  • Production-ready correctness: Zod validation, explicit error hierarchy, request IDs, graceful error responses, and robust shutdown guidance (via references).
  • Database & performance patterns: DrizzleORM modeling, transaction boundaries, and avoiding N+1 using query composition; PostgreSQL query/migration guidance (via references).
  • Auth, caching, and async work: JWT middleware, cache-aside with Redis, BullMQ queues/workers for retries and background processing; event-driven orchestration (via references).

Quick Start

Provide your endpoint requirements and constraints (auth method, request/response shapes, data model) and ask for a layered Hono or Go chi implementation including validation, error responses, and the repository/service split.

Frequently Asked Questions about backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a production-ready HTTP API with Hono or Go chi?

A production-ready HTTP API requires a layered architecture separating routers, handlers, services, and repositories. This structure enforces consistent error handling, isolated business logic, and maintainable database operations across Hono or Go chi implementations.

What's the best way to validate API requests and handle errors in a backend service?

Backend validation is best handled using Zod for input schemas alongside a robust AppError hierarchy. This combination ensures consistent error responses, explicit request IDs, and graceful failures across your HTTP API endpoints.

How do I avoid N+1 queries and manage transactions with PostgreSQL?

Avoid N+1 queries in PostgreSQL by using query composition and transaction boundaries within your repository layer. This approach ensures transaction-safe database operations and optimized data fetching.

Can I use Redis and BullMQ for background jobs in a Node or Bun backend?

Yes, Redis and BullMQ are used for background jobs in Node or Bun backends. This setup enables cache-aside patterns, retry queues, and event-driven orchestration for asynchronous processing.

Does this backend architecture support typed JWT auth middleware?

Yes, this backend architecture supports typed JWT auth middleware. It integrates directly into the HTTP API layer to secure endpoints and manage authentication flows seamlessly.

When should I separate repository and service layers in API design?

Separate repository and service layers whenever building production-grade HTTP APIs to isolate data access from business logic. This split prevents N+1 queries, clarifies transaction boundaries, and maintains clean code.