fisioflow-api-patterns

Standardize API route patterns for Hono-based Cloudflare Workers with Drizzle ORM and Neon Auth.

Updated Sep 2, 2025
One-click install
npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill fisioflow-api-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fisioflow-api-patterns
Source: https://github.com/rafaelminatto1/fisioflow-51658291/tree/main/.agents/skills/fisioflow-api-patterns
Command: npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill fisioflow-api-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a consistent blueprint for API route patterns across the FisioFlow stack, reducing ad-hoc routing decisions and increasing maintainability.

Core Features & Use Cases

  • Route file structure guidance for Hono-based Cloudflare Workers.
  • Middleware, authentication flow, error handling, and response formatting standards aligned with Neon Auth, Drizzle ORM, and tenant scoping.
  • Practical use cases and examples to review or implement new routes that conform to the project conventions.

Quick Start

Follow the documented API pattern conventions to ensure new routes align with FisioFlow standards.

Frequently Asked Questions about fisioflow-api-patterns

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

FAQPage Schema
How do I structure API routes for Hono on Cloudflare Workers?

Standardize API routes for Hono on Cloudflare Workers by following consistent file structure, middleware, and response formatting conventions to ensure predictable development practices and maintainability.

What is the standard pattern for tenant-scoped API routing?

Tenant-scoped API routing standardizes request handling by applying consistent authentication flows and data access patterns, ensuring queries are properly isolated per tenant across the application stack.

How do I handle authentication flow and errors with Neon Auth and Drizzle ORM?

Handle authentication flow and errors with Neon Auth and Drizzle ORM by applying standardized middleware and error handling patterns that normalize responses across all API routes.

Can I use these API conventions to review existing route files?

Yes, you can use these API conventions to review existing route files by checking their middleware, authentication flow, and response formats against the documented standardization patterns.

What's the best way to standardize API response formats across a full stack?

The best way to standardize API response formats is to enforce consistent normalization patterns across Hono routes, Drizzle ORM data access, and Neon Auth flows, reducing ad-hoc routing decisions.