hono-void — Claude Code skill: test Void apps with Hono CLI
hono-void — a skill for Claude Code, Cursor, Codex and other platforms that triggers when working with Void, a framework built on Hono. The agent checks pages, actions and API routes through Hono CLI instead of a browser or curl.
MIT 608 installs ★ 20 updated 2026-10-15
npx skills add honojs/skills --skill hono-void -a claude-codeWhat hono-void does
Void builds a Hono app from file-based routes, and the code does not import hono directly. hono-void trains the agent to run npx hono routes, npx hono request and npx hono batch to verify pages, page actions and JSON responses. For a form with validation, the agent sends x-voidpages: true and checks errors in the response body — an action returns 200 even on validation failure, so the status code won't help.
The skill activates when package.json lists void as a dependency, the project has void.config.ts, or you mention Void in your prompt. To check client-side JavaScript (redirects, form values persisting after submit), the agent runs npx hono browse with happy-dom — it renders the page and executes scripts, but without CSS or layout. Without happy-dom in devDependencies, the command fails.
What it helps with
- test a Void app with file-based routing through Hono CLI
- verify a page action with validation and
errorsin the JSON response - run a create-then-read flow with a single
npx hono batchcall - check client-side JavaScript and redirects in
npx hono browse - confirm a form does not retain old values after submit
Example prompts for the agent
- Check the routes in this Void app and request the home page
- Send POST to
/ramenwith an emptyshopfield and verify the validation error - Fill the form at
/with the nameHono Ramen, click the button and check the redirect in the browser
How to install hono-void
1Skills CLI (Vercel)
npx skills add honojs/skills --skill hono-void -a claude-code2Manually: put the files in place
~/.claude/skills/hono-void/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/hono-void/
1Skills CLI (Vercel)
npx skills add honojs/skills --skill hono-void -a codex2Manually: put the files in place
.agents/skills/hono-void/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add honojs/skills --skill hono-void -a cursor2Manually: put the files in place
.cursor/skills/hono-void/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install honojs/skills skills/hono-void2Manually: put the files in place
.github/skills/hono-void/SKILL.md1Skills CLI (Vercel)
npx skills add honojs/skills --skill hono-void -a gemini-cli2Platform CLI
gemini skills install https://github.com/honojs/skills --path skills/hono-voidManually: put the files in place
.devin/skills/hono-void/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add honojs/skills --skill hono-void -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about hono-void
How to install hono-void in Claude Code?
Run npx skills add honojs/skills --skill hono-void -a claude-code, and the skill lands in ~/.claude/skills/hono-void/SKILL.md.
What does hono-void do?
The skill activates in Void projects and trains the agent to test pages, actions and API routes through Hono CLI: npx hono request, npx hono batch and npx hono browse. Void builds the app from files, and typical verification methods do not fit.
Why send x-voidpages: true in the request?
A Void page returns HTML, but with this header it returns JSON with props, errors and component. The agent checks page data and validation errors without parsing HTML.
Source text
SKILL.md · MIT
---
name: hono-void
description: Use when checking or testing a Void app with Hono CLI — pages, page actions, and API routes. TRIGGER when package.json depends on 'void', the project has void.config.ts, or the user mentions Void. Void is a framework built on Hono.
---
# Hono Void Skill
[Void](https://void.cloud) builds a Hono app from file-based routes, so there is no entry file and the code does not import `hono`. Verify changes with [Hono CLI](https://github.com/honojs/cli), not with a browser, curl, or a dev server. It runs the app through Vite with no flag and no file argument:
```bash
npm install -D @hono/cli@next
npx hono --help
npx hono routes --exclude /__void # hide Void's internal routes
npx hono request /
```
For a flow (create, then read), use one `npx hono batch -` call with `expect` on every step. Send `x-voidpages: true` so a page answers with JSON instead of the full HTML. A page action returns 200 even when it fails, so assert on the body (`body` in `expect` is a deep partial match):
```bash
npx hono batch - <<'EOF'
{"method":"POST","path":"/","headers":{"x-voidpages":"true"},"body":{"shop":""},"expect":{"status":200,"body":{"errors":{"shop":"Enter a shop name"}}}}
{"method":"POST","path":"/","headers":{"x-voidpages":"true"},"body":{"shop":"Hono Ramen"},"expect":{"status":200}}
EOF
```
A create that redirects shows its `location`; follow it with `"save":{"next":"header:location"}` and then `"path":"{{next}}"`. An array in `expect` must match the whole array, so check one item of a list by reading the response, not with `expect`. The path, fields, and messages above are an example. Check yours with `npx hono routes` and one request first.
## Checking the page in a browser
HTTP requests do not run the page's JavaScript, so they miss client-side bugs: a form that keeps its values after a submit, or a redirect that lands on the wrong URL. Check those with `npx hono browse`. It loads the page in happy-dom, runs its JavaScript, and fills and clicks in order. Install happy-dom first:
```bash
npm install -D happy-dom
npx hono browse / --fill "Shop name=Hono Ramen" --click 'button[type=submit]'
```
`--fill` takes a field's name, label text, or placeholder (the keys in `forms` of the output), or a CSS selector. The output has the final `url`, the visible `text`, the `forms` values, and `console` errors. happy-dom has no layout or CSS.
## Checking a Void app
- `pages/**` return HTML. Send the header `x-voidpages: true` to get the page data as JSON: `{ component, props, errors, head, ... }`.
- Page actions are POST/PUT/PATCH/DELETE to the page URL. A named action has a `?name` suffix, e.g. `POST /ramen/1?delete`.
- A validation failure in a page action returns 200, not 422, with the messages in `body.errors` (`{ field: message }`). A success has no `errors`.
- A foreign `Origin` header gets 403. Omit `Origin` or use the app's own origin.
- `npx void db seed --yes` resets the local DB between runs.
For Void itself (routing, pages, the Void CLI), read Void's docs in `node_modules/void/docs/`.
© honojs · MIT · honojs/skills