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

references/official/tanstack-start/current-docs-2026-11-04.md

View on GitHub
# TanStack Start Current Docs Snapshot

- last_verified_at: 2026-11-04
- source: TanStack official Start docs pages fetched directly (the `guide/<page>.md` URLs below) plus published package types from `@tanstack/start-client-core@1.170.39` and `@tanstack/start-plugin-core@1.171.55`
- use_when: Start/Router API behavior, Start plugin config, import protection, execution boundaries, middleware, or server-function and server-route API shape affects an architecture decision
- authority: Official TanStack docs for API facts; Hypercore conventions remain in `rules/tanstack-start/`
- supersedes: the retired 2026-09-22 and 2026-06-02 snapshots (see "Corrected from earlier snapshots")

## Contents

- [Corrected from earlier snapshots](#corrected-from-earlier-snapshots)
- [Server functions](#server-functions)
- [Execution boundaries](#execution-boundaries)
- [Global Start configuration](#global-start-configuration)
- [CSRF protection](#csrf-protection)
- [Middleware](#middleware)
- [Import protection](#import-protection)
- [Server routes](#server-routes)
- [Drift handling](#drift-handling)
- [Sources](#sources)

## Corrected from earlier snapshots

- **`.inputValidator(...)` is removed, not deprecated.** Earlier snapshots recorded it as "deprecated but still resolving at runtime". `@tanstack/react-start@1.169.0` (2026-10-12) removed it from `createServerFn` and `createMiddleware`; the release note reads "Remove the deprecated `.inputValidator()` from `createServerFn` and `createMiddleware`. Use `.validator()`, which takes the same validator."
- Evidence, re-checked 2026-11-04:
  - Types: `start-client-core@1.170.39`'s declarations carry zero `inputValidator` occurrences.
  - Docs: `guide/server-functions.md` and `guide/middleware.md` use `.validator(...)` only, and `guide/middleware.md`'s comparison table lists `Input Validation | No | Yes (`.validator()`)`.
  - Migration page: the removed-API table maps `.inputValidator()` on server functions and middleware to `.validator()`.
- **The earlier "still resolves at runtime" record is now false.** It described `createServerFn.ts:921`'s `options.validator ?? options.inputValidator` fallback at commit `fe7f1fd0e6ef73c3f341dd2338b406749538a85d`; that fallback no longer exists. The earlier correction that `.validator(...)` was canonical was right; its claim that the alias kept working was a fact about that commit only.
- **Start is stable, not in Release Candidate.** The overview page now opens with "TanStack Start is stable."
- **Vite 8 is required, and Node ≥22.12.** `@tanstack/react-start@1.169.4` declares `peerDependencies.vite >=8.0.0` and `engines.node >=22.12.0`; the release note says "Vite 7 is no longer supported."
- The 2026-06-02 snapshot's deeper history, where an earlier pass recorded the inverse of the docs three days after the rename merged, is retained only as a caution: a dated snapshot is only as good as the pass that produced it.

## Server functions

- `createServerFn()` defines a server function. `method` defaults to `GET`; `createServerFn({ method: 'POST' })` is the other form. `Method` is exactly `'GET' | 'POST'` — `packages/start-client-core/src/createServerFn.ts:449` reads `export type Method = 'GET' | 'POST'`. No other verb is available.
- `.handler(...)` is the terminal builder call: it ends the chain and defines the implementation. `.validator(...)` attaches input validation and `.middleware([...])` attaches middleware before it. There is no `.inputValidator(...)`.
- The `strict` option exists and defaults to `strict: true`. It controls 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.
- File organization: the docs present the `*.functions.ts` (server function wrappers) / `*.server.ts` (server-only helpers) split as "one approach", not a mandate. Import protection does **not** enforce that naming — only `*.server.*` and `*.client.*` are enforced patterns.
- Static imports of server functions are safe; the docs warn against dynamic imports for them (`guide/server-functions.md:150`: "Avoid dynamic imports for server functions").
- Server functions are same-origin app RPC endpoints. They are callable from loaders, components, hooks, other server functions, and event handlers; `useServerFn()` is the React wrapper when hook ergonomics are needed.

## Execution boundaries

- `createServerFn`, `createServerOnlyFn`, `createClientOnlyFn`, and `createIsomorphicFn` are the official execution-control primitives.
- `createIsomorphicFn()` composes one function with per-environment implementations via `.server(...)` and `.client(...)`. A missing side is a no-op returning `undefined`, not an error.
- `createServerOnlyFn(...)` and `createClientOnlyFn(...)` enforce environment-bound execution and throw descriptive runtime errors when called in the wrong environment.
- Environment functions are tree-shaken per bundle: `.client()` bodies are excluded from the server bundle and vice versa.
- Loaders are isomorphic, not server-only — the docs' own "Common Problems" section calls out assuming otherwise as the classic secret-leak mistake.

## Global Start configuration

- `src/start.ts` is **not** part of the default Start template; it is created when global middleware or Start-level options are needed.
- The canonical shape is the callback form: `export const startInstance = createStart(() => ({ requestMiddleware: [...], functionMiddleware: [...] }))`. The source signature is `createStart(getOptions: () => StartInstanceOptions | Promise<StartInstanceOptions>)`.
- The real option surface is `serializationAdapters`, `defaultSsr`, `requestMiddleware`, `functionMiddleware`, and `serverFns: { fetch }` (`packages/start-client-core/src/createStart.ts:15-50`). `requestMiddleware` runs for every request handled by Start; `functionMiddleware` runs for every server function.
- These options are **not new**. They predate the retired 2026-06-02 snapshot — that file simply never listed them, so the omission was the skill's own, not upstream drift.

## CSRF protection

- `createCsrfMiddleware()` is the named API for protecting server functions from cross-site requests. The guide's recommended install 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 with none of the three are rejected unless `allowRequestsWithoutOriginCheck: true`. Options: `filter`, `origin`, `secFetchSite` (default `'same-origin'`), `referer` (default `true`), `allowRequestsWithoutOriginCheck` (default `false`), `failureResponse` (default `403 Forbidden`). The guide documents `filter`, `origin`, and `allowRequestsWithoutOriginCheck`; the rest are type-level facts.
- **Start installs this middleware automatically for server functions when the app does not define `src/start.ts`.** The trap: creating `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.

## Middleware

- Two middleware types. Request middleware uses `createMiddleware()`; `createMiddleware({ type: 'request' })` is allowed but the request type is the default. Server function middleware uses `createMiddleware({ type: 'function' })` and can define `.client(...)` and `.server(...)` phases.
- Server function middleware validation uses `.validator(...)` as well, and `inputValidator` was removed from `createMiddleware` in the same 1.169.0 release. Do not confuse middleware `.validator(...)` with server-function `.validator(...)`: they belong to different chain objects and different data contexts.
- A route guard is not a data authorization boundary. Middleware and `beforeLoad` can deny access to a page, but data returned by a server function or server route still needs its own check against the session principal.
- `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: {...} })`. Anything the client can send, the client can lie about, so values arriving via `sendContext` are client-provided data.
- **"Shape validation is not authorization."** (`guide/middleware.md:348`.) 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, otherwise a logged-in user can rewrite the value in their own request and reach other tenants' data.
- The docs' required pattern (`guide/middleware.md:377`): "Always derive the session itself from a server-trusted source (a cookie + DB lookup in `authMiddleware`), never from `sendContext`. Anything the client can send, the client can lie about."

## 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." Documented options: `enabled`, `behavior`, `log`, `include`, `exclude`, `maxTraceDepth`, environment `files`/`specifiers`/`excludeFiles`, `ignoreImporters`, `onViolation`.
- Enabled out of the box. Documented defaults: `enabled: true`; `behavior: { dev: 'mock', build: 'error' }` (`'mock'` warns and substitutes a mock module, `'error'` fails the build); `log: 'once'` (deduplicates repeated violations); scope `include` = Start's `srcDirectory`; `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 (`guide/import-protection.md:561-567`):
  - `client.specifiers` is **additive with defaults** — providing it extends the built-in list.
  - `client.files`, `client.excludeFiles`, `server.files`, `server.specifiers`, and `server.excludeFiles` **replace** the defaults. (`server.specifiers` is listed as "replaces defaults", but its default is `[]`, so it is not additive in practice.)
  - `excludeFiles` **fully replaces** `['**/node_modules/**']`. To exclude extra paths while still skipping `node_modules`, pass both: `excludeFiles: ['**/node_modules/**', '**/vendor/**']`.
  - Setting `client.files` without carrying `'**/*.server.*'` therefore silently drops the default deny rule.
- `excludeFiles: []` re-enables resolved-target checking in locations the defaults skip, such as `node_modules`. It is a deliberate opt-in, not a recommendation.
- 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'`, optional) 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 schema option that the docs do not document, so it must be labeled as such whenever it is cited and never presented as a documented option.
- Dev-mode violations can be false positives because build mode defers the check until after tree-shaking; confirm with a production build before changing a boundary.

## Server routes

- Server routes are declared by adding `server` to a `createFileRoute(...)(...)` call in a route file, and follow Router's file-based routing conventions.
- The `server` property contains `handlers` — either an object mapping HTTP methods to handler functions, or a function that receives `createHandlers` for handlers that need middleware composition — and an optional `middleware` array that applies route-level middleware to all handlers.
- 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.
- Duplicate route paths with duplicate HTTP methods are invalid; wildcard/splat routes use the trailing `$` file-route convention.

## Drift handling

- This is a dated official-doc snapshot, not a permanent rulebook. Its filename date and `last_verified_at` agree by construction; if either changes, both change together.
- Refresh trigger: re-verify when the official doc pages listed below change, or on an advisory check. Do **not** key it on local package versions moving beyond a pinned set — router/start absorb breaking changes in PATCH releases, so a version-based trigger both over- and under-fires.
- If local installed package types disagree with this file, run typecheck and record the project-specific exception rather than editing this snapshot.
- `src/modules`, `src/lib`, `src/db`, `src/server`, `src/integrations`, and `src/config` grouping remain Hypercore conventions, not official TanStack requirements. The `.functions.ts` / `.server.ts` split is official guidance, but enforcing it inside `src/modules/<domain>/<feature>/` nested folders is a Hypercore convention.

## Sources

> Sources checked 2026-11-04. Every page and source below was fetched directly 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 will drift as the pages change — the quoted text is the stable anchor.

- <https://tanstack.com/start/latest/docs/framework/react/guide/server-functions.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/middleware.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/authentication-server-primitives.md>
- <https://tanstack.com/start/latest/docs/framework/react/migrate-from-release-candidate.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/import-protection.md>
- <https://tanstack.com/start/latest/docs/framework/react/guide/server-routes.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>
- <https://registry.npmjs.org/@tanstack/start-client-core/-/start-client-core-1.170.39.tgz>
- <https://registry.npmjs.org/@tanstack/start-plugin-core/-/start-plugin-core-1.171.55.tgz>
- <https://registry.npmjs.org/@tanstack/react-start/latest>
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