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.
references/official/tanstack-start/tanstack-start-2026-11-04.md
View on GitHub# TanStack Start Official Snapshot
- last_verified_at: 2026-11-04
- next_re_verification: 2027-05-04 (or earlier if a Refresh Trigger below fires)
- packages_checked:
- `@tanstack/react-start`: `1.169.4`
- `@tanstack/start-client-core`: `1.170.39`
- `@tanstack/start-server-core`: `1.169.45`
- `@tanstack/start-plugin-core`: `1.171.55`
- `@tanstack/router-plugin`: `1.168.48`
- `@tanstack/router-cli`: `1.167.46`
- `@tanstack/zod-adapter`: `1.167.0`
- `@tanstack/cli`: `0.72.16`
- `vite`: `8.3.6`
- `zod`: `4.6.7`
- `@tanstack/react-query`: `5.107.1`
- patch_checked_at: 2026-11-07 (`vite` and `@tanstack/react-query` only; every other row is the 2026-11-04 reading)
- engines: `@tanstack/react-start@1.169.4` declares `node >=22.12.0` and `peerDependencies.vite >=8.0.0`
- source_priority: canonical guide pages > API/reference pages > examples > migration/comparison pages > release notes for drift context
- supersedes: the retired 2026-09-22 Start snapshot (release-candidate era)
Use this file when Start-specific API behavior affects an architecture rule. Every fact below is labeled `Official` — it comes from TanStack's own guide pages, source tree, or package metadata. Hypercore conventions stay in `rules/tanstack-start/`; keep official facts here.
## Contents
- [Corrected from the 2026-09-22 snapshot](#corrected-from-the-2026-09-22-snapshot)
- [Release status](#release-status)
- [Project structure](#project-structure)
- [Router setup](#router-setup)
- [Server functions](#server-functions)
- [Execution model](#execution-model)
- [Import protection](#import-protection)
- [Middleware](#middleware)
- [Server routes](#server-routes)
- [SSR, hydration, and rendering](#ssr-hydration-and-rendering)
- [Platform and tooling](#platform-and-tooling)
- [Refresh Triggers](#refresh-triggers)
- [Sources](#sources)
## Corrected from the 2026-09-22 snapshot
- **`.inputValidator(...)` is gone, not deprecated.** The retired 2026-09-22 snapshot (and the 2026-04-30 one before it) recorded the alias as "deprecated but still resolves at runtime". `@tanstack/react-start@1.169.0` removed it from both `createServerFn` and `createMiddleware`, and `start-client-core@1.170.39`'s types contain zero `inputValidator` occurrences. Any remaining call is broken code.
- **Start is stable.** The retired snapshot described the Release Candidate stage; the overview page now opens with "TanStack Start is stable."
- **Vite 8 is mandatory.** The retired snapshot treated Vite 7 as a supported branch. Start 1.169+ requires Vite 8.
- The pinned versions above were re-measured on 2026-11-04 from the npm `latest` dist-tags.
## Release status
- Verbatim, from the Start overview page: "TanStack Start is stable. If you're upgrading from a release candidate, follow `Migrate from the Release Candidate`."
- `@tanstack/react-start` 1.169.0 is the first stable release, published 2026-10-12. The migration page states it plainly: "`@tanstack/react-start` 1.169 is the first stable release of TanStack Start." The current stable patch is 1.169.4 (2026-10-22).
- Removed APIs when coming from a release candidate: `@tanstack/nitro-v2-vite-plugin` becomes `nitro()` from `nitro/vite`; `useSession` becomes a session library such as iron-session (existing Start session cookies are not readable by the new library, so use a new cookie name or migrate the old cookies first); `.inputValidator()` becomes `.validator()`.
- Vite 8: "Start requires Vite 8 when you build with Vite." The release note adds "Require Vite 8 for Vite builds. Vite 7 is no longer supported."
- Still experimental and not to be adopted on the strength of stability: deferred hydration (`<Hydrate>`), static server functions, React Server Components.
- Sources:
- <https://tanstack.com/start/latest/docs/framework/react/overview.md>
- <https://tanstack.com/start/latest/docs/framework/react/migrate-from-release-candidate.md>
- <https://github.com/TanStack/router/releases/tag/%40tanstack%2Freact-start%401.169.0>
## Project structure
- Start's plugin defaults `srcDirectory` to `'src'`, and the routes directory resolves to `<srcDirectory>/routes` unless overridden through `tanstackStart({ router: { routesDirectory } })` — derive the real route root from config instead of hard-coding `src/routes`.
- The docs' typical shape is `src/routes`, `src/router.tsx`, generated `src/routeTree.gen.ts`, `src/styles.css`, optional `src/types`, `public/`, a root bundler config (`vite.config.ts` or `rsbuild.config.ts`), `package.json`, and `tsconfig.json`.
- `routeTree.gen.ts` is generated by Router tooling. The Router FAQ says it should be committed — "it is essentially part of your application's runtime, not a build artifact" — and the file-based-routing API page advises ignoring the generated path from linters and formatters. Do not hand-edit it (Hypercore convention).
- File organization: the server-functions guide presents the `*.functions.ts` (server function wrappers, safe to import anywhere) / `*.server.ts` (server-only helpers) / plain `*.ts` (client-safe) split as "one approach", not a mandate.
- `.functions.ts` is **not** enforced by import protection. The import-protection guide's default file patterns are only `**/*.server.*` and `**/*.client.*`; `.functions.ts` appears solely in the file-organization section of the server-functions guide.
- Router supports flat, directory, and mixed route file structures officially; a route-directory preference is a local convention and is not official TanStack behavior (<https://tanstack.com/router/latest/docs/routing/file-based-routing>).
- Sources:
- <https://tanstack.com/start/latest/docs/framework/react/guide/server-functions.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/import-protection.md>
- <https://tanstack.com/router/latest/docs/faq>
- <https://tanstack.com/router/latest/docs/api/file-based-routing>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-plugin-core/src/schema.ts>
## Router setup
- `src/router.tsx` must export a `getRouter` function that returns a new router instance on every call. The official example uses a function declaration: `export function getRouter() { ... }`.
- Search validation: Zod v4 passes the schema directly to `validateSearch`; `@tanstack/zod-adapter` is Zod v3 only because its `peerDependencies` pin `zod: ^3.23.8`, so a Zod 4 project cannot install it. Zod v3 still uses `zodValidator` / `fallback` from the adapter.
- Sources:
- <https://tanstack.com/start/latest/docs/framework/react/guide/routing.md>
- <https://tanstack.com/router/latest/docs/guide/search-params>
- <https://tanstack.com/router/latest/docs/how-to/validate-search-params>
- <https://registry.npmjs.org/@tanstack/zod-adapter/latest>
## Server functions
- `createServerFn()` defines a server function. `method` defaults to `'GET'`, and `Method` is exactly `'GET' | 'POST'` — no other verb exists (`packages/start-client-core/src/createServerFn.ts:449`, `:84-86`).
- `.validator(...)` is the only spelling. `.inputValidator(...)` was removed from `createServerFn` and `createMiddleware` in 1.169.0 — the release note reads "Remove the deprecated `.inputValidator()` from `createServerFn` and `createMiddleware`. Use `.validator()`, which takes the same validator," and `start-client-core@1.170.39`'s declarations contain no `inputValidator` at all.
- Zod schemas pass directly to `.validator(...)`. Validator input types must be serializable; `FormData` is also allowed for `POST` server functions.
- A builder carries a **single** validator — `.validator(...)` sets it (a later call replaces the earlier one) — while `.middleware([...])` is repeatable and merges with previously supplied middleware.
- The `strict` option exists and defaults to `strict: true`. It governs TypeScript-level serialization checks; `createServerFn({ strict: false })` and the granular `strict: { input: false }` / `strict: { output: false }` forms opt out. The docs warn that `strict: false` only relaxes the type checks — the runtime serialization layer still has to handle the values.
- Server functions are same-origin app RPC endpoints, callable from loaders, components, hooks, other server functions, and event handlers; `useServerFn()` is the React wrapper when hook ergonomics are needed.
- Sources:
- <https://tanstack.com/start/latest/docs/framework/react/guide/server-functions.md>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-client-core/src/createServerFn.ts>
## Execution model
- Start code is isomorphic by default — it runs and is bundled in both environments unless explicitly constrained — and route loaders are isomorphic, not server-only (they run on the server during SSR and on the client during navigation).
- The execution-control primitives are `createServerFn`, `createServerOnlyFn`, `createClientOnlyFn`, and `createIsomorphicFn`.
- `createIsomorphicFn()` composes one function with per-environment implementations via `.server(...)` and `.client(...)`; a missing side is a no-op returning `undefined`, not an error. Environment functions are tree-shaken per bundle.
- `createServerOnlyFn(...)` and `createClientOnlyFn(...)` enforce environment-bound execution and throw descriptive runtime errors when called in the wrong environment.
- Secrets, DB access, filesystem access, and privileged SDK calls must sit behind server-only or server-function boundaries.
- Sources:
- <https://tanstack.com/start/latest/docs/framework/react/guide/execution-model.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/code-execution-patterns.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/environment-functions.md>
## Import protection
- **Status: documented, no Experimental banner.** The page opens with "Import protection prevents server-only code from leaking into client bundles and client-only code from leaking into server bundles. It runs inside TanStack Start and is enabled by default." The documented option surface is `enabled`, `behavior`, `log`, `include`, `exclude`, `maxTraceDepth`, `client`/`server` rules/tanstack-start (`files`, `specifiers`, `excludeFiles`), `ignoreImporters`, and `onViolation`.
- Enabled out of the box. Documented defaults: `enabled: true`; `behavior: { dev: 'mock', build: 'error' }`; `log: 'once'` (deduplicates repeated violations); `include` = Start's `srcDirectory`; `exclude: []`; `maxTraceDepth: 20`.
- Default deny rules: `client.files` = `['**/*.server.*']`, `server.files` = `['**/*.client.*']`, `client.specifiers` = the framework server specifiers, `server.specifiers` = `[]`, and both `excludeFiles` = `['**/node_modules/**']`.
- **Replace vs additive is the trap.** Per the option table: `client.specifiers` is **additive with defaults**; `client.files`, `client.excludeFiles`, `server.files`, `server.specifiers`, and `server.excludeFiles` **replace** the defaults. `excludeFiles` **fully replaces** `['**/node_modules/**']` — to exclude extra paths while still skipping `node_modules`, pass both. Setting `client.files` without carrying `'**/*.server.*'` silently drops the default deny rule.
- Type-only imports and re-exports are ignored because they are erased at runtime; mixed imports still count when they carry at least one runtime value.
- Side-effect marker imports remain available for explicit boundaries: `@tanstack/react-start/server-only` and `@tanstack/react-start/client-only`.
- `mockAccess` (`'error' | 'warn' | 'off'`) exists in `@tanstack/start-plugin-core@1.171.55`'s `schema.d.ts` but is **absent from the import-protection guide**. It is a real, undocumented schema option: label it as such and never present it as documented.
- Dev-mode violations can be false positives. Build mode defers the check until after tree-shaking, so an import that vanishes from the production graph can still warn in dev; confirm with a build before editing a boundary.
- Sources:
- <https://tanstack.com/start/latest/docs/framework/react/guide/import-protection.md>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-plugin-core/src/schema.ts>
## Middleware
- Two middleware types. **Request middleware** customizes any server request; **server function middleware** is a subset that adds server-function-only features such as input validation and client-side logic. Request middleware uses `createMiddleware()` (or `createMiddleware({ type: 'request' })`); server function middleware uses `createMiddleware({ type: 'function' })`.
- Middleware input validation uses `.validator(...)` too, and `inputValidator` was removed from `createMiddleware` in the same 1.169.0 release.
- `sendContext` is explicit and one-directional per hop. Client context is **not** sent to the server by default; it must be passed through `next({ sendContext: {...} })`, and anything the client can send, the client can lie about.
- **"Shape validation is not authorization."** A parsed UUID or number is a well-formed identifier, not an authorized one. When the value selects which rows get read or written — a query key, filter, or path parameter — the session principal's access to it must be verified separately, or a logged-in user can rewrite the value in their own request and reach other tenants' data.
- The docs' required pattern: "Always derive the session itself from a server-trusted source (a cookie + DB lookup in `authMiddleware`), never from `sendContext`."
- **CSRF.** `createCsrfMiddleware()` protects server functions from cross-site requests. The guide's install form now carries a filter: `createCsrfMiddleware({ filter: (ctx) => ctx.handlerType === 'serverFn' })`, because "by default, `createCsrfMiddleware()` validates every request handled by the middleware". It verifies `Sec-Fetch-Site`, `Origin`, or `Referer` and rejects requests that cannot be proven same-origin; requests carrying none of the three are rejected unless `allowRequestsWithoutOriginCheck: true`. Type surface (`createCsrfMiddleware.d.ts`): `filter`, `origin`, `secFetchSite` (default `'same-origin'`), `referer` (default `true`), `allowRequestsWithoutOriginCheck` (default `false`), `failureResponse` (default `403 Forbidden`). The guide documents `filter`, `origin`, and `allowRequestsWithoutOriginCheck`; the other three are type-level facts.
- **The CSRF trap:** if the app does not define `src/start.ts`, Start installs its CSRF middleware automatically for server functions. Defining `src/start.ts` silently drops that automatic installation, so the file must add `requestMiddleware: [createCsrfMiddleware()]` explicitly. Start logs a development warning for server function requests when `src/start.ts` exists without it; `disableCsrfMiddlewareWarning: true` suppresses the warning for apps that handle CSRF another way.
- Sources:
- <https://tanstack.com/start/latest/docs/framework/react/guide/middleware.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/server-functions.md>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-client-core/src/createCsrfMiddleware.ts>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-client-core/src/createMiddleware.ts>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-plugin-core/src/schema.ts>
## Server routes
- Server routes are declared by adding `server` to a route file's `createFileRoute(...)(...)` call and follow Router's file-based routing conventions.
- `handlers` is either an object mapping HTTP methods to handler functions, or a function that receives `createHandlers` for handlers that need their own middleware composition. An optional route-level `middleware` array applies to all handlers and runs before handler-specific middleware.
- Pathless layout routes and break-out routes are supported for grouping server-route middleware: a pathless layout adds middleware to a group of routes, and a break-out route escapes parent middleware.
- Methods beyond GET and POST (`PUT`, `PATCH`, `DELETE`) are supported on server routes.
- Source: <https://tanstack.com/start/latest/docs/framework/react/guide/server-routes.md>
## SSR, hydration, and rendering
- Routes matching the initial request render on the server by default. Per-route `ssr` defaults to `true`, and `createStart({ defaultSsr: false })` changes that default.
- Hydration mismatches come from `Intl` locale/time-zone differences, `Date.now()`, random IDs, responsive-only logic, feature flags, and user preferences. The documented fix is to compute once on the server from a cookie (preferred) or the `Accept-Language` header and hydrate that as initial state.
- **Deferred hydration is experimental**: `<Hydrate>` with strategies imported from `@tanstack/react-start/hydration`.
- ISR is available: static prerendering plus standard HTTP cache headers plus revalidation, deliberately CDN-agnostic.
- Sources:
- <https://tanstack.com/start/latest/docs/framework/react/guide/selective-ssr.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/hydration-errors.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/deferred-hydration.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/isr.md>
## Platform and tooling
- Two official bundlers: Vite (the default) and **Rsbuild**, imported as `@tanstack/react-start/plugin/rsbuild` from `rsbuild.config.ts`. An Rsbuild production build emits client assets in `dist/client` and a server bundle in `dist/server/index.js`.
- `autoCodeSplitting` is a bundler-plugin option that defaults to `false` (v2 will default it to `true`). The Start plugin's config schema omits it (`configSchema.omit({ autoCodeSplitting: true, target: true })`), so it **cannot** be passed through `tanstackStart()`.
- Client-exposed environment variables use the build tool's public prefix — `VITE_` for Vite, `PUBLIC_` for Rsbuild.
- `src/server.ts` is the optional server entry point, using the fetch-style `ServerEntry` shape; when it is absent Start supplies a default. `createStartHandler(...)` now rethrows the original error; `createServerEntry` converts errors to responses and the built-in entry already uses it. `handleStartError(error)` produces Start's error response with helper state applied. Register `server.requestContext` on `@tanstack/react-router`'s `Register` interface to type the context passed through `handler.fetch(request, { context })`.
- Hosting through Nitro uses `nitro()` from `nitro/vite`; `@tanstack/nitro-v2-vite-plugin` is removed. Official partners are Cloudflare (`@cloudflare/vite-plugin` + `wrangler`), Netlify (`@netlify/vite-plugin-tanstack-start`), and Railway (via Nitro).
- Static server functions are **experimental** (`staticFunctionMiddleware` from `@tanstack/start-static-server-functions`).
- Scaffolding: `npx @tanstack/cli@latest create` (`@tanstack/cli` `0.71.0`) or TanStack Builder. The legacy aliases `create-tsrouter-app`, `create-start-app`, `create-tanstack-app`, `create-tanstack`, and `@tanstack/create-start` print deprecation warnings.
- Sources:
- <https://tanstack.com/start/latest/docs/framework/react/guide/hosting.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/environment-variables.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/server-entry-point.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/static-server-functions.md>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-plugin-core/src/schema.ts>
## Refresh Triggers
Refresh this snapshot when:
- Any official Start guide page listed under Sources changes its text, option table, or documented defaults.
- A Start guide page the skill relies on is renamed, removed, or superseded by a new page.
- A security advisory affects any pinned package. Check the repository advisories (`gh api repos/TanStack/router/security-advisories`) and the npm advisory database. Precedent: advisory `GHSA-g7cv-rxg3-hmpx` (2026-05-11) published malicious versions of 42 `@tanstack/*` packages, so an advisory check belongs in every re-verification pass.
- Start announces a new major or changes the stable line's minimum Vite/Node floor.
**Do NOT key this trigger on version numbers alone.** Router and Start stay on `1.x` and absorb breaking changes in patch releases, and `@tanstack/react-router` 1.170.41 through 1.170.46 carry only internal composition and link-hydration changes plus an agent-skills publish, with no behavior change a version bump would flag. Meanwhile `@tanstack/react-start@1.169.0` removed `useSession` and `.inputValidator()` in what looks like an ordinary minor. A version-based trigger therefore both over-fires and under-fires. The version list above is a provenance record of what was measured on 2026-11-04, not the trigger.
## Sources
> Sources checked 2026-11-04, the date this snapshot records as its verification date; the filename date and that record agree by construction. Every source below was fetched on 2026-11-04 for this snapshot. The `guide/` path segment is required — the same pages without it return 404. Line numbers cited are positions in an older fetched copy, so they drift as the pages change; the quoted text is the stable anchor. No source outside this list is claimed.
- <https://tanstack.com/start/latest/docs/framework/react/overview.md>
- <https://tanstack.com/start/latest/docs/framework/react/migrate-from-release-candidate.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/routing.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/server-functions.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/environment-functions.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/middleware.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/server-routes.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/import-protection.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/code-execution-patterns.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/execution-model.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/selective-ssr.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/hydration-errors.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/deferred-hydration.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/isr.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/environment-variables.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/hosting.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/server-entry-point.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/static-server-functions.md>
- <https://tanstack.com/router/latest/docs/faq>
- <https://tanstack.com/router/latest/docs/api/file-based-routing>
- <https://tanstack.com/router/latest/docs/routing/file-based-routing>
- <https://tanstack.com/router/latest/docs/guide/search-params>
- <https://tanstack.com/router/latest/docs/how-to/validate-search-params>
- <https://registry.npmjs.org/@tanstack/zod-adapter/latest>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-client-core/src/createServerFn.ts>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-client-core/src/createMiddleware.ts>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-client-core/src/createStart.ts>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-client-core/src/createCsrfMiddleware.ts>
- <https://raw.githubusercontent.com/TanStack/router/fe7f1fd0e6ef73c3f341dd2338b406749538a85d/packages/start-plugin-core/src/schema.ts>
- <https://registry.npmjs.org/@tanstack/react-start/latest>
- <https://github.com/TanStack/router/releases/tag/%40tanstack%2Freact-start%401.169.0>
- <https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 470k | Updated | Claude CodeCodex | Verified | Install |
| 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: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |