The Complete Production SOP: How to Deploy and Run Hono Ultra-Fast Multi-Runtime Edge Router in Autonomous AI Agents

Autonomous agents load procedural skills from either global or workspace-level configuration directories. Mount the `hono-edge-router-middleware` manifest into the standard agent skill directory (`~/.agents/skills/` or `.claude/skills/`). The agent runtime parses the YAML frontmatter to index triggers such as 'write hono api route' and 'hono cors middleware', while mapping execution permissions (`fs_read: true`, `fs_write: 'workspace'`).

---
name: "hono-edge-router-middleware"
description: "Build lightweight, standard-compliant HTTP APIs running seamlessly on Cloudflare, Bun, and Node."
metadata:
  author: "Yusuke Wada"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "write hono api route"
  - "hono cors middleware"
  - "deploy hono cloudflare workers"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# Hono Ultra-Fast Multi-Runtime Edge Router
Develops REST APIs with Hono: configuring routing patterns, chaining built-in middleware (cors, logger, secureHeaders, basicAuth), context methods (c.json, c.text, c.req.header), and multi-runtime portability.

Ensure the target repository contains the minimal Hono core package and runtime-specific typings. For Cloudflare Workers, `@cloudflare/workers-types` and `wrangler` are needed; for Bun, zero extra adapters are required; for Node.js, `@hono/node-server` is required. Verify that runtime environment variables and secrets (like JWT secrets or database connection strings) are sourced strictly through Hono's `env()` context or `c.env` binding rather than hardcoded `process.env`.

Instruct the agent using registered triggers like 'write hono api route' or 'hono cors middleware'. The agent detects the trigger signature from the SKILL.md specification and switches from generic Express/Node boilerplate generation to strict Hono multi-runtime routing syntax.

import { Hono } from 'hono'
import { cors } from 'hono/cors'
import { logger } from 'hono/logger'
import { secureHeaders } from 'hono/secure-headers'

export interface Bindings {
  DATABASE_URL: string
}

const app = new Hono<{ Bindings: Bindings }>()

// Deterministic Middleware Chaining
app.use('*', logger())
app.use('*', secureHeaders())
app.use('/api/*', cors({
  origin: ['https://example.com'],
  allowMethods: ['GET', 'POST', 'PUT', 'DELETE', 'OPTIONS'],
  maxAge: 86400,
}))

app.get('/api/users/:id', (c) => {
  const id = c.req.param('id')
  return c.json({ status: 'ok', userId: id, timestamp: Date.now() })
})

export default app

The skill mandates a verification checklist prior to session sign-off. Force the agent to execute a dry-run TypeScript check (`tsc --noEmit`) and verify router exports to confirm that routes compile cleanly against Web Standard types without uncommitted secrets or broken imports.