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/drizzle-docs.md

View on GitHub
# Drizzle Official Docs Summary

last_verified_at: 2026-11-04

## Stable package snapshot

Verified from npm registry metadata and release notes on 2026-11-04:

| Package | Stable |
|---|---:|
| `drizzle-orm` | 0.45.4 |
| `drizzle-kit` | 0.31.11 |

Sources: [npm registry: drizzle-orm](https://registry.npmjs.org/drizzle-orm), [npm registry: drizzle-kit](https://registry.npmjs.org/drizzle-kit), [Drizzle releases](https://github.com/drizzle-team/drizzle-orm/releases)

These versions are maintenance evidence, not permission to upgrade. The installed dialect driver, peer dependencies, config format, and generated migration format must be checked together.

Use this reference when Hono architecture decisions depend on Drizzle ORM, `drizzle-kit`, runtime-specific database drivers, schema files, migrations, or transactions.

## Confirmed points from official docs

1. Drizzle provides a database connection hub with runtime/dialect-specific pages for PostgreSQL, Neon, Cloudflare D1, Turso/libSQL, SQLite, PGLite, Bun SQL, and other drivers. Pick the driver that matches the deployment runtime.
Source: [Database connection](https://orm.drizzle.team/docs/connect-overview)

2. Drizzle schema is declared in TypeScript files. Drizzle Kit reads schema files or folders, so schema declarations should live in a stable, exported location.
Source: [Schema declaration](https://orm.drizzle.team/docs/sql-schema-declaration), [Drizzle config file](https://orm.drizzle.team/docs/drizzle-config-file)

3. `drizzle.config.ts` uses `schema` for the schema file/folder path and `out` for the migration output folder. The default migration output folder is `./drizzle`.
Source: [Drizzle config file](https://orm.drizzle.team/docs/drizzle-config-file), [`drizzle-kit generate`](https://orm.drizzle.team/docs/drizzle-kit-generate)

4. `drizzle-kit generate` creates SQL migrations from Drizzle schema changes. Generated migrations can then be applied with `drizzle-kit migrate`, Drizzle ORM's migration APIs, external tools, or direct SQL execution.
Source: [`drizzle-kit generate`](https://orm.drizzle.team/docs/drizzle-kit-generate), [Migrations](https://orm.drizzle.team/docs/migrations)

5. `drizzle-kit migrate` applies SQL migrations generated by `drizzle-kit generate`, reads the migration folder, checks the migrations log table, runs unapplied SQL, and logs applied migrations.
Source: [`drizzle-kit migrate`](https://orm.drizzle.team/docs/drizzle-kit-migrate)

6. Drizzle's migration docs distinguish database-first and codebase-first workflows. `pull`, `generate`, `push`, `migrate`, `export`, and `check` exist for different workflow needs, so a skill should not force one migration workflow unless the repo already standardizes on it. `drizzle-kit check` verifies the consistency of the generated SQL migration history, which matters when several branches each generate migrations.
Source: [Migrations](https://orm.drizzle.team/docs/migrations), [`drizzle-kit check`](https://orm.drizzle.team/docs/drizzle-kit-check)

7. Drizzle's serverless performance guidance recommends declaring database connections and prepared statements outside handler scope when the runtime can reuse the process.
Source: [Serverless performance](https://orm.drizzle.team/docs/perf-serverless)

8. Cloudflare D1 support uses the D1 Worker binding with `drizzle-orm/d1`; the D1 docs show `drizzle(env.<BINDING_NAME>)` and Wrangler migration configuration with `migrations_dir`.
Source: [Cloudflare D1](https://orm.drizzle.team/docs/connect-cloudflare-d1)

9. Neon support has separate HTTP, WebSocket, and serverless driver paths. The docs state that HTTP is faster for single, non-interactive transactions, while WebSockets are needed for session or interactive transaction support.
Source: [Neon](https://orm.drizzle.team/docs/connect-neon)

10. Drizzle transactions use `db.transaction(async (tx) => ...)`. The docs also show returning values, rollback, nested transactions with savepoints, relational queries inside transactions, and dialect-specific transaction config.
Source: [Transactions](https://orm.drizzle.team/docs/transactions)

11. Relational query building has two generations. Stable 0.x declares relations with `relations()` imported from `drizzle-orm`; `defineRelations()` and Relational Queries v2 belong to `drizzle-orm@rc` and its migration guide. The live relations page is written against the release candidate, so following it on a 0.45.x install asks for APIs that do not exist there.
Source: [Relations v1 to v2](https://orm.drizzle.team/docs/relations-v1-v2), [Relations](https://orm.drizzle.team/docs/relations)

## How this affects the skill

- Hypercore Hono rules/hono should treat Drizzle setup as runtime-specific rather than one universal import path.
- Database client construction belongs in a database/platform boundary, not in each route handler.
- Drizzle schema and migration folders must be discoverable from `drizzle.config.ts`.
- Migration generation/application is operational behavior and should not be silently performed as part of ordinary route edits.
- Transaction boundaries belong at the service/use-case layer; repository helpers that participate in a transaction should accept a `tx` or database dependency.
- Public API DTOs, OpenAPI schemas, and typed RPC response shapes should not be assumed to equal Drizzle row shapes.

## Version and docs caveats

- The Drizzle docs are live and version-sensitive. Re-check exact package versions and import paths against the installed `drizzle-orm` / `drizzle-kit` release before making code changes.
- The rule that repository helpers should accept `tx` is an architectural inference from the Drizzle transaction API shape, not a verbatim official requirement.
- Runtime pages for Neon, D1, Turso/libSQL, and other providers can change as provider SDKs change.
- `drizzle-orm` 1.0.0-rc.x is a release candidate. Its `defineRelations` / Relational Queries v2 API, `EmptyFilter`, and `undefined` filter errors are not stable behavior; this skill records them as upcoming, not adopted.
- `drizzle-kit` 0.31.11 warns about silent migration skips during `check`. Treat that warning as a migration-history defect, not noise.


## Sources

> Checked 2026-11-04.

| Claim | Source |
|---|---|
| The `drizzle-orm` and `drizzle-kit` versions in the snapshot table above | the registry and release URLs listed beside that table |
| The Drizzle behavior recorded in points 1-11 above | the inline `Source:` links on each numbered point above |
| The closing caveats, including the `tx` note that section marks as this package's inference rather than an official requirement | the same Drizzle documentation pages linked in points 1-11; the inference is attributed in that section to this package |
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