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/testing.ko.md

View on GitHub
# Lynx Testing

> test를 추가하거나 검토하고, test runner를 바꾸고, Lynx 변경을 검증됐다고 주장하기 전에 읽습니다.

## Template이 제공하는 것

공식 ReactLynx TypeScript template은 Rstest를 실행합니다.

```ts
// rstest.config.ts
import { withLynxConfig } from '@lynx-js/react/testing-library/rstest-config';
import { defineConfig } from '@rstest/core';

export default defineConfig({
  extends: withLynxConfig(),
});
```

`withLynxConfig()`는 app의 실제 `lynx.config.ts`를 재사용하므로 test가 build와 같은 alias, plugin, `engineVersion`을 봅니다. Test가 app config를 상속하면 안 될 때는 `withDefaultConfig()`가 대안입니다. Template은 `jsdom`과 `@testing-library/jest-dom`도 설치합니다.

`package.json` script는 `build: rspeedy build`, `dev: rspeedy dev`, `preview: rspeedy preview`, `test: rstest run`입니다.

## Testing library

`@lynx-js/react/testing-library`는 `@lynx-js/react` package 안에 `./testing-library` export로 들어 있습니다. React Testing Library를 그대로 반영하며 `render`, `fireEvent`, `screen`을 제공하고, `@lynx-js/testing-environment`로 dual thread를 한 process에서 emulation합니다.

Runner 둘을 지원합니다.

| Runner | 설정 |
|---|---|
| Rstest | `@lynx-js/react/testing-library/rstest-config`의 `withDefaultConfig()` 또는 `withLynxConfig()`를 `extends`에 |
| Vitest | `@lynx-js/react/testing-library/plugins`의 `vitestTestingLibraryPlugin()`을 `plugins`에 |

App test에는 실제 build config를 재사용하는 Rstest와 `withLynxConfig()`를 선호합니다. Vitest는 repository가 이미 그것을 표준으로 삼았을 때만 씁니다.

## Event

Attribute 의미와 맞는 typed event 이름으로 발생시킵니다.

```ts
fireEvent(element, new Event('bindEvent:tap'));
fireEvent(element, new Event('catchEvent:tap'));
fireEvent(element, new Event('capture-bind:tap'));
fireEvent(element, new Event('capture-catch:tap'));

// 흔한 경우의 shorthand
fireEvent.tap(element);
```

Element PAPI를 JSDOM에서 emulation하므로 `@testing-library/jest-dom` matcher가 동작합니다. 그 말은 test가 JavaScript와 element 의미를 증명하고 native rendering은 증명하지 않는다는 뜻입니다. 통과한 test가 device에서 `<list>`가 정확히 recycle되는 것을 증명하지는 않습니다.

## 무엇을 test하는가

화면 또는 feature마다 다음을 둡니다.

1. 주어진 `initData`에서 초기 tree를 확인하는 render test.
2. 화면이 실제로 binding한 handler를 발생시키는 event test.
3. 없거나 일부만 있는 `initData`, 갱신된 `initData`, `globalProps`가 `null` 또는 `{}`인 경우의 host data test.
4. `main-thread:` handler가 있으면 그 handler의 thread test. Directive는 binding을 통해서만 적용되므로 handler를 직접 호출하지 말고 보이는 결과를 확인합니다.
5. `item-key`와 `key`가 일치하고 주어진 data로 row가 render되는지 확인하는 list test.

감추지 말고 밝혀야 하는 test 한계입니다.

- Dual-thread emulation은 JavaScript emulation입니다. PrimJS/JSC 동작 차이, bytecode load, 실제 main-thread timing bug를 증명하지 않습니다.
- Test는 `engineVersion` 호환성을 증명할 수 없습니다. 그건 host version 사실이고 unit test가 아니라 host와 대조해 확인합니다.
- Native module은 test 환경에 없습니다. `NativeModules`가 아니라 `src/shared/native/`의 adapter를 mock합니다. 그래야 mock이 app이 실제로 쓰는 경계에 놓입니다.

## Type checking

Rspeedy는 type check를 하지 않습니다. "Type checking is not performed"가 문서화된 동작이므로 통과한 `rspeedy build`는 type에 대해 아무 말도 하지 않습니다.

명시적으로 연결합니다.

```ts
import { pluginTypeCheck } from '@rsbuild/plugin-type-check';

pluginTypeCheck({ enable: true });
```

공식 template은 이미 `@rsbuild/plugin-type-check`를 포함하고 `pluginTypeCheck()`를 호출합니다.

중요한 TypeScript 설정입니다.

- `isolatedModules: true`가 필요합니다. SWC가 file 단위로 compile하기 때문입니다.
- Source program에 `jsx: "react-jsx"`와 `jsxImportSource: "@lynx-js/react"`가 필요합니다.
- Source는 `moduleResolution: "Bundler"`, config program은 `node16`입니다.
- `strict`, `verbatimModuleSyntax`, `esModuleInterop`, `skipLibCheck`가 template default입니다.

`isolatedModules`가 켜져 있으므로 `export type { X }`와 `import type`은 style 선택이 아닙니다. 표시하지 않은 type re-export는 build를 실패시킵니다.

## Check 순서

1. Project 자체 command로 type check합니다(`tsc -b`로 referenced program을 검사하거나 repo가 정의한 script).
2. Unit과 component test에 `rstest run`을 실행합니다.
3. `rspeedy build`로 production bundle이 여전히 build되는지 확인합니다.
4. Threading, list, native module, `engineVersion`을 건드린 변경이면 device 또는 Lynx Explorer에서 실행합니다. Test suite가 이를 대신하지 못합니다.

실행하지 못한 단계와 이유를 보고합니다. 일어나지 않은 device 확인을 주장하지 않습니다.

## Checklist

- [ ] Test runner가 `withLynxConfig()`를 쓰는 Rstest이거나, 근거가 있는 Vitest입니다.
- [ ] `pluginTypeCheck()`가 설정됐고 type check가 check 순서에 들어 있습니다.
- [ ] `isolatedModules: true`와 `jsxImportSource: "@lynx-js/react"`가 있습니다.
- [ ] Touched 화면에 render test와 event test가 있습니다.
- [ ] Host data test가 없거나 일부만 있는 `initData`와 없는 `globalProps`를 다룹니다.
- [ ] Main-thread handler test가 직접 호출이 아니라 binding을 통해 확인합니다.
- [ ] List test가 `item-key`와 `key` 일치를 확인합니다.
- [ ] Native module을 `NativeModules`가 아니라 `src/shared/native/` adapter에서 mock합니다.
- [ ] 보고에 unit test가 증명할 수 없는 것(device 동작, engine 호환성, 실제 timing)을 밝혔습니다.

## Sources

> 확인 2026-11-07. 이 서술은 이 패키지의 날짜가 있는 snapshot `references/official/lynx/lynx-2026-11-07.md`를 재진술한 것이며, 그 파일이 2026-11-07에 읽은 Lynx 문서, `@lynx-js/create-lynx` 0.2.1 tarball, npm registry metadata를 인용합니다.

| Claim | Source |
|---|---|
| `@lynx-js/react/testing-library`, Rstest와 Vitest 설정, typed event 이름 | https://lynxjs.org/react/reactlynx-testing-library.md |
| `@lynx-js/testing-environment`의 dual thread emulation | https://registry.npmjs.org/@lynx-js%2Ftesting-environment, https://registry.npmjs.org/@lynx-js%2Freact |
| 제공되는 `rstest.config.ts`, template script, `@rstest/core` | https://registry.npmjs.org/@lynx-js%2Fcreate-lynx/-/create-lynx-0.2.1.tgz |
| Build에서 type check를 하지 않음, `pluginTypeCheck`, `isolatedModules` 요구 | https://lynxjs.org/rspeedy/typescript.md |
| JSDOM element PAPI emulation과 `jest-dom` matcher | https://lynxjs.org/react/reactlynx-testing-library.md |
| 경계 mock과 device 증거 요구 | 공식 Lynx 요구가 아니라 이 패키지의 관례 |
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