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/project-structure.md

View on GitHub
# Project Structure and Ownership

> Read this rule for folder design, app composition ownership, feature growth, monorepos, or structural refactors. Official Hono facts are summarized in [`../../references/official/hono/hono-docs.md`](../../references/official/hono/hono-docs.md); the layouts below are Hypercore conventions unless marked otherwise.

## 1. Choose a profile from repository evidence

Inspect the package/runtime, source roots, entrypoints, route mounts, aliases, workspace boundaries, generated files, database and migration configuration, OpenAPI generation, tests, and current import graph. Preserve a coherent brownfield layout unless a touched boundary is unsafe or blocks the requested change.

Use the smallest profile that gives every dependency one clear owner:

| Profile | Use when | Add now |
|---|---|---|
| Compact | A small API with a few routes and little reusable domain or persistence logic | Runtime entry, `app.ts`, flat routes, only evidenced shared support |
| Product | Several domains, contributors, validators, persistence workflows, generated API docs, or typed clients | Domain route folders, service/repository boundaries, shared middleware and contract owners |
| Workspace | Multiple deployables or separately built clients consume server contracts | Product structure inside the server package plus a compiled contract package when justified |

Do not pre-create every directory. Promote a folder only when it has a distinct owner, dependency rule, or build/runtime contract. Empty layers and one-file pass-through abstractions are not scalability.

## 2. Ownership and dependency direction

```text
runtime entry -> app composition -> route module -> service/use case -> repository/client -> database/external system
```

| Concern | Default owner | Must not own |
|---|---|---|
| Runtime startup and adapter APIs | `runtime/`, `server.ts`, `worker.ts`, or configured entry | Domain routes or persistence policy |
| Root middleware, errors, not-found, version prefixes, route mounts | `app.ts` or one `routes/index.ts` mount table | Feature business logic |
| HTTP method/path, validation, auth gate, response shaping | `routes/<domain>/` | ORM queries, migrations, provider SDK details |
| Business decisions and multi-step transactions | `services/<domain>/` or feature-local `service.ts` | Hono `Context`, cookies, headers, raw request parsing |
| Queries and external SDK adaptation | `repositories/<domain>/`, `clients/<provider>/` | HTTP response shaping or route registration |
| Connection lifecycle, ORM schema, migration configuration | `database/`, configured schema/migration roots | Request routing |
| Shared API components and generated spec composition | `openapi/` and the app composition boundary | Duplicated feature operation definitions |

Dependencies point rightward/downward. Lower layers do not import Hono transport types. Feature route modules do not import another feature's route module; cross-feature workflows meet in a service/use case or a deliberately shared contract.

## 3. Compact layout

```text
src/
├── app.ts                    # runtime-neutral Hono composition and exported app type
├── server.ts                 # Node/Bun adapter; use worker.ts or index.ts when configured
├── lib/
│   └── create-app.ts         # only when shared Env/factory typing is needed
├── middleware/
│   └── request-id.ts         # only genuinely cross-cutting middleware
└── routes/
    ├── health.ts             # tiny operational endpoint
    └── users.ts              # small chained sub-app
```

A compact route may call a small pure helper directly. Add a service or repository only when business decisions, reuse, persistence, transactions, or external SDK behavior justify the boundary.

## 4. Product layout

```text
src/
├── app.ts                    # sole root composition and exported AppType surface
├── runtime/
│   ├── node.ts               # create only for supported adapters
│   └── worker.ts
├── config/
│   └── env.ts                # validated runtime configuration
├── middleware/
│   ├── auth.ts
│   └── request-id.ts
├── routes/
│   ├── index.ts              # optional sole mount table; do not duplicate app.ts ownership
│   ├── health.ts
│   └── users/
│       ├── index.ts          # chained usersApp export
│       ├── handlers.ts       # extracted with typed factory when needed
│       ├── schemas.ts        # request/response schemas
│       ├── routes.ts         # optional OpenAPI route definitions
│       ├── middleware.ts     # users-only middleware
│       └── users.test.ts
├── services/
│   └── users/
│       └── create-user.ts
├── repositories/
│   └── users/
│       └── users-repository.ts
├── clients/
│   └── mail/
│       └── mail-client.ts
├── database/
│   ├── client.ts
│   ├── schema.ts
│   └── types.ts
└── openapi/
    ├── components.ts
    └── registry.ts

drizzle/                     # generated migrations only when drizzle.config.ts points here
└── migrations/
```

The tree is illustrative; configured source, schema, and migration roots win.

## 5. Feature growth thresholds

| Pressure | Structural response |
|---|---|
| One tiny operational endpoint | Keep one route file |
| Validation or several handlers appear | Promote to `routes/<domain>/` and colocate route-only schemas/handlers |
| Business behavior is reused or independently testable | Add a feature-local or root `services/<domain>/` owner, following the existing repository pattern |
| Persistence/provider calls appear | Add a repository/client boundary; routes must not import DB tables, drivers, or provider SDKs |
| Two domains reuse a transport-agnostic contract | Promote that contract to a purpose-named shared owner; do not create a generic dumping-ground `utils/` |
| Multiple domains reuse middleware or OpenAPI components | Promote only the reused primitive to `middleware/` or `openapi/` |
| A second deployable consumes server RPC types | Consider a compiled contract package; do not deep-import server source across package boundaries |

Do not split by file count alone. A cohesive feature can remain colocated; a large file with mixed transport, business, and persistence ownership must be separated even if used once.

## 6. Composition and type surface

Official Hono guidance supports `app.route()` for larger applications and requires careful chaining for RPC inference. Keep exactly one obvious root composition path:

```ts
const routes = app
  .route('/users', usersApp)
  .route('/billing', billingApp)

export type AppType = typeof routes
export default app
```

- Put `/api` and version prefixes at the root mount or `basePath()` boundary.
- Register root middleware before affected routes and fallbacks last.
- Keep runtime startup separate from the reusable app so `app.request()` tests do not boot a server.
- Derive RPC clients, `testClient`, and generated OpenAPI from the same composed surface when the repository uses them.
- For very large RPC surfaces, prefer compiled declarations or deliberately split clients after measuring type-check/IDE pressure; never sacrifice the canonical server contract silently.

## 7. Workspace layout

```text
apps/
├── api/                     # Product profile; owns runtime and implementation
└── web/                     # consumes a stable client/contract package
packages/
└── api-contract/            # emitted types/client only when independently built and consumed
```

Keep `hono` versions compatible across producer and consumer, enable TypeScript `strict`, and use project references or emitted declarations according to the existing build system. A client package must not export database schema, secrets, runtime bindings, or server-only implementation modules.

## 8. Brownfield migration

1. Map actual entrypoints, mounts, imports, generated files, and configured roots.
2. Identify ownership violations and cycles before moving files.
3. Preserve public paths, middleware order, error behavior, `AppType`, OpenAPI output, and migration provenance.
4. Move one vertical slice at a time and update imports/configuration atomically.
5. Run focused route/request tests and type checks after each slice; keep the candidate only when behavior and guards pass.
6. Record untouched Hypercore-only drift as backlog when broad movement would exceed the request. Safety, validation, typing, persistence, and runtime-boundary violations in touched code still block.

This is a bounded migration loop: feedback is focused tests/type checks plus import-boundary inspection; the guard is unchanged public behavior and contracts; the maximum iterations equal the planned slices; discard or revert a slice that fails its guard before continuing.

## 9. Structural verification

- Confirm one runtime-neutral app and one obvious mount table.
- Confirm every route has an unambiguous owner and fallback order is preserved.
- Search routes/handlers for imports from DB clients, ORM tables, migrations, drivers, and provider SDKs.
- Search services/repositories for Hono `Context` and raw request/response dependencies.
- Check aliases, package exports, generated-file ownership, and schema/migration paths against configuration.
- Run type checking plus focused `app.request()` or `testClient()` tests for moved routes.
- When RPC/OpenAPI is present, verify the exported composed type/spec still includes representative routes and error shapes.
- Report untested runtimes, clients, migrations, or generated artifacts explicitly; do not infer success from file layout alone.

## Sources

> Checked 2026-11-04. No external source outside this package's own references informed this file; official Hono behavior is delegated to [`references/official/hono/hono-docs.md`](../../references/official/hono/hono-docs.md), verified 2026-11-04.
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: 469kUpdated 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: 469kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 469kUpdated 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