Structure Hono APIs with separated routes, services, middleware, and Zod validation.
npx skills add https://github.com/Levironexe/architect --skill hono-api-levironexe
Please help me install this Agent Skill. Skill: Hono API Source: https://github.com/Levironexe/architect/tree/main/skills/stacks/hono-api Command: npx skills add https://github.com/Levironexe/architect --skill hono-api-levironexe
Projects built with Hono can drift into inconsistent route structure, mixed responsibilities, ad-hoc validation, and unsafe refactors that break edge compatibility or error handling contracts.
Ask your agent to restructure the codebase to match the Hono API skill: create src/routes, src/services, src/middleware, move business logic out of handlers, add zValidator-based Zod validation, and implement a global app.onError() that returns consistent JSON using HTTPException.
High-intent search queries and answers about installing and using this skill.
Structure a Hono API by separating routing in src/routes, platform-agnostic business logic in src/services, and cross-cutting concerns like auth in src/middleware. This separation supports safe phased refactoring and ensures edge compatibility across Cloudflare Workers, Node.js, and Bun.
The best way to validate request inputs in a Hono application is using @hono/zod-validator at the route boundary. This enforces typed, schema-validated inputs under src/schemas rather than trusting raw request JSON, ensuring data integrity.
Centralized error handling in Hono works by implementing app.onError() to return consistent JSON responses using HTTPException. This approach avoids Node-only APIs, ensuring uniform error handling across edge and Node-like runtimes.
No, you should avoid Node-only APIs like process or fs inside Hono route handlers to maintain edge compatibility. Business logic must be platform-agnostic inside src/services, ensuring the same code works across Cloudflare Workers and Bun.
Yes, Zod is required to implement schema validation for Hono APIs in this architecture. You define schemas under src/schemas and apply them via zValidator to enforce typed inputs at the route boundary.
Hono API architecture drifts into mixed responsibilities and ad-hoc validation without enforced separation. Establishing src/routes, src/services, and src/middleware directories centralizes validation and cross-cutting concerns, preventing inconsistent route structure.
AgentiveCityGenerate Hono + TypeScript backend scaffolds with runtime-specific configuration.
trystan2kTest Hono endpoints and access API documentation across runtimes.
ftc8569Build type-safe REST APIs with Hono routes, middleware, and CORS in Node.js.
AgLyx3Design backend architectures and APIs for Node.js, Express, Fastify, and PostgreSQL services.
