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/native-and-platform.md

View on GitHub
# Lynx Native and Platform

> Read when touching native modules, host app integration, the engine dependency, `engineVersion`, or the web target. The `engineVersion` gate in this file blocks deployment, not just review.

## `engineVersion` is a deployment constraint

`engineVersion` declares the oldest engine a bundle can run on. A bundle that declares N runs on an engine of N or newer and **fails fatally with error 10204 on anything older**. There is no degradation path, no fallback, and no runtime warning that a build would catch.

That makes it the hardest constraint in a Lynx deployment:

- It is not a build setting. The build succeeds regardless.
- It is not versioned with the bundle in a way the host can negotiate. The host either satisfies it or the screen dies.
- `pluginReactLynx` defaults it to `'3.2'`. That default is a floor, not a target; leaving it alone is safe, but it also forbids newer CSS and APIs that a higher value would unlock.

### Blocking review rule

**A change that raises `engineVersion` cannot merge until the lowest engine version of every host that loads the bundle is recorded with its evidence.** Accept evidence in this order:

1. The host dependency in this repository: an iOS `Podfile` line `pod 'Lynx', '<version>'`, an Android Gradle `org.lynxsdk.lynx:lynx:<version>`, or a HarmonyOS `@lynx/primjs` dependency.
2. A release-train document or app-version matrix the repository points at.
3. A named person's confirmation with the app version it applies to, recorded in the config comment.

If none of those exist, the bundler cannot verify the floor. Keep `engineVersion` at its current value, report the missing evidence, and do not raise it to unlock a feature. Silently raising it passes review and then kills the screen on the oldest shipped host, which is the worst failure shape: it reproduces on exactly the users who cannot update.

```ts
pluginReactLynx({
  // Lowest engine on a shipping host: 3.9 (Android app 24.x pins org.lynxsdk.lynx:lynx:3.9.0).
  engineVersion: '3.9',
})
```

The same reasoning applies to every engine-gated feature: `!important` and the `flex` shorthand change at 3.9, `FetchBundle` lazy-bundle loading at 3.9 and later, Trace from 3.4, WebAssembly from 3.8 on Android only. Using one of them is a decision about the host floor.

## Native modules

Native modules are registered by the host app and called from the bundle.

| Platform | Registration |
|---|---|
| Android | `LynxEnv.inst().registerModule(...)` |
| iOS | `[globalConfig registerModule:...]` |

Rules:

- Native modules can be used only from Background Thread Scripting. `NativeModules.X` in a render body or at module top level throws on the main thread. This is a blocking gate in `rules/lynx/threading.md`.
- Native module access funnels through one adapter under `src/shared/native/`. Every call site goes through it, so the thread and the error handling are decided once.
- The host decides what exists. A bundle cannot assume a module; call it defensively or check availability once and cache the answer.
- Host permissions — camera, location, storage — are not Lynx concepts. The bundle can do only what the host's native modules and `fetch` service permit. There is no Lynx-level permission model beyond the module validator.

### Module call authorization

From SDK 3.5 the host can install a per-`LynxView` validator that sees `(moduleName, methodName, params)` and returns allow or deny; denying raises a JS error.

```kotlin
// Android
lynxViewBuilder.registerModuleAuthValidator(object : LynxModule.AuthValidator {
  override fun validate(module: String, method: String, params: JSONObject): Boolean =
    allowed[module]?.contains(method) == true
})
```

```objc
// iOS
[config registerMethodAuth:^BOOL(NSString *module, NSString *method, NSDictionary *params) {
  return [self allowedModule:module method:method params:params];
}];
```

Available on Android and iOS; HarmonyOS support was pending at the time the documentation was read. Treat the validator as the seam for "this screen must not call the wallet module" and record which modules each surface may reach.

## Host data contract

`initData` and `globalProps` are host inputs, not local state. Their platform entry points and typing live in `rules/lynx/ui-and-data.md`; this file owns only the boundary rule: a frontend change that adds a field to `initData` is a host contract change, so it ships with the host change or behind a check for absence. A bundle deployed before its host would read `undefined`.

## Host app integration

| Platform | Dependency | Notes |
|---|---|---|
| iOS | CocoaPods `pod 'Lynx', '<version>'`, plus `PrimJS`; optionally `LynxService`, `XElement`, `SDWebImage`, `SDWebImageWebPCoder` | Version must satisfy every bundle's `engineVersion` |
| Android | Maven `org.lynxsdk.lynx:lynx`, `:lynx-jssdk`, `:lynx-trace`, `:primjs`; optionally `:lynx-service-image`, `:lynx-service-log`, `:lynx-service-http` | Gradle version is the floor for `engineVersion` |
| HarmonyOS | `@lynx/primjs` artifacts | Engine APIs differ; verify separately |
| Windows | CMake plus LynxSDK | Not verified by this package |
| Web | `@lynx-js/web-core` and `<lynx-view>` | See below |

`LynxView` is itself a native view: it works full-screen or embedded. The host sets size constraints and Lynx lays out the `<page>` inside. When the loader shows a splash, a skeleton, or a native header around the view, that chrome is host code and its layout must match what the bundle assumes — a bundle that expects the full screen while the host gives it 60% height produces a layout that looks like a CSS bug.

Engine versions across platforms are released together but the host dependencies advance independently. Pinning Android to 3.9 and iOS to 4.0 is normal; the effective floor is the lower of the two for any bundle both load.

## Engine release model

- Documented stable engine at the time of writing: 4.2, released 2026-10-27. 4.2.0 pins PrimJS 4.2.1 across Android Gradle, the iOS pod, and Harmony.
- The project moved from a bi-monthly to a monthly cadence starting with 3.8. The published plan has already slipped once — 4.2 was planned for 2026/09 and landed 2026-10-27 — so treat the plan as intent, not as a schedule to depend on.
- Platform floor: iOS 10 and Android 5.0 (API 21) or newer. macOS is the recommended development OS; Windows and Linux hosts are "not yet verified or guaranteed" by the engine project.

`@lynx-js/types` tracks the engine major line (4.4.2 observed while the engine was 4.2) while `@lynx-js/react` has its own 0.129.x line. No published matrix ties a `@lynx-js/react` minor to an engine minor, so read the installed versions instead of asserting a pairing.

## Web target status

`@lynx-js/web-core` provides the Lynx web platform. It renders a `.lynx.bundle` inside a `<lynx-view>` custom element.

- Registry state observed: 0.26.7, while the engine is 4.2.
- The documentation gives a full integration path but **no production-readiness statement**, and no SSR guide was found even though `enableSSR` exists and defaults to `false`.
- Treat a web target as available but unverified for production. Do not present it as a way to ship one codebase to web and native without the caveat.

`<lynx-view>` attributes: `url` (required), `globalProps`, `initData`, `browser-config` with `pixelRatio`/`width`/`height`, `transform-vw`, `transform-vh`; properties `nativeModulesMap` and `onNativeModulesCall`. The bundle URL and every module URL are network resources, so treat both as untrusted input.

## Supply chain

A `.lynx.bundle` is a binary artifact containing both JS layers, loaded by a host that enforces `engineVersion`. Three consequences:

- Sign or checksum the bundle at the distribution layer; the format does not carry a signature.
- Serve it over TLS from a host you control. A replaced bundle runs with the native module access the validator allows.
- Keep the validator's allow-list narrow enough that a replaced bundle gains little.

## Checklist

- [ ] `engineVersion` is at or below the lowest engine on a shipping host, with the evidence recorded next to it.
- [ ] Any raised `engineVersion` names the feature that needs it and the host evidence that permits it.
- [ ] No native call reaches `NativeModules` outside the adapter under `src/shared/native/`.
- [ ] No native call appears in a render body or at module top level.
- [ ] The adapter handles a missing module rather than assuming the host registered it.
- [ ] Module-call authorization is considered for any privileged module, and the platform gap is stated.
- [ ] A new `initData` field ships with its host change or an absence check.
- [ ] Host dependencies pin a version that satisfies every bundled `engineVersion`.
- [ ] Embedded-host sizing and surrounding chrome were checked against the bundle's layout assumptions.
- [ ] The web target is reported as available but unverified for production.
- [ ] Bundle distribution is over TLS from a controlled host, and the module allow-list stays narrow.

## 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 engine release feed, and npm registry metadata read on 2026-11-07.

| Claim | Source |
|---|---|
| `engineVersion` semantics, the fatal 10204 error on an older engine, and the `'3.2'` default | https://lynxjs.org/guide/compatibility.md, https://lynxjs.org/rspeedy/plugin.md |
| Native modules being background-thread only and the per-`LynxView` auth validator from SDK 3.5 | https://lynxjs.org/guide/use-native-modules.md |
| Registration APIs and host permission boundary | https://lynxjs.org/guide/use-native-modules.md, https://lynxjs.org/llms.txt |
| CocoaPods, Maven, and HarmonyOS dependencies; `LynxView` as an embeddable native view | https://lynxjs.org/guide/start/integrate-with-existing-apps.md, https://lynxjs.org/llms.txt |
| Engine 4.2.0 on 2026-10-27, PrimJS 4.2.1 pinning, and the monthly cadence with its slippage | https://github.com/lynx-family/lynx/releases.atom, https://lynxjs.org/blog/lynx-open-source-roadmap-2026.md, https://lynxjs.org/blog/lynx-3-8.md |
| iOS 10 and Android 5.0 platform floor; unverified Windows/Linux hosts | https://github.com/lynx-family/lynx/develop/README.md |
| `@lynx-js/web-core` 0.26.7 with no production-readiness statement; `lynx-view` attributes | https://registry.npmjs.org/@lynx-js%2Fweb-core, https://lynxjs.org/llms-full.txt |
| Engine-gated features: `!important` and `flex` at 3.9, Trace from 3.4, WebAssembly from 3.8 Android-only | https://lynxjs.org/blog/lynx-3-9.md, https://lynxjs.org/guide/devtool/trace.md, https://lynxjs.org/guide/scripting-runtime/index.md |
| The engine-version evidence requirement, the adapter boundary, and the supply-chain advice | 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: 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