Skip to content

hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-architecture

hyper-architecture

Verified

[Hyper] Use this skill when the user asks for architecture, project setup, or performance work - building, auditing, restructuring, or reviewing project structure, routes, data or server boundaries, the lint/format/type tooling baseline (oxlint, Prettier, tsconfig, rustfmt, clippy), or build and runtime performance - in a Next.js App Router, TanStack Start, Vite with TanStack Router, Astro, Expo, Lynx (ReactLynx), Hono, Axum, Tauri v2, Electron, or Rust CLI, WASM, or MCP server project. It detects the stack from manifests and config files, routes each touched package of a monorepo separately, and applies the matching bundled stack guide, the shared setup baseline, and that stack's performance rules. Do not use it for stacks outside those eleven or for work that crosses no architecture, setup, or performance boundary, such as copy edits, a plain dependency bump, or one build failure.

FileKindSize
SKILL.ko.mdmarkdown19.9 KB
SKILL.mdskill md18.4 KB
assets/evals/astro-cases.jsonlother17.1 KB
assets/evals/axum-cases.jsonlother13.7 KB
assets/evals/electron-cases.jsonlother14.6 KB
assets/evals/expo-cases.jsonlother18.3 KB
assets/evals/hono-cases.jsonlother22.2 KB
assets/evals/hyper-architecture-cases.jsonlother26.0 KB
assets/evals/lynx-cases.jsonlother17.9 KB
assets/evals/nextjs-cases.jsonlother21.5 KB
assets/evals/rust-cases.jsonlother17.8 KB
assets/evals/tanstack-start-cases.jsonlother21.0 KB
assets/evals/tauri-cases.jsonlother18.6 KB
assets/evals/vite-cases.jsonlother18.6 KB
assets/templates/setup/repo/editorconfigother357 B
assets/templates/setup/repo/gitattributesother714 B
assets/templates/setup/repo/lefthook.ymlconfig843 B
assets/templates/setup/rust/clippy.tomlconfig110 B
assets/templates/setup/rust/rust-toolchain.tomlconfig86 B
assets/templates/setup/rust/rustfmt.tomlconfig200 B
assets/templates/setup/rust/workspace-lints.tomlconfig809 B
assets/templates/setup/typescript/oxlintrc.jsonconfig929 B
assets/templates/setup/typescript/oxlintrc.react.jsonconfig1.1 KB
assets/templates/setup/typescript/prettierignoreother316 B
assets/templates/setup/typescript/prettierrc.jsonconfig263 B
assets/templates/setup/typescript/tsconfig.base.jsonconfig551 B
references/official/astro/astro-2026-11-07.ko.mdmarkdown18.6 KB
references/official/astro/astro-2026-11-07.mdmarkdown17.0 KB
references/official/axum/axum-docs.ko.mdmarkdown5.7 KB
references/official/axum/axum-docs.mdmarkdown4.8 KB
references/official/axum/ecosystem-docs.ko.mdmarkdown3.8 KB
references/official/axum/ecosystem-docs.mdmarkdown3.5 KB
references/official/axum/sqlx-docs.ko.mdmarkdown5.5 KB
references/official/axum/sqlx-docs.mdmarkdown4.7 KB
references/official/axum/tower-docs.ko.mdmarkdown4.2 KB
references/official/axum/tower-docs.mdmarkdown3.7 KB
references/official/axum/utoipa-docs.ko.mdmarkdown4.1 KB
references/official/axum/utoipa-docs.mdmarkdown3.7 KB
references/official/electron/electron-2026-11-08.ko.mdmarkdown15.7 KB
references/official/electron/electron-2026-11-08.mdmarkdown14.1 KB
references/official/expo/expo-react-native-2026-11-04.ko.mdmarkdown23.0 KB
references/official/expo/expo-react-native-2026-11-04.mdmarkdown21.5 KB
references/official/hono/drizzle-docs.ko.mdmarkdown7.0 KB
references/official/hono/drizzle-docs.mdmarkdown6.6 KB
references/official/hono/hono-docs.ko.mdmarkdown15.8 KB
references/official/hono/hono-docs.mdmarkdown14.8 KB
references/official/lynx/lynx-2026-11-07.ko.mdmarkdown14.3 KB
references/official/lynx/lynx-2026-11-07.mdmarkdown14.0 KB
references/official/nextjs/current-docs-2026-11-04.ko.mdmarkdown13.1 KB
references/official/nextjs/current-docs-2026-11-04.mdmarkdown12.0 KB
references/official/nextjs/drizzle-docs.ko.mdmarkdown6.7 KB
references/official/nextjs/drizzle-docs.mdmarkdown6.3 KB
references/official/nextjs/nextjs-docs.ko.mdmarkdown13.6 KB
references/official/nextjs/nextjs-docs.mdmarkdown13.9 KB
references/official/rust/rust-crates-2026-11-07.ko.mdmarkdown22.6 KB
references/official/rust/rust-crates-2026-11-07.mdmarkdown22.0 KB
references/official/tanstack-start/current-docs-2026-11-04.ko.mdmarkdown16.0 KB
references/official/tanstack-start/current-docs-2026-11-04.mdmarkdown14.7 KB
references/official/tanstack-start/tanstack-router-2026-11-04.ko.mdmarkdown10.5 KB
references/official/tanstack-start/tanstack-router-2026-11-04.mdmarkdown9.6 KB
references/official/tanstack-start/tanstack-start-2026-11-04.ko.mdmarkdown25.8 KB
references/official/tanstack-start/tanstack-start-2026-11-04.mdmarkdown23.9 KB
references/official/tauri/tanstack-vite-react-2026-11-04.ko.mdmarkdown14.1 KB
references/official/tauri/tanstack-vite-react-2026-11-04.mdmarkdown13.1 KB
references/official/tauri/tauri-v2-2026-11-04.ko.mdmarkdown18.5 KB
references/official/tauri/tauri-v2-2026-11-04.mdmarkdown17.6 KB
references/official/tooling/tooling-2026-11-07.ko.mdmarkdown21.0 KB
references/official/tooling/tooling-2026-11-07.mdmarkdown20.5 KB
references/official/vite/current-docs-2026-11-04.ko.mdmarkdown11.2 KB
references/official/vite/current-docs-2026-11-04.mdmarkdown10.3 KB
rules/astro/actions-middleware-env.ko.mdmarkdown14.6 KB
rules/astro/actions-middleware-env.mdmarkdown12.9 KB
rules/astro/content.ko.mdmarkdown8.1 KB
rules/astro/content.mdmarkdown7.3 KB
rules/astro/performance.ko.mdmarkdown11.3 KB
rules/astro/performance.mdmarkdown10.0 KB
rules/astro/project-structure.ko.mdmarkdown11.2 KB
rules/astro/project-structure.mdmarkdown9.6 KB
rules/astro/rendering-and-islands.ko.mdmarkdown10.2 KB
rules/astro/rendering-and-islands.mdmarkdown8.7 KB
rules/astro/testing.ko.mdmarkdown10.4 KB
rules/astro/testing.mdmarkdown9.4 KB
rules/axum/conventions.ko.mdmarkdown5.3 KB
rules/axum/conventions.mdmarkdown4.8 KB
rules/axum/database.ko.mdmarkdown11.9 KB
rules/axum/database.mdmarkdown10.2 KB
rules/axum/errors.ko.mdmarkdown6.5 KB
rules/axum/errors.mdmarkdown6.0 KB
rules/axum/handlers.ko.mdmarkdown5.6 KB
rules/axum/handlers.mdmarkdown5.0 KB
rules/axum/middleware.ko.mdmarkdown5.4 KB
rules/axum/middleware.mdmarkdown4.9 KB
rules/axum/openapi.ko.mdmarkdown9.5 KB
rules/axum/openapi.mdmarkdown8.3 KB
rules/axum/performance.ko.mdmarkdown9.6 KB
rules/axum/performance.mdmarkdown8.6 KB
rules/axum/platform.ko.mdmarkdown6.9 KB
rules/axum/platform.mdmarkdown6.3 KB
rules/axum/project-structure.ko.mdmarkdown10.8 KB
rules/axum/project-structure.mdmarkdown9.9 KB
rules/axum/routes.ko.mdmarkdown7.3 KB
rules/axum/routes.mdmarkdown6.3 KB
rules/axum/testing.ko.mdmarkdown5.2 KB
rules/axum/testing.mdmarkdown4.6 KB
rules/axum/validation.ko.mdmarkdown4.8 KB
rules/axum/validation.mdmarkdown4.4 KB
rules/electron/packaging.ko.mdmarkdown7.9 KB
rules/electron/packaging.mdmarkdown7.0 KB
rules/electron/performance.ko.mdmarkdown5.8 KB
rules/electron/performance.mdmarkdown5.0 KB
rules/electron/processes-and-ipc.ko.mdmarkdown10.6 KB
rules/electron/processes-and-ipc.mdmarkdown9.7 KB
rules/electron/project-structure.ko.mdmarkdown8.8 KB
rules/electron/project-structure.mdmarkdown8.1 KB
rules/electron/renderer.ko.mdmarkdown10.8 KB
rules/electron/renderer.mdmarkdown9.8 KB
rules/electron/security.ko.mdmarkdown10.3 KB
rules/electron/security.mdmarkdown9.2 KB
rules/electron/testing.ko.mdmarkdown5.7 KB
rules/electron/testing.mdmarkdown5.0 KB
rules/expo/data-state-and-boundaries.ko.mdmarkdown4.7 KB
rules/expo/data-state-and-boundaries.mdmarkdown4.3 KB
rules/expo/native-platform-and-security.ko.mdmarkdown8.2 KB
rules/expo/native-platform-and-security.mdmarkdown7.5 KB
rules/expo/performance.ko.mdmarkdown11.2 KB
rules/expo/performance.mdmarkdown10.1 KB
rules/expo/project-structure.ko.mdmarkdown13.4 KB
rules/expo/project-structure.mdmarkdown13.2 KB
rules/expo/routing-and-navigation.ko.mdmarkdown8.6 KB
rules/expo/routing-and-navigation.mdmarkdown8.0 KB
rules/expo/testing-and-validation.ko.mdmarkdown5.1 KB
rules/expo/testing-and-validation.mdmarkdown4.8 KB
rules/hono/conventions.ko.mdmarkdown3.7 KB
rules/hono/conventions.mdmarkdown3.5 KB
rules/hono/database.ko.mdmarkdown11.7 KB
rules/hono/database.mdmarkdown10.8 KB
rules/hono/errors.ko.mdmarkdown3.9 KB
rules/hono/errors.mdmarkdown3.7 KB
rules/hono/handlers.ko.mdmarkdown2.5 KB
rules/hono/handlers.mdmarkdown2.2 KB
rules/hono/middleware.ko.mdmarkdown3.3 KB
rules/hono/middleware.mdmarkdown3.0 KB
rules/hono/openapi.ko.mdmarkdown11.7 KB
rules/hono/openapi.mdmarkdown10.9 KB
rules/hono/performance.ko.mdmarkdown8.9 KB
rules/hono/performance.mdmarkdown8.0 KB
rules/hono/platform.ko.mdmarkdown5.0 KB
rules/hono/platform.mdmarkdown4.7 KB
rules/hono/project-structure.ko.mdmarkdown10.4 KB
rules/hono/project-structure.mdmarkdown9.9 KB
rules/hono/routes.ko.mdmarkdown6.9 KB
rules/hono/routes.mdmarkdown6.6 KB
rules/hono/testing-rpc.ko.mdmarkdown5.6 KB
rules/hono/testing-rpc.mdmarkdown5.2 KB
rules/hono/validation.ko.mdmarkdown3.7 KB
rules/hono/validation.mdmarkdown3.5 KB
rules/lynx/native-and-platform.ko.mdmarkdown11.4 KB
rules/lynx/native-and-platform.mdmarkdown10.7 KB
rules/lynx/performance.ko.mdmarkdown11.6 KB
rules/lynx/performance.mdmarkdown10.6 KB
rules/lynx/project-structure.ko.mdmarkdown10.2 KB
rules/lynx/project-structure.mdmarkdown9.6 KB
rules/lynx/testing.ko.mdmarkdown7.0 KB
rules/lynx/testing.mdmarkdown6.4 KB
rules/lynx/threading.ko.mdmarkdown13.0 KB
rules/lynx/threading.mdmarkdown12.0 KB
rules/lynx/ui-and-data.ko.mdmarkdown11.8 KB
rules/lynx/ui-and-data.mdmarkdown10.8 KB
rules/nextjs/data-fetching.ko.mdmarkdown9.9 KB
rules/nextjs/data-fetching.mdmarkdown9.3 KB
rules/nextjs/db.ko.mdmarkdown8.1 KB
rules/nextjs/db.mdmarkdown7.3 KB
rules/nextjs/execution-model.ko.mdmarkdown5.0 KB
rules/nextjs/execution-model.mdmarkdown4.5 KB
rules/nextjs/hooks.ko.mdmarkdown5.8 KB
rules/nextjs/hooks.mdmarkdown5.3 KB
rules/nextjs/performance.ko.mdmarkdown12.5 KB
rules/nextjs/performance.mdmarkdown11.2 KB
rules/nextjs/platform.ko.mdmarkdown7.7 KB
rules/nextjs/platform.mdmarkdown7.0 KB
rules/nextjs/project-structure.ko.mdmarkdown9.4 KB
rules/nextjs/project-structure.mdmarkdown9.0 KB
rules/nextjs/route-handlers.ko.mdmarkdown4.7 KB
rules/nextjs/route-handlers.mdmarkdown4.3 KB
rules/nextjs/routes.ko.mdmarkdown5.0 KB
rules/nextjs/routes.mdmarkdown4.6 KB
rules/nextjs/server-actions.ko.mdmarkdown7.1 KB
rules/nextjs/server-actions.mdmarkdown6.4 KB
rules/nextjs/services.ko.mdmarkdown5.8 KB
rules/nextjs/services.mdmarkdown5.5 KB
rules/nextjs/validation.ko.mdmarkdown2.2 KB
rules/nextjs/validation.mdmarkdown2.3 KB
rules/rust/cli.ko.mdmarkdown13.6 KB
rules/rust/cli.mdmarkdown12.0 KB
rules/rust/crate-layout.ko.mdmarkdown11.4 KB
rules/rust/crate-layout.mdmarkdown10.1 KB
rules/rust/errors-and-logging.ko.mdmarkdown13.0 KB
rules/rust/errors-and-logging.mdmarkdown11.6 KB
rules/rust/mcp-server.ko.mdmarkdown15.2 KB
rules/rust/mcp-server.mdmarkdown13.8 KB

references/official/hono/hono-docs.md

View on GitHub
# Hono Official Docs Summary

last_verified_at: 2026-11-07

## Contents

- Stable package snapshot
- Confirmed points from official docs
- How this affects the skill
- Sources

## Stable package snapshot

Verified from npm registry metadata and the cited release notes on 2026-11-07. These are evidence snapshots, not automatic upgrade targets.

| Package | Stable | Compatibility observed |
|---|---:|---|
| `hono` | 4.13.17 | Node engine `>=16.9.0` in the core package; registry `latest` is 4.13.17 and 4.13.16 remains the security floor |
| `@hono/node-server` | 2.1.6 | Node `>=20`, Hono `^4 || ^5.0.0-0` |
| `@hono/zod-validator` | 0.9.1 | Hono `>=4.11.2`, Zod `^3.25.0 || ^4.0.0` |
| `@hono/standard-validator` | 0.4.1 | Hono `>=4.11.2`, Standard Schema `^1.0.0` |
| `@hono/zod-openapi` | 1.6.3 | Hono `>=4.10.0`, Zod `^4.0.0` only |
| `@hono/swagger-ui` | 0.6.2 | Hono `>=4.0.0` |
| `hono-openapi` | 1.5.0 | Third-party; Hono `^4.11.2` plus Standard Schema peers |

Sources: [npm registry: hono](https://registry.npmjs.org/hono), [npm registry: `@hono/node-server`](https://registry.npmjs.org/@hono/node-server), [Hono middleware repository](https://github.com/honojs/middleware), [`@hono/node-server`](https://github.com/honojs/node-server), [`hono-openapi`](https://github.com/rhinobase/hono-openapi)

Not adopted: `hono` 5.0.0-rc.1 sits on the `next` tag and `drizzle-orm` 1.0.0-rc.x is a release candidate. Where this skill names a v5 behavior it records a removal that already exists as a v4 deprecation; no release-candidate API is presented as current.

Installed manifests and lockfiles win for implementation. Re-check registry metadata before changing dependencies after the verification date.

Use this reference when the core skill or rule files need an official-doc check.

## Confirmed points from official docs

1. Best practices favor smaller apps and `app.route()` composition, and explicitly say not to make controllers when possible.
Source: [Best Practices](https://hono.dev/docs/guides/best-practices)

2. `createFactory()`, `createHandlers()`, and `createApp()` exist to preserve types when extracting handlers and middleware. `createFactory()` also accepts `defaultAppOptions` and `initApp`.
Source: [Factory Helper](https://hono.dev/docs/helpers/factory)

3. `Context` is instantiated per request. It can hold request-scoped values, headers, and status, and typed `Variables` should be supplied through app generics when using `c.set()` / `c.get()`.
Source: [Context API](https://hono.dev/docs/api/context)

4. Middleware and handlers execute in registration order. Fallback and catch-all placement therefore matters.
Source: [Routing API](https://hono.dev/docs/api/routing), [Middleware Guide](https://hono.dev/docs/guides/middleware)

5. Hono validation is middleware-based. The docs recommend using a third-party validator, and the official ecosystem supports both `@hono/zod-validator` and `@hono/standard-validator`.
Source: [Validation Guide](https://hono.dev/docs/guides/validation)

6. `HTTPException.getResponse()` is not aware of `Context`; if headers were already set on `Context`, a new response must preserve them explicitly.
Source: [HTTPException API](https://hono.dev/docs/api/exception)

7. `testClient()` only infers route types correctly when routes are defined through chained methods directly on the `Hono` instance whose type is exported.
Source: [Testing Helper](https://hono.dev/docs/helpers/testing)

8. Larger-app RPC composition needs care to preserve type inference, and typed clients depend on stable `AppType` or sub-app exports.
Source: [RPC Guide](https://hono.dev/docs/guides/rpc)

9. `app.request()` supports request/response testing, and Hono also provides typed testing helpers for route contracts.
Source: [Testing Guide](https://hono.dev/docs/guides/testing), [Testing Helper](https://hono.dev/docs/helpers/testing)

10. `@hono/zod-openapi` uses `OpenAPIHono`, `createRoute()`, `app.openapi()`, and `app.doc()` / `app.doc31()` to generate OpenAPI documents from route schemas.
Source: [Zod OpenAPI Example](https://hono.dev/examples/zod-openapi), [`@hono/zod-openapi` README](https://github.com/honojs/middleware/tree/main/packages/zod-openapi)

11. `hono-openapi` supports middleware-driven OpenAPI generation with `describeRoute()`, `validator()`, `resolver()`, and `openAPIRouteHandler()` for multiple validator ecosystems. From 1.3.2 a `validator()` route gets a 400 validation response without manual documentation, and 1.4.0 resolves `resolver()` schemas in headers.
Source: [Hono OpenAPI Example](https://hono.dev/examples/hono-openapi), [`hono-openapi` releases](https://github.com/rhinobase/hono-openapi/releases)

12. `@hono/swagger-ui` serves Swagger UI from a Hono route and should point at a generated spec endpoint; it does not generate the spec by itself. 0.6.2 escapes the title and string options embedded in the generated page.
Source: [Swagger UI Example](https://hono.dev/examples/swagger-ui), [`@hono/swagger-ui` README](https://github.com/honojs/middleware/tree/main/packages/swagger-ui)

13. OpenAPI operations should define responses and reusable components explicitly; security schemes belong under `components.securitySchemes`, and examples can be reusable components.
Source: [OpenAPI Specification 3.1.0](https://spec.openapis.org/oas/v3.1.0.html), [Swagger Authentication Docs](https://swagger.io/docs/specification/v3_0/authentication/), [Swagger `$ref` Docs](https://swagger.io/docs/specification/v3_0/using-ref/), [Swagger Examples Docs](https://swagger.io/docs/specification/v3_0/adding-examples/)

14. Hono environment bindings are typed through app generics and accessed with `c.env`. The Cloudflare Workers docs include D1 and other bindings as part of the `Bindings` model, and the Factory Helper docs show an `initApp` example that creates a Drizzle D1 database from `c.env` and stores it in typed `Variables`.
Source: [Context API](https://hono.dev/docs/api/context), [Cloudflare Workers](https://hono.dev/docs/getting-started/cloudflare-workers), [Factory Helper](https://hono.dev/docs/helpers/factory)

15. The root app provides `use`, `route`, `basePath`, `notFound`, and `onError`; `notFound` is called only from the top-level app, while route-level `onError` handlers take priority over a parent handler.
Source: [App API](https://hono.dev/docs/api/hono)

16. Middleware executes in registration order and typed variables accumulate across chained middleware. Shared middleware placement therefore affects both behavior and inferred context.
Source: [Middleware Guide](https://hono.dev/docs/guides/middleware)

17. Hono is Web-Standards based and supports multiple runtimes, while Node.js runs through `@hono/node-server`. A runtime-neutral app plus separate adapter entrypoint is a Hypercore portability convention grounded in those facts, not an official required folder layout.
Source: [Hono repository](https://github.com/honojs/hono), [Node.js Guide](https://hono.dev/docs/getting-started/nodejs), [`@hono/node-server`](https://github.com/honojs/node-server)

18. `hono` 4.13.16 is the security floor. It fixes, in one release, `mount()` / `app.mount()` forwarding a path that bypasses middleware scoped inside the mount prefix, `RegExpRouter` (and therefore the default `SmartRouter`) skipping wildcard middleware for some route patterns and for paths with an encoded line terminator, `validator('form')` skipping `multipart/form-data` validation when extra parameters such as `charset` are present, `css` HTML injection through a closing tag split across template parts, and `csrf()` not checking `text/ping` requests. Custom patterns that can match the empty string, such as `{[0-9]*}`, now throw `UnsupportedPathError`, and build-time `PreparedRegExpRouter` data must be regenerated on upgrade.
Source: [`hono` v4.13.16 release](https://github.com/honojs/hono/releases/tag/v4.13.16)

19. Runtime adapters are separate packages: `@hono/bun`, `@hono/deno`, `@hono/cloudflare-workers`, `@hono/aws-lambda`, `@hono/lambda-edge`, `@hono/netlify`, `@hono/vercel`, and `@hono/service-worker`. `hono/<adapter>` still works in v4 but is deprecated and will be removed in v5. `hono/cloudflare-pages` is deprecated without a replacement package; Cloudflare recommends Workers with static assets.
Source: [`hono` v4.13.10 release](https://github.com/honojs/hono/releases/tag/v4.13.10), [Cloudflare Pages guide](https://hono.dev/docs/getting-started/cloudflare-pages)

20. `app.mount()` is deprecated in v4 and removed in v5. The replacement is the Mount middleware: `import { mount } from 'hono/mount'`, registered as `app.all('/prefix/*', mount(handler))`. The mounted application is called as `handler(request, c.env, c.executionCtx)`, and by default receives a `Request` whose matched path prefix has been removed; `optionHandler` and `replaceRequest` change those arguments and that request.
Source: [App API](https://hono.dev/docs/api/hono), [Mount Middleware](https://hono.dev/docs/middleware/builtin/mount), [`hono` v4.13.13 release](https://github.com/honojs/hono/releases/tag/v4.13.13)

21. `methodNotAllowed({ app })` from `hono/method-not-allowed` returns `405 Method Not Allowed` with an `Allow` header when the path matches a registered route but the method does not. Without this middleware Hono returns `404 Not Found` for that case.
Source: [Method Not Allowed Middleware](https://hono.dev/docs/middleware/builtin/method-not-allowed)

22. The HTTP QUERY method is first-class: `app.query()` registers a handler, the Cache middleware caches QUERY responses with a body digest in the key, ETag handles conditional QUERY requests, and CORS defaults to `GET, HEAD, PUT, POST, DELETE, PATCH, QUERY`. The internal cache key format changed for all methods, including GET: entries are stored under `/.hono/cache?__hono_cache_key=...`, so code that purges by the original URL must be updated.
Source: [`hono` v4.13.0 release](https://github.com/honojs/hono/releases/tag/v4.13.0), [Routing API](https://hono.dev/docs/api/routing)

23. `serveStatic` rejects request paths that still contain `%` after decoding, and `allowPercentInPath: true` restores serving files whose names contain a literal `%`. It also serves only `GET` and `HEAD`, and respects `Accept-Encoding` q-values for precompressed files.
Source: [`hono` v4.13.11 release](https://github.com/honojs/hono/releases/tag/v4.13.11), [`hono` v4.13.14 release](https://github.com/honojs/hono/releases/tag/v4.13.14)

24. `validator('form')` handles `multipart/form-data` with extra parameters from 4.13.16. `@hono/standard-validator` 0.4.0 adds `flattenErrors` for form and field error sorting, and 0.4.1 removes the `cookie` header from the default 400 body of `header` validation.
Source: [`hono` v4.13.16 release](https://github.com/honojs/hono/releases/tag/v4.13.16), [`@hono/standard-validator` releases](https://github.com/honojs/middleware/releases)

25. `getPath()` cannot be combined with `strict: false`; the strict default stays `true`.
Source: [`hono` v4.13.14 release](https://github.com/honojs/hono/releases/tag/v4.13.14)

26. `@hono/zod-openapi` 1.6.x: a JSON or form body whose `Content-Type` matches none of the route's declared media types is rejected with `415 Unsupported Media Type` instead of validating an empty object; `request.body.required` defaults to `false`, so an absent body reaches the handler with `c.req.valid('json')` as `{}`, while `required: true` fails with `400`; `get()`, `post()`, and `use()` return the `Hono` type, so `$()` or `HonoToOpenAPIHono` restores `OpenAPIHono`; `defineOpenAPIRoute()` plus `openapiRoutes([...] as const)` registers batches; `createRoute()` accepts `method: 'query'` from 1.6.0.
Source: [`@hono/zod-openapi` README](https://github.com/honojs/middleware/tree/main/packages/zod-openapi), [`@hono/zod-openapi` releases](https://github.com/honojs/middleware/releases)

27. RPC client pitfalls: path parameters and query values must be passed as `string`; a handler that returns a `.then()` chain directly loses its response type and the client infers `unknown`; `$path()` returns a typed path string without the origin; module augmentation of `NotFoundResponse` lets `c.notFound()` carry a typed 404; compiling a client module with the server app (`hcWithType`) removes per-call type calculation.
Source: [RPC Guide](https://hono.dev/docs/guides/rpc)

28. `ContextVariableMap` adds types globally to all contexts, regardless of whether the middleware that sets the variable has actually run, so `c.get()` can look type-safe while returning `undefined` at runtime. Augmentation is appropriate only for a variable set by app-wide middleware.
Source: [Context API](https://hono.dev/docs/api/context)

29. WebSocket support is built into `@hono/node-server`: install `ws`, create a `WebSocketServer` with `{ noServer: true }`, and pass it to `serve()` as `websocket: { server: wss }` while the route uses `upgradeWebSocket` from `@hono/node-server`. `@hono/node-ws` is deprecated. The package requires Node `>=20`; the Node.js guide page still lists older minimums, so the package manifest wins.
Source: [Node.js Guide](https://hono.dev/docs/getting-started/nodejs), [`@hono/node-server` README](https://github.com/honojs/node-server)

## How this affects the skill

- Hypercore route composition rules/hono are grounded in official `app.route()` and factory guidance.
- Hypercore validation rules/hono should not invent a custom validation surface before checking the existing repo standard, and they inherit the 4.13.16 form-validation floor.
- Hypercore error handling rules/hono must not claim `HTTPException.getResponse()` preserves context-set headers automatically.
- Hypercore testing and RPC rules/hono must protect chained app typing instead of treating detached registration as harmless.
- Hypercore OpenAPI rules/hono should keep runtime validation, typed RPC responses, and generated OpenAPI responses aligned, including the 415 and `body.required` outcomes.
- Swagger UI exposure is a platform/security decision separate from spec generation.
- Large apps should compose route modules, typed clients, and OpenAPI metadata from the same app boundary to avoid drift.
- Database bindings and request-scoped database variables should be typed through `Bindings` / `Variables`, while route modules should stay independent from provider-specific setup.
- Adapter imports belong in `@hono/*` packages, and `app.mount()` migrations belong to the Mount middleware, so neither `hono/<adapter>` nor `app.mount()` is accepted as new code.

## Sources

> Checked 2026-11-07. The `hono` row was refreshed against the npm registry; 4.13.16 stays the documented security floor.

| Claim | Source |
|---|---|
| The package versions and compatibility ranges in the snapshot table above | the npm registry and repository URLs listed beside that table |
| The release-specific behavior in points 18-26 | the `honojs/hono` and `honojs/middleware` release pages linked on each point |
| The official Hono and OpenAPI behavior recorded in points 1-17 and 27-29 | the inline `Source:` links on each numbered point above |
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall