Production Hono patterns — zValidator hooks, typed generics, error handling, middleware composition, testing, and multi-runtime deployment
87
80%
Does it follow best practices?
Impact
98%
2.57xAverage score across 5 eval scenarios
Passed
No known issues
{
"instruction": "Use the correct entry point pattern for the target runtime",
"relevant_when": "Agent creates the entry point / server startup file for a Hono application",
"context": "Each runtime has a specific entry point pattern. Node.js requires the @hono/node-server adapter: import { serve } from '@hono/node-server'; serve({ fetch: app.fetch, port: 3000 }). Bun uses export default { fetch: app.fetch, port: 3000 }. Cloudflare Workers uses export default app. Deno uses Deno.serve({ port: 3000 }, app.fetch). Using the wrong pattern for a runtime causes silent failures -- e.g. 'export default app' does not start a server on Node.js. The @hono/node-server package must be in dependencies when targeting Node.",
"sources": [
{
"type": "file",
"filename": "skills/hono-best-practices/SKILL.md",
"tile": "tessl-labs/hono-best-practices@0.2.0"
}
],
"checklist": [
{
"name": "correct-runtime-pattern",
"rule": "The entry point uses the correct pattern for the target runtime: @hono/node-server serve() for Node.js, export default { fetch, port } for Bun, export default app for Cloudflare, Deno.serve() for Deno",
"relevant_when": "Agent creates a Hono entry point file"
},
{
"name": "node-server-dependency",
"rule": "When targeting Node.js, @hono/node-server is listed as a dependency in package.json",
"relevant_when": "Agent sets up a Hono project targeting Node.js"
}
]
}