Files
stack/packages/mosaic/framework/skills/vercel-react-best-practices/rules/server-serialization.md
T
fargo 1a822493ba format: apply repo prettier (3.8.1) to the folded skills tree
963 markdown files reformatted with the repository's pinned prettier so
pnpm format:check covers the folded tree like every other repo file.

The formatter's embedded-language pass also normalized code fences
(TS semicolons, closed HTML tags in examples, lowercased CSS hex colors,
one renumbered list that skipped an index). Alphanumeric token deltas vs
the fold commit were audited file-by-file; all are formatter-equivalent
markup normalizations plus the four sanitized skills.
2026-08-19 14:37:17 -05:00

1006 B

title, impact, impactDescription, tags
title impact impactDescription tags
Minimize Serialization at RSC Boundaries HIGH reduces data transfer size server, rsc, serialization, props

Minimize Serialization at RSC Boundaries

The React Server/Client boundary serializes all object properties into strings and embeds them in the HTML response and subsequent RSC requests. This serialized data directly impacts page weight and load time, so size matters a lot. Only pass fields that the client actually uses.

Incorrect (serializes all 50 fields):

async function Page() {
  const user = await fetchUser(); // 50 fields
  return <Profile user={user} />;
}

('use client');
function Profile({ user }: { user: User }) {
  return <div>{user.name}</div>; // uses 1 field
}

Correct (serializes only 1 field):

async function Page() {
  const user = await fetchUser();
  return <Profile name={user.name} />;
}

('use client');
function Profile({ name }: { name: string }) {
  return <div>{name}</div>;
}