innozverse-api-style

Name: innozverse-api-style
Availability: InStock
Author: lastcow

Enforce RESTful design, Fastify patterns, Zod validation, and versioning for innozverse APIs.

Updated Dec 21, 2025

Search Tags:#typescript #versioning #rest #zod #fastify #api-design

Ready to run

npx skills add https://github.com/lastcow/innozverse --skill innozverse-api-style

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: innozverse-api-style
Source: https://github.com/lastcow/innozverse/tree/main/.claude/skills/api-style
Command: npx skills add https://github.com/lastcow/innozverse --skill innozverse-api-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides RESTful API design, Fastify patterns, Zod validation, error handling, and versioning for innozverse APIs.

Core Features & Use Cases

Route registration & versioning: Structured v1/v2 routes and prefixing.
Type safety: Shared types in @innozverse/shared for consistency.
Validation & errors: Zod-based validation and standardized error responses.

Quick Start

Use this Skill when building new API endpoints or updating API structure.

Frequently Asked Questions about innozverse-api-style

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

FAQPage Schema

How do I build REST APIs with consistent versioning in Fastify?▼

REST API versioning in Fastify uses structured v1/v2 route prefixing and registration patterns. This Skill standardizes route organization, endpoint conventions, and versioned paths to keep APIs maintainable as they evolve across multiple versions.

How do I validate request and response data in Fastify APIs?▼

Zod-based validation enforces type safety on incoming requests and outgoing responses. This Skill applies Zod schemas to create typed request/response contracts, ensuring data consistency across all endpoints without manual type checking.

What's the best way to handle errors consistently across a Fastify API?▼

Standardized error handling applies global error responses and async/await patterns across all routes. This Skill ensures every endpoint returns uniform error structures, status codes, and messages so clients can parse failures predictably.

Can I use shared types across multiple Fastify microservices?▼

Yes. The @innozverse/shared package centralizes type definitions so all versioned routes and endpoints reference the same TypeScript contracts. This prevents type drift and keeps request/response schemas synchronized across services.

How do I structure new API endpoints to follow RESTful conventions?▼

Endpoint structure follows RESTful method/URL conventions: GET for retrieval, POST for creation, PUT/PATCH for updates, DELETE for removal. This Skill applies those patterns consistently across routes with proper request handling and response formatting.