Agent skill · software engineering · pedronauck
hono
Use when building Hono web applications or when the user asks about Hono APIs, routing, middleware, JSX, validation, testing, or streaming. TRIGGER when code imports from 'hono' or 'hono/*', or user mentions Hono. Use Hono CLI to inspect and test the app.
Why this skill is useful
Adds specific commands and workflows for using Hono CLI that enhance the AI's ability to develop Hono applications efficiently.
What it needs
Requires @hono/cli installed locally. About 8k tokens when loaded. Last updated 2026-08-01. 564 stars on the source repository.
What this skill does
Hono Skill Build Hono web applications. This skill provides inline API knowledge for AI. Use Hono CLI to inspect and test the app. Latest Documentation For details beyond this inline reference, fetch the latest documentation from https://hono.dev. Get the index of doc pages from https://hono.dev/llms.txt, then fetch a page with the Accept: text/markdown header to receive it as Markdown: Hono CLI Use Hono CLI to inspect and test the app. Install it in the project, then let the CLI explain itself: <!-- TODO at the 0.2 release: change @hono/cli@next to @hono/cli --> Follow the output. It explains every command (routes, request, batch, snapshot, benchmark, optimize, ssg), the JSON output contract, and the workflow. Notes: hono request sends a request with app.request() — no server needed. Do not pass credentials directly in CLI arguments; use environment variables for sensitive values. For Cloudflare Workers bindings (KV, D1, R2, etc.), use hono request /path --runtime workerd. It starts the app with the wrangler config of the project, so the local bindings (c.env) are real. wrangler must be installed in the project. For several requests, or a flow that keeps state (POST, then use the returned id), run them in one hono batch - call. One JSON object per line; save a value and use it as {{id}} in later steps. The steps share one app instance. Declare the expected status/body per step with expect (body is a deep partial match) and iterate until the summary shows "failed": 0: Before changing existing routes, capture the current behavior: npx hono snapshot prints it as batch JSONL lines (real responses become the expect). Keep the lines, make the change, then rerun them with npx hono batch - until "failed": 0. On a large API, use npx hono snapshot --status-only and npx hono batch - --compact — same loop, much smaller output. A failed step carries diff: fix what it names. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pedronauck/hono