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

View on GitHub
# Lynx Project Structure

> Read when choosing or changing folders, entry files, `source.entry`, output targets, or the boundary between the bundle and the native host.

## Template tree

The official ReactLynx TypeScript template from `@lynx-js/create-lynx@0.2.1` ships exactly this shape:

```text
.
├── lynx.config.ts          # Rspeedy config, pluginReactLynx, type-check plugin
├── package.json            # scripts: build, dev, preview, test
├── rstest.config.ts        # extends withLynxConfig()
├── tsconfig.json           # strict, isolatedModules, project references
├── tsconfig.node.json      # compiles lynx.config.ts and rstest.config.ts
└── src/
    ├── tsconfig.json       # jsx react-jsx, jsxImportSource @lynx-js/react
    ├── index.tsx           # the only root.render call site
    ├── App.tsx
    ├── App.css
    ├── lynx-env.d.ts       # GlobalProps augmentation
    ├── assets/
    ├── lib/
    ├── useFlappy.ts
    └── __tests__/index.test.tsx
```

The root `tsconfig.json` holds no files of its own; it lists `references` to `tsconfig.node.json` and `./src` and sets `files: []`. Two separate programs, one for config and tests, one for source. Keep that split: the source program needs `jsxImportSource`, the config program needs `node16` resolution.

## Entry file

`src/index.tsx` is the only place that mounts a tree:

```tsx
import { root } from '@lynx-js/react';

import { App } from './App.js';

root.render(<App />);

if (import.meta.webpackHot) {
  import.meta.webpackHot.accept();
}
```

Two details that are easy to get wrong:

- The local import carries `.js` even though the source is `.tsx`. The source program resolves with `moduleResolution: "Bundler"`, but keeping the extension matches the template and survives a later resolution change.
- `import.meta.webpackHot` works because Rspeedy is Rspack-based; the webpack HMR surface is present. Do not replace it with a Vite API.

Everything the app does belongs outside the entry. A second `root.render` in a feature file creates a second tree and breaks the assumption that one bundle has one root.

## `source.entry`

`source.entry` accepts a string, an array of modules, or a record. The default is `'./src/index.js'`, so a TypeScript project must state it.

```ts
// one entry
source: { entry: './src/index.tsx' }

// several entries in one target
source: { entry: { main: './src/index.tsx', settings: './src/settings.tsx' } }

// one entry assembled from several modules
source: { entry: ['./src/polyfills.ts', './src/index.tsx'] }
```

Each entry produces its own `[name].lynx.bundle`. Use several entries when the host loads genuinely different screens as separate bundles, not to reduce a single app's bundle size — that is lazy loading's job, in `rules/lynx/performance.md`.

## Output layout

Production:

```text
dist/
├── [name].lynx.bundle          # both JS layers plus styles in one artifact
├── async/[name].lynx.bundle    # lazy bundles
└── static/
    ├── js/[id].[hash].js
    ├── image/
    └── svg/
```

Development adds readable intermediates under `dist/.rspeedy/[name]/`: `background.js`, `main-thread.js`, `[name].css`, `tasm.json`, `debug-metadata.json`. Those two JS files are the artifact boundary this skill reviews; `DEBUG=rspeedy rspeedy build` keeps them for a production investigation.

A `.lynx.bundle` is one binary artifact holding both layers. That is why an `engineVersion` mistake is a deployment failure rather than a build failure: the bundle is valid, the host is too old.

## Web target

The web output is opt-in. `environments` defaults to `{ lynx: {} }`.

```ts
export default defineConfig({
  environments: { lynx: {}, web: {} },
});
```

The web build emits `dist/main.web.bundle`, embedded through `@lynx-js/web-core`:

```tsx
import '@lynx-js/web-core/client';

export const App = () => (
  <lynx-view style={{ height: '100vh', width: '100vw' }} url="/main.web.bundle" />
);
```

`lynx-view` accepts `url` (required), `globalProps`, `initData`, `browser-config` with `pixelRatio`/`width`/`height`, `transform-vw`, and `transform-vh`, plus the `nativeModulesMap` property and `onNativeModulesCall`. Treat the bundle URL and every native-module URL as network input.

`@lynx-js/web-core` is at 0.26.7 while the engine is 4.2, and no production-readiness statement was found. Report a web target as available but unverified for production rather than recommending it.

## Host embedding boundary

`LynxView` is itself a native view. The host decides its size constraints; Lynx lays out the `<page>` inside. Keep the boundary explicit in the repository:

| Concern | Owner | Where it lives |
|---|---|---|
| Engine dependency version | host app | iOS `pod 'Lynx', '<version>'`; Android `org.lynxsdk.lynx:lynx`; HarmonyOS `@lynx/primjs` artifacts |
| Bundle artifact | frontend build | `dist/[name].lynx.bundle` |
| `initData` and its updates | host app | `LynxView.loadTemplate(meta.initialData)`, `setInitialData`, `MetaData(new TemplateData(...))`, later `updateData`/`updateMetaData` |
| `globalProps` | host app | `lynx.__globalProps`; may be absent or `{}` |
| Native modules | host app registers, bundle calls | `LynxEnv.inst().registerModule(...)`, `[globalConfig registerModule:...]` |
| Module call authorization | host app | per-`LynxView` validator from SDK 3.5 |

When the host lives in the same repository, the engine version in the host dependency must be the value that bounds `engineVersion`. When it does not, record the host floor in the config next to `engineVersion` with its source. A frontend-only repository cannot verify the floor by itself and must say so.

## Folder ownership

For a growing app, keep the entry thin and organize by feature. The official template's flat `src/` is fine for a demo; once there are three or more screens, feature folders beat a global `components/` bucket.

```text
src/
├── index.tsx             # root.render only
├── App.tsx               # top-level composition
├── app/                  # screen composition per route
├── features/<domain>/    # feature components, hooks, host-data mapping
├── shared/
│   ├── ui/               # primitives, no native call
│   ├── native/           # the only NativeModules adapters
│   ├── lynx/             # thread helpers and MainThreadRef utilities
│   └── lib/              # focused utilities
└── types/                # InitData, GlobalProps, IntrinsicElements augmentation
```

Rules that keep this honest:

- A feature imports only `shared`. Two features coordinating is composition in `app/`.
- `shared/native/` is the only folder allowed to import `NativeModules`. Every call there is background-thread only.
- `shared/lynx/` holds the wrapper that pairs `runOnMainThread` with its main-thread function so the pairing is reviewed once.
- Files directly under `src/` stay limited to the entry, the root component, and its styles.

This layout is hypercore-default, not an official Lynx requirement.

## Naming

Follow the project's existing convention. For a new structure prefer kebab-case file names and named exports, except where the framework requires otherwise. A main-thread handler file states the interaction it serves (`header-scroll.main-thread.ts`), because the thread is part of what the file is.

## Checklist

- [ ] The entry is `src/index.tsx`-style, mounts once, and holds no feature logic.
- [ ] `source.entry` is stated explicitly when the project is TypeScript.
- [ ] Every extra entry maps to a screen the host loads separately, not to a size workaround.
- [ ] Production output was inspected as `[name].lynx.bundle` plus `static/`, not as plain JS.
- [ ] The web target is opt-in and reported as available but unverified for production.
- [ ] The engine version in the host project bounds `engineVersion` in `lynx.config.ts`, or the missing host evidence is recorded.
- [ ] `initData`, `globalProps`, and native modules have a named owner on the host side.
- [ ] Features import only `shared`; no feature-to-feature import exists.
- [ ] `NativeModules` appears only under `shared/native/`.

## Sources

> Checked 2026-11-07. These statements restate the package's dated snapshot, `references/official/lynx/lynx-2026-11-07.md`, which cites the Lynx documentation, the `@lynx-js/create-lynx` 0.2.1 tarball, and npm registry metadata read on 2026-11-07.

| Claim | Source |
|---|---|
| Template file set, the entry file, and the `.js` extension on a `.tsx` import | https://registry.npmjs.org/@lynx-js%2Fcreate-lynx/-/create-lynx-0.2.1.tgz |
| `source.entry` accepted forms, default value, and multi-entry behavior | https://lynxjs.org/llms-full.txt (Rspeedy `source.entry` page) |
| Production and development output layout, and `DEBUG=rspeedy rspeedy build` | https://lynxjs.org/rspeedy/output.md, https://lynxjs.org/guide/performance/analysis-performance/analysis-bundle-size.md |
| `environments` defaulting to `{ lynx: {} }`, `dist/main.web.bundle`, and `lynx-view` attributes | https://lynxjs.org/guide/start/integrate-with-existing-apps.md, https://lynxjs.org/llms-full.txt (lynx-view page) |
| CocoaPods, Maven, and HarmonyOS host dependencies, `initData` injection, and native module registration | https://lynxjs.org/guide/start/integrate-with-existing-apps.md, https://lynxjs.org/guide/use-data-from-host-platform.md, https://lynxjs.org/guide/use-native-modules.md |
| `@lynx-js/web-core` 0.26.7 registry state with no production-readiness statement | https://registry.npmjs.org/@lynx-js%2Fweb-core |
| Folder ownership, the `shared/native/` boundary, and the naming convention | this package's convention, not an official Lynx requirement |
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: 470kUpdated 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: 470kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 470kUpdated 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