fastify-domain-delivery

Convert Fastify feature changes into schema-first, plugin-encapsulated implementations with scoped fastify.inject verification.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill fastify-domain-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fastify-domain-delivery
Source: https://github.com/vTRKA/supervibe/tree/main/skills/fastify-domain-delivery
Command: npx skills add https://github.com/vTRKA/supervibe --skill fastify-domain-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents Fastify implementations from drifting into unstructured, schema-inconsistent behavior by turning API changes into plugin-safe, schema-first, lifecycle-aware deliveries with scoped verification.

Core Features & Use Cases

  • Schema-first route contracts: Defines params, query, body, and response schemas up front to keep runtime validation and output shape aligned.
  • Plugin encapsulation and lifecycle correctness: Ensures decorators are registered before use, external resources are opened/closed in the owning plugin, and lifecycle phases are respected.
  • Operationally visible verification: Plans and tests the smallest fastify.inject slice to prove auth hooks, serializers, async error mapping, and shutdown behavior without binding a real port.
  • Error, hook, and observability rigor: Routes async errors through typed errors and a registered error handler, applies hooks at the narrowest lifecycle scope, and instruments request/trace/metrics fields when safe.

Quick Start

Ask your AI tool to apply the Fastify domain delivery flow to your specific feature by requesting a schema-first implementation plan with the exact plugin boundary and a scoped fastify.inject verification command.

Frequently Asked Questions about fastify-domain-delivery

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

FAQPage Schema
How do I verify Fastify route changes without binding a real port?

Use scoped fastify.inject checks to verify Fastify route changes without binding a real port. This proves auth hooks, serializers, async error mapping, and shutdown behavior during development without requiring a live server.

What's the best way to structure Fastify plugins to prevent decorator errors?

The best way to structure Fastify plugins is through plugin encapsulation, ensuring decorators are registered before use and external resources are opened and closed within the owning plugin's lifecycle phases.

How do I manage async errors in Fastify hooks and error handlers?

Manage async errors in Fastify by routing them through typed errors and a registered error handler. Apply hooks at the narrowest lifecycle scope to maintain operational visibility and request traceability.

When do I need schema-first route contracts in Fastify?

You need schema-first route contracts in Fastify when adding or modifying routes to keep runtime validation and output shape aligned. Define params, query, body, and response schemas up front to prevent unstructured behavior.

How do I handle graceful startup and shutdown behavior in Fastify plugins?

Handle graceful Fastify startup and shutdown by ensuring external resources are opened and closed in the owning plugin, respecting lifecycle phases and lifecycle-aware resource handling to maintain operational correctness.

Does Fastify schema-first delivery support observability and metrics instrumentation?

Yes, Fastify schema-first delivery supports observability by instrumenting request, trace, and metrics fields when safe. This ensures operationally visible verification and evidence-based behavior throughout the plugin lifecycle.