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

rules/hono/openapi.md

View on GitHub
# OpenAPI and Swagger

> Treat generated API documentation as a typed contract boundary

---
## Stable Package Baseline

As verified on 2026-11-04: `@hono/zod-openapi` 1.6.3 requires Hono `>=4.10.0` and Zod `^4.0.0` only; `@hono/swagger-ui` 0.6.2 requires Hono `>=4`; third-party `hono-openapi` 1.5.0 requires Hono `^4.11.2` and Standard Schema ecosystem peers. Lockfile and peer compatibility must be checked before choosing a path.

- Prefer `@hono/zod-openapi` for a Zod 4 route-first API. It does not accept Zod 3, unlike `@hono/zod-validator`.
- Preserve an established `hono-openapi` surface rather than migrating generators incidentally; it is third-party, not an official HonoJS package. From 1.3.2 a `validator()` route gets its 400 validation response automatically, so do not document it twice.
- Do not combine undocumented plain `Hono` children and expect `OpenAPIHono` to discover their metadata.
- Schema every actual success and error status. Keep central error envelopes synchronized with runtime and RPC global response types.
- Generate the document in a deterministic check, validate references and unique `operationId` values, and diff the artifact when it is committed.
- Gate spec/UI exposure separately. A hidden UI does not make a public JSON spec private, and Swagger UI does not generate the spec.

## Core Rule

When a Hono API publishes OpenAPI/Swagger docs, route changes must update the generated contract in the same change. The contract must describe the same requests, responses, status codes, security, and examples that the runtime route actually supports.

Database rows are not automatically public API DTOs. If persistence changes affect a documented response, map ORM rows to the public response schema before publishing or codegen.

## Approved Generation Paths

| Repo shape | Preferred path |
|------|------|
| Zod-first routes | `@hono/zod-openapi` with `OpenAPIHono`, `createRoute()`, `app.openapi()`, and `app.doc()` |
| Mixed validator or Standard Schema repos | `hono-openapi` with `describeRoute()`, `resolver()`, `validator()`, and `openAPIRouteHandler()` |
| UI only | `@hono/swagger-ui` mounted against the generated spec endpoint |

Do not switch generators across a whole app unless the user explicitly asked for that migration.

## Folder Structure

```text
src/
├── app.ts
├── openapi/
│   ├── components.ts
│   ├── errors.ts
│   └── registry.ts
└── routes/
    └── users/
        ├── index.ts
        ├── routes.ts
        ├── schemas.ts
        └── handlers.ts
```

- Keep shared components, security schemes, examples, and error envelopes in `src/openapi/` when more than one feature reuses them.
- Keep feature operation metadata near the feature route it documents.
- Compose the canonical spec at the app boundary, not by copying generated fragments by hand.
- Use a stable spec path such as `/doc` or `/openapi.json`.
- Serve Swagger UI from a separate path such as `/ui`, `/docs`, or an admin route.

## Operation Metadata Checklist

Every documented operation should define:

- Stable `operationId`
- Consistent `tags`
- Path params, query params, headers, and request body schemas
- Success responses with status-specific JSON schemas
- Expected error responses such as 400, 401, 403, 404, 409, 422, and 500 when applicable
- Auth requirements through reusable `components.securitySchemes`
- Request and response examples that match the schema
- Deprecation or hide metadata when an endpoint should not be public

## Contract Drift Rules

| Drift | Rule |
|------|------|
| Handler reads validated data not represented in OpenAPI | BLOCKED. Add the request schema or stop documenting the route. |
| OpenAPI lists a response status the handler never returns | WARNING. Fix the handler or docs before codegen/client publication. |
| Handler returns status-specific payloads but docs only show a generic response | WARNING. Add explicit response schemas. |
| OpenAPI response schema exposes raw ORM rows with internal or sensitive fields | BLOCKED. Add DTO mapping and document the public response contract. |
| Shared auth middleware exists but OpenAPI omits security requirements | BLOCKED for public or partner-facing docs. |
| Swagger UI is public by accident | BLOCKED. Add auth/admin/dev gating or document the public-docs decision. |
| Generated spec fails linting or has broken `$ref` values | BLOCKED before publishing. |
| A documented JSON or form body omits `415` while clients can send an undeclared `Content-Type` | WARNING. Document the 415 outcome or narrow the accepted media types. |
| A route declares the body optional but the handler assumes every field exists | BLOCKED. Set `body.required: true` or validate the absent-body case explicitly. |

## Request Body Contract

`@hono/zod-openapi` 1.6.x validates only JSON and form media types. Two behaviors belong in the documented contract:

- A request body whose `Content-Type` matches none of the route's declared media types is rejected with `415 Unsupported Media Type`. Earlier versions validated an empty object instead, so a client that sent the wrong header reached the handler.
- `request.body.required` defaults to `false`. A request with no body reaches the handler and `c.req.valid('json')` is `{}`. Set `required: true` when the body is mandatory; then an absent body fails with `400`.

Declare every accepted media type in `createRoute({ request: { body: { content: { ... } } } })`, and mirror both outcomes in the operation's response list when the client depends on them.

## Large-App Pattern

For `@hono/zod-openapi`, prefer feature-local route definitions and app-level registration. `openapiRoutes()` accepts `defineOpenAPIRoute()` results, which pair a `route` with its `handler`; a bare `createRoute()` object is not registrable this way.

```ts
// routes/users/routes.ts
import { createRoute, defineOpenAPIRoute } from '@hono/zod-openapi'

export const listUsersRoute = defineOpenAPIRoute({
  route: createRoute({
    method: 'get',
    path: '/',
    operationId: 'listUsers',
    tags: ['Users'],
    responses: {
      200: {
        description: 'Users returned',
        content: {
          'application/json': {
            schema: usersResponseSchema,
          },
        },
      },
    },
  }),
  handler: async (c) => {
    return c.json({ users: await listUsers() }, 200)
  },
})

export const userRoutes = [listUsersRoute] as const
```

```ts
// app.ts
const app = new OpenAPIHono()

app.openapiRoutes([...userRoutes, ...billingRoutes] as const)
app.doc('/doc', { openapi: '3.0.0', info: { title: 'API', version: '1.0.0' } })
app.get('/ui', swaggerUI({ url: '/doc' }))
```

When an RPC app grows past a few dozen routes, split it into small `OpenAPIHono` instances and mount them with `.route()`. A long chain of `.openapi()` calls accumulates schema type at every link, so a single giant app slows down `hc` type checking. Routing and OpenAPI output stay the same; only the accumulated type work shrinks.

```ts
const users = new OpenAPIHono().openapi(getUserRoute, getUserHandler)
const posts = new OpenAPIHono().openapi(getPostRoute, getPostHandler)

export const appRoutes = new OpenAPIHono().route('/', users).route('/', posts)
```

`get()`, `post()`, and `use()` return the `Hono` type rather than `OpenAPIHono`, so a chain that mixes them loses `.openapi()`. Wrap the result with `$()` or convert the type with `HonoToOpenAPIHono`.

```ts
import { $, OpenAPIHono } from '@hono/zod-openapi'

const app = $(new OpenAPIHono().use(requestIdMiddleware))
app.openapi(route, handler)
```

For `hono-openapi`, prefer route-local `describeRoute()` metadata and a single app-level `openAPIRouteHandler()` endpoint.

## Version and Package Caveats

- `@hono/zod-openapi` examples commonly show `app.doc()` with OpenAPI 3.0; use `app.doc31()` / `getOpenAPI31Document()` only when the project needs OpenAPI 3.1 output and the toolchain supports it. `getOpenAPI31Document()` takes generator options as its second argument, such as `unionPreferredType: 'oneOf'`.
- `@hono/zod-openapi` peers on Zod `^4.0.0` only. A repo still on Zod 3 must stay on `hono-openapi` or migrate Zod first; the two validators do not share a Zod major.
- `@hono/swagger-ui` serves UI, not the spec generator. Use `url` for one spec and `urls` for multiple specs. 0.6.2 escapes the title and string options it embeds in the page.
- `persistAuthorization`, `remoteAssets.baseUrl`, UI `version`, and custom HTML are deployment/UI knobs, not spec contract knobs.
- Plain `Hono` sub-apps nested under `OpenAPIHono` may not contribute OpenAPI metadata to the generated spec.
- When mounting nested OpenAPI sub-apps, parent `.route()` path params should use Hono `:param` syntax.
- Keep header schema keys lowercase so Hono validators and OpenAPI generators agree.
- `createRoute({ method: 'query' })` is available from 1.6.0; confirm the generated document's consumers accept a QUERY operation before publishing it.

## Review Checklist

- One generator strategy is used consistently
- Spec endpoint and Swagger UI endpoint are separate and intentional
- Route validators and documented schemas share a source or synchronization rule
- JSON and form bodies declare their media types, and 415 is documented where clients can trigger it
- `body.required` matches what the handler assumes
- Middleware chains that return plain `Hono` are wrapped with `$()` or `HonoToOpenAPIHono` before `.openapi()` is used
- Database row shapes are mapped to public DTO schemas before publication
- Reusable schemas, errors, security schemes, parameters, and examples use `components`
- Operation IDs are stable and unique
- Error responses match central error handling
- RPC `AppType`/typed client shapes do not conflict with generated OpenAPI shapes
- Large RPC surfaces are split across mounted `OpenAPIHono` instances when a single chain slows type checking
- CI or local verification lints, bundles, or validates the generated spec before publication

## Sources

> Checked 2026-11-04.

| Claim | Source |
|---|---|
| `@hono/zod-openapi` 1.6.3, `@hono/swagger-ui` 0.6.2, `hono-openapi` 1.5.0 versions and peer ranges | [npm registry: `@hono/zod-openapi`](https://registry.npmjs.org/@hono/zod-openapi), [npm registry: `@hono/swagger-ui`](https://registry.npmjs.org/@hono/swagger-ui), [npm registry: hono-openapi](https://registry.npmjs.org/hono-openapi) |
| 415 on an undeclared media type, `body.required` default, `$()` / `HonoToOpenAPIHono`, `defineOpenAPIRoute` / `openapiRoutes`, mounted-instance type performance, 3.1 generator options | [`@hono/zod-openapi` README](https://github.com/honojs/middleware/tree/main/packages/zod-openapi) |
| QUERY support in `createRoute()`, 415 fix in 1.6.3, type cost reductions in 1.6.1 and 1.6.2 | [`@hono/zod-openapi` releases](https://github.com/honojs/middleware/releases) |
| `hono-openapi` automatic 400 and header `resolver()` support | [`hono-openapi` releases](https://github.com/rhinobase/hono-openapi/releases) |
| Swagger UI escaping in 0.6.2 | [`@hono/swagger-ui` releases](https://github.com/honojs/middleware/releases) |
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: 468kUpdated 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: 468kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 468kUpdated 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