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/ui-and-data.md

View on GitHub
# Lynx UI and Data

> Read when touching elements, styles, layout, events, lists, host-provided data, or routing in a Lynx app.

## Elements

Lynx elements are not DOM nodes. They map to iOS `UIView`, Android `ViewGroup`, HarmonyOS components, or web custom elements.

`view`, `text`, `image`, `scroll-view`, `list`/`list-item`, `page`, `frame`, `input`, `textarea`, `overlay`, `refresh`, `scroll-coordinator`, `svg`, `title-bar-view`, `viewpager`.

Three habits carried over from web React break here:

- Text must live inside `<text>`. Bare text in a `<view>` does not render.
- Inline layout is nested `<text>`, not `display: inline`.
- `<image>` is an empty tag with `src`; `auto-size` sizes it from the image instead of a declared width and height.
- `<svg>` differs from web: pass markup with `content` or a URL with `src`.

## CSS differences

Selectors, specificity, and inline `style` largely match web. The layout model does not.

| Web behavior | Lynx behavior |
|---|---|
| `display: inline`, `display: block` | Not supported as `display` values; every element is block-level by default |
| `box-sizing: content-box` | Always `border-box` |
| Margin collapsing | Does not occur |
| `overflow: scroll` | Unsupported; use `<scroll-view scroll-x>` or `scroll-y` |
| `position: fixed` relative to viewport | Fixed nodes are promoted under the root node |
| Regular properties inherit | Only CSS custom properties inherit by default |

`display` modes that do exist:

- `flex` — CSS Flexbox, but `min-content` is unsupported and the flex shrink lower bound is treated as `0px`.
- `linear` — vertical main axis with `linear-direction` and `linear-weight`.
- `grid` — no `grid-area` and no line names.
- `relative` — Android `RelativeLayout` mental model, mobile only.

`position` supports `relative`, `absolute`, and `fixed`.

Units: `rpx` is 1/750 of the configured logical width from host screen metrics. `vw` and `vh` exist; on the web target `transform-vw` and `transform-vh` can re-base them per container.

Inheritance is opt-in and its default is easy to misread. `pluginReactLynx({ enableCSSInheritance: true })` makes a fixed list inherit — `direction`, `color`, `font-*`, `letter-spacing`, `line-height`, `text-align`, `text-decoration`, `text-shadow` — and `customCSSInheritanceList` extends that list. `enableCSSInheritance` defaults to `false`, so a font set on a container does not reach a child unless you set it again or enable inheritance.

`-x-` prefixed properties expose mobile capabilities such as `-x-auto-font-size`.

Version-sensitive CSS, all requiring a matching `engineVersion`:

- `!important` requires `engineVersion` 3.9 or later.
- 3.9 changed the `flex` shorthand so an omitted `flex-basis` parses as `0%` instead of `0`.
- 3.9 added `grid-row`/`grid-column` shorthands, `position: sticky`, and the HarmonyOS motion path.

Each of those is a deployment decision, not a styling detail: raising `engineVersion` to use one raises the host floor.

## Events

The attribute name encodes both the phase and whether propagation is intercepted.

| Attribute | Behavior |
|---|---|
| `bindtap` | Bubble phase, handler runs on background |
| `catchtap` | Bubble phase, stops propagation |
| `capture-bindtap` | Capture phase |
| `capture-catchtap` | Capture phase, stops propagation |
| `global-bindtap` | Global listening, regardless of the target node |
| `main-thread:bindtap` and variants | Handler runs synchronously on the main thread |

A background handler receives plain JSON. Non-touch events fire only on the target node. `stopPropagation()` exists only inside a main-thread script; on the background thread the `catch`/`capture` naming is the mechanism.

Handler style, per the official best practices:

- Pass function references, not inline arrows. An inline arrow is re-created per render and loses the inference that makes background-only marking work.
- Read data from `dataset` rather than closing over values.
- Prefer `currentTarget` over `target` so the handler stays correct when the event originates in a child.

```tsx
<view
  data-id={item.id}
  bindtap={onRowTap}
/>

function onRowTap(e) {
  'background only';
  openDetail(e.currentTarget.dataset.id);
}
```

## Lists

`<list>` virtualizes and recycles. Only children in the visible area are rendered, and the width and height of `<list>` are its viewport, "so they need to be fixed values."

Required attributes: `scroll-orientation`, `list-type` (`single`, `flow`, `waterfall`), `span-count`. Every direct child is a `<list-item>` with `item-key`, which must match the `key` used to build the list.

```tsx
<list
  scroll-orientation="vertical"
  list-type="single"
  span-count={1}
  style={{ height: '100vh' }}
>
  {rows.map((row) => (
    <list-item key={row.id} item-key={row.id}>
      <Row row={row} />
    </list-item>
  ))}
</list>
```

Recycling controls:

- `reuse-identifier` groups structurally identical items so nodes are reused across groups. It is auto-generated per loop shape at compile time; set it explicitly when two loops should share nodes.
- `recyclable={false}` opts a node out of recycling.
- `experimental-recycle-sticky-item` is enabled by default from some `engineVersion` threshold.

The lifecycle caveat that causes real bugs: every child component's JS instance is created up front, but its real UI node is created or reused only when scrolled near. So `useEffect` and `ref` fire even when no UI node exists. Use `main-thread:ref` when the code must know whether a node is actually attached.

## Host data

The host injects `initData` and updates it:

| Platform | Initial | Update |
|---|---|---|
| iOS | `LynxView.loadTemplate(meta.initialData)` | `updateData` |
| Android | `setInitialData` on the `LynxLoadMeta.Builder` | `updateMetaData` |
| HarmonyOS | `MetaData(new TemplateData(...))` | `updateMetaData` |

Read it with `useInitData()`, which re-renders on update, or `useGlobalProps()` for `lynx.__globalProps`. `__globalProps` can be `null` or `{}` when the host does not provide it, so a consumer must handle absence.

Type the contract by augmenting the interfaces once:

```ts
// src/types/lynx.d.ts
declare module '@lynx-js/react' {
  interface InitData {
    userId: string;
    entryPoint: 'feed' | 'detail';
  }
}

declare module '@lynx-js/types' {
  interface GlobalProps {
    locale: string;
  }
}
```

`useInitDataChanged` and `useGlobalPropsChanged` exist for code that must react to an update rather than re-render with it.

Host data is untrusted input. Validate `initData` at the boundary like any network payload: it arrives as JSON from the host and can be absent, partial, or stale after an update.

## Routing

There is no History API and no `document`, so routing is memory-based by necessity.

- **React Router** — install v6, not v7. ReactLynx exposes the React v17 API surface, and the docs state this directly. Use `MemoryRouter`; `<Link>` and `<NavLink>` render anchors and do not apply. Navigate with `useNavigate`.
- **TanStack Router** — memory routing is required. File-based routing works through `@tanstack/router-plugin/rspack`. Alias `react$` to `@lynx-js/react/compat` so `React.startTransition` resolves, set `isServer: false` because `document` is undefined, and add `url-search-params-polyfill` in the entry.

Both are supported. Pick by the repository's existing dependency, not by preference.

A routing library inside a Lynx app is part of the Lynx target, not a second framework.

## What is not here

`document`, `window`, DOM APIs, `localStorage`, `History API`, `<Link>`. The replacements are `lynx.reload`, `lynx.createSelectorQuery`, `GlobalEventEmitter`, native modules, and custom elements. A library that depends on `window` or `document` at import time fails at load, not at call.

`TextEncoder`/`TextDecoder` are missing in PrimJS; use `TextCodecHelper` where text codec work is needed. `fetch` depends on a host-provided HTTP service, so it is not available in every embedding.

## Checklist

- [ ] All text is inside `<text>`; no bare text node exists in a `<view>`.
- [ ] No `display: inline` or `display: block` was introduced.
- [ ] No `overflow: scroll` was introduced; a `<scroll-view>` is used instead.
- [ ] A container-level font or color is not assumed to inherit unless `enableCSSInheritance` is on.
- [ ] Any `!important`, `flex` shorthand, or `position: sticky` use is matched by the `engineVersion` it requires.
- [ ] Event handlers are function references, read `dataset`, and prefer `currentTarget`.
- [ ] Every virtualized feed is a `<list>` with fixed viewport, `list-type`, `span-count`, `scroll-orientation`, and `item-key` equal to `key`.
- [ ] Code that must know whether a list row's node exists uses `main-thread:ref`.
- [ ] `initData` and `globalProps` are typed by one augmentation and validated at the boundary.
- [ ] Absent `globalProps` is handled rather than assumed.
- [ ] Routing uses memory history, and no `<Link>`, `NavLink`, or History API call remains.
- [ ] Uploads and text codec paths handle the missing `TextEncoder`/`TextDecoder` and host-dependent `fetch`.

## 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 read on 2026-11-07.

| Claim | Source |
|---|---|
| Element set and element-to-native mapping | https://lynxjs.org/guide/ui/elements-components.md, https://lynxjs.org/llms.txt |
| Text-in-`<text>`, `<image>` with `auto-size`, and `<svg>` `content`/`src` | https://lynxjs.org/llms.txt |
| `display` modes, `box-sizing`, no margin collapsing, `overflow`, `position`, units, and inheritance defaults | https://lynxjs.org/guide/ui/layout/index.md, https://lynxjs.org/guide/ui/styling.md, https://lynxjs.org/llms.txt |
| `!important`, the `flex` shorthand change, `grid-row`/`grid-column`, `position: sticky` in 3.9 | https://lynxjs.org/blog/lynx-3-9.md |
| Event attribute naming and phases | https://lynxjs.org/guide/interaction/event-handling.md |
| Function references, `dataset`, and `currentTarget` guidance | https://lynxjs.org/react/best-practices.md |
| `<list>` fixed viewport, attributes, `reuse-identifier`, and `recyclable` | https://lynxjs.org/api/elements/built-in/list.md |
| Child JS instances created up front and `main-thread:ref` accuracy | https://lynxjs.org/react/lifecycle.md |
| `initData` injection per platform and `useInitData`/`useGlobalProps` | https://lynxjs.org/guide/use-data-from-host-platform.md |
| TypeScript augmentation of `InitData`, `GlobalProps`, `NativeModules`, `IntrinsicElements` | https://lynxjs.org/rspeedy/typescript.md |
| React Router v6 with `MemoryRouter` and no `<Link>` | https://lynxjs.org/react/routing/react-router.md |
| TanStack Router memory routing, `react$` alias, `isServer: false`, and the search-params polyfill | https://lynxjs.org/react/routing/tanstack-router.md |
| No `document`/`window`, and `TextCodecHelper` for the missing text codecs | https://lynxjs.org/llms.txt |
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