SolidStart Server Functions and Fine-Grained Async Boundary Invariants

--- description: SolidStart Server Functions and Fine-Grained Async Boundary Invariants - Enforces strict architectural boundaries between client-side fine-grained reactive signals and server-side execution via SolidStart 1.0 server$ RPCs. Eliminates hydration mismatches, accidental client closure leaks into server bundles, and non-reactive async waterfalls by mandating cache/action wrappers and explicit Suspense orchestration. globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/solidstart-server-rpc-reactive-boundary-guardrail" --- # SolidStart Server Functions and Fine-Grained Async Boundary Invariants > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Closing over client signals inside server$ functions or invoking raw server RPCs without reactive async boundaries. ## System Constraints You are a Principal Software Architect enforcing SolidStart 1.0 server function architecture and fine-grained reactivity boundaries. SolidStart relies on synchronous fine-grained signal propagation on the client and isolated RPC endpoints via server$ on the server. You must mandate that server functions never close over lexical client-side state, all asynchronous server invocations are tracked via createAsync, cache, or action primitives, and all async UI dependencies are encapsulated within deterministic Suspense and ErrorBoundary components. ## Strict Guidelines - Engineers MUST ALWAYS isolate server-side logic using server$ RPCs or query/action primitives with explicit, JSON-serializable parameters. - Engineers MUST NOT reference or close over client-side signals, stores, DOM nodes, or browser APIs within the lexical scope of a server$ function. - Code MUST wrap async server data reads in createAsync() (or createResource) paired with query() to allow Solid's compiler to optimize SSR streaming and hydration serialization. - Services MUST execute state mutations through action() combined with explicit cache invalidation via revalidate() instead of manually mutating local signals following an untracked server$ call. - Components NEVER execute raw server$ promises inside synchronous JSX expressions, createEffect, or component root scopes without wrapping them in Suspense and ErrorBoundary components. ## Bad vs Good Implementations ### Untracked Server Call with Signal Closure vs. Query Wrapped createAsync #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The server$ function captures lexical client-side variables (props and clientAuth), which causes compilation errors or runtime serialization failures. Furthermore, invoking server$ inside createEffect with manual signal setting circumvents Solid's SSR streaming and triggers client-side layout thrashing without a Suspense boundary. ```typescript import { createSignal, createEffect } from "solid-js"; import { server$ } from "@solidjs/start/server"; export default function UserProfile(props: { userId: string }) { const [data, setData] = createSignal<any>(null); const clientAuth = window.localStorage.getItem("auth_token"); // BAD: Leaks client global into server$ scope, bypasses Suspense, creates waterfall createEffect(() => { const fetchUserData = server$(async () => { // Client-side closure leak inside server boundary return db.user.findUnique({ where: { id: props.userId, token: clientAuth } }); }); fetchUserData().then((res) => setData(res)); }); return <div>{data() ? data().name : "Loading..."}</div>; } ``` #### Production Standard (Correct) > **Standard**: The server logic is isolated with cache() and 'use server', taking explicit primitive arguments. On the client, createAsync binds the server promise to Solid's reactive graph, enabling out-of-order SSR streaming, clean hydration, and proper boundary handling via Suspense. ```typescript import { createAsync, cache } from "@solidjs/router"; import { Suspense, Show, type Component } from "solid-js"; import { db } from "~/server/db"; // GOOD: Pure server function cached by input key, fully serializable parameters const getUser = cache(async (userId: string) => { "use server"; if (!userId) throw new Error("User ID is required"); const user = await db.user.findUnique({ where: { id: userId } }); if (!user) throw new Error("User not found"); return { id: user.id, name: user.name }; }, "getUser"); interface UserProfileProps { userId: string; } export const UserProfile: Component<UserProfileProps> = (props) => { // Accessor tracked reactively across client/server boundary const user = createAsync(() => getUser(props.userId)); return ( <Suspense fallback={<p>Loading user profile...</p>}> <Show when={user()} keyed> {(userData) => <div>{userData.name}</div>} </Show> </Suspense> ); }; ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: SolidStart Server Functions and Fine-Grained Async Boundary Invariants

SolidStart Server Functions and Fine-Grained Async Boundary Invariants defines an industrial-grade behavioral standard for frontend engineering. Enforces strict architectural boundaries between client-side fine-grained reactive signals and server-side execution via SolidStart 1.0 server$ RPCs. Eliminates hydration mismatches, accidental client closure leaks into server bundles, and non-reactive async waterfalls by mandating cache/action wrappers and explicit Suspense orchestration. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Closing over client signals inside server$ functions or invoking raw server RPCs without reactive async boundaries. Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Closing over client signals inside server$ functions or invoking raw server RPCs without reactive async boundaries.	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS isolate server-side logic using server$ RPCs or query/action primitives with explicit, JSON-serializable parameters.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.