Fastify API

What problem does it solve?

Fastify codebases often drift into inconsistent patterns, duplicated route logic, scattered validation, and hard-to-change handlers that make refactors risky.

Core Features & Use Cases

• Phased architectural rules for structuring routes, plugins, schemas, and services so concerns stay separated (validation in schemas, cross-cutting in plugins, business logic in services).
• Safe Fastify best practices including TypeBox schema validation, global error handling, and startup-time config validation to prevent runtime surprises.
• Use Case: You are inheriting a Fastify API where routes manually parse inputs, auth logic is duplicated, and failures return inconsistent shapes; use this Skill to standardize structure and error/validation behavior while keeping behavior stable.

Quick Start

Tell your agent: implement the Fastify API structure by moving schema validation into src/schemas, encapsulating auth/DB/error handling into src/plugins, and refactoring route handlers to call pure services in src/services.