SolidStart 1.0 Server Function Boundaries & Fine-Grained Reactive Serialization

--- description: SolidStart 1.0 Server Function Boundaries & Fine-Grained Reactive Serialization - Enforces strict isolation between SolidJS fine-grained reactivity and SolidStart 1.0 server$ RPC boundaries. Prohibits capturing client-side signals inside server closures and mandates wrapping server queries inside query/cache and createAsync within Suspense boundaries to prevent hydration mismatches and broken tracking roots. globs: src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/solidstart-server-rpc-async-boundaries-guardrail" --- # SolidStart 1.0 Server Function Boundaries & Fine-Grained Reactive Serialization > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Capturing reactive signal accessors inside server$ closures or invoking naked server RPC promises within reactive render bodies ## System Constraints You are a Principal Software Architect enforcing SolidStart 1.0 server function architecture and reactivity guardrails. You mandate clear segregation between client-side signal accessors and server-side RPC executions. Code must prevent boundary leaks, serialization failures, and uncoordinated async hydration locks. ## Strict Guidelines - Engineers MUST ALWAYS pass signals into server functions as evaluated, serializable arguments via function invocations rather than referencing client signal accessors directly inside server$ closures. - Engineers MUST wrap read-oriented server functions using query() or cache() from @solidjs/router and consume them via createAsync() to preserve Solid's synchronous tracking roots and Suspense integration. - Engineers MUST wrap mutation server functions using action() from @solidjs/router to maintain automated submission tracking and cache invalidation via reload(). - Engineers MUST NOT invoke server$ functions nakedly inside the synchronous body of a component without createAsync, createResource, or an explicit event handler. - Components NEVER render asynchronous createAsync results directly without an enclosing <Suspense> boundary or null-safety guards, preventing hydration desynchronization between SSR and client. ## Bad vs Good Implementations ### Decoupling Reactive Signals from Server RPC Execution #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Client-side signal accessors cannot be serialized across the server$ boundary. Referencing userId() inside server$ results in a runtime reference error on the server. Additionally, calling the RPC nakedly during component initialization triggers hydration mismatches and uncoordinated async waterfall rendering. ```typescript import { createSignal, createEffect } from 'solid-js'; import { server$ } from '@solidjs/start/server'; import { db } from '~/server/db'; export default function UserProfile() { const [userId, setUserId] = createSignal('usr_101'); const [user, setUser] = createSignal<any>(null); // ANTI-PATTERN: Capturing client-side reactive accessor directly in server$ closure // Breaks compilation boundaries, loses tracking, and causes undefined runtime scope on server const fetchUser = server$(async () => { const id = userId(); // Invalid: userId is undefined on the server return await db.user.findUnique({ where: { id } }); }); // ANTI-PATTERN: Naked asynchronous execution inside component root without Suspense/createAsync fetchUser().then(res => setUser(res)); return <div>{user()?.name}</div>; } ``` #### Production Standard (Correct) > **Standard**: The server function explicitly accepts primitive, serializable arguments via 'use server' / query(). The client component tracks userId() through createAsync, correctly orchestrating async resolution with the <Suspense> boundary without crossing execution scopes. ```typescript import { createSignal, Suspense } from 'solid-js'; import { query, createAsync } from '@solidjs/router'; import { db } from '~/server/db'; // INVARIANT: Server function takes explicit serializable primitives and is wrapped in query() const getUserById = query(async (id: string) => { 'use server'; if (!id) return null; return await db.user.findUnique({ where: { id } }); }, 'getUserById'); export default function UserProfile() { const [userId, setUserId] = createSignal('usr_101'); // INVARIANT: createAsync tracks signal accessor on client and pipes into Solid's reactive graph const user = createAsync(() => getUserById(userId())); return ( <Suspense fallback={<p>Loading profile...</p>}> <div>{user()?.name}</div> </Suspense> ); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: SolidStart 1.0 Server Function Boundaries & Fine-Grained Reactive Serialization

SolidStart 1.0 Server Function Boundaries & Fine-Grained Reactive Serialization defines an industrial-grade behavioral standard for frontend engineering. Enforces strict isolation between SolidJS fine-grained reactivity and SolidStart 1.0 server$ RPC boundaries. Prohibits capturing client-side signals inside server closures and mandates wrapping server queries inside query/cache and createAsync within Suspense boundaries to prevent hydration mismatches and broken tracking roots. 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: Capturing reactive signal accessors inside server$ closures or invoking naked server RPC promises within reactive render bodies 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	Capturing reactive signal accessors inside server$ closures or invoking naked server RPC promises within reactive render bodies	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 pass signals into server functions as evaluated, serializable arguments via function invocations rather than referencing client signal accessors directly inside server$ closures.

Engineers MUST ALWAYS pass signals into server functions as evaluated, serializable arguments via function invocations rather than referencing client signal accessors directly inside server$ closures.

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.