lazy-prefetch-pattern
Skill1.2k starsChanged 21 days agoApache-2.0View on GitHub
Use the ChatJS React Query v5 lazy-prefetch pattern without blocking server rendering. Use when prefetching tRPC queries in Next.js Server Components or changing query dehydration and hydration behavior in apps/chat.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Start optional server prefetches early without awaiting them so they can stream through React hydration without blocking rendering.
- Very specific: line 10
Use the exported prefetch() helper from @/trpc/server: prefetch(trpc.foo.bar.queryOptions(...)).
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lazy prefetch pattern
Start optional server prefetches early without awaiting them so they can stream through React hydration without blocking rendering.
- Use the exported
prefetch()helper from@/trpc/server:prefetch(trpc.foo.bar.queryOptions(...)). It handles both paginated and non-paginated queries. - Await only data required before rendering.
- Render through the existing
HydrateClientorHydrationBoundary.
This depends on trpc/query-client.ts dehydrating pending queries and using SuperJSON for serialization and hydration. Preserve those settings when using this pattern.
Other versions2 projects use a version of this.
Word for word · 1
- FranciscoMoretti/sparka★ 1.2k100% same
Edited · 1
- FranciscoMoretti/chat-js★ 1.2k30% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- check-visual-changesSkill
- create-vercel-ai-issueSkill
- dev-auth-bypassSkill
- economical-visual-testsSkill
- generate-code-snippetSkill
- making-ui-changesSkill
- next-cache-components-adoptionSkill
- next-dev-loopSkill
- next-partial-prefetching-adoptionSkill
- review-docsSkill
- strategic-testingSkill
- triage-visual-changesSkill
- trpc-patternsSkill
- vitest-visual-testingSkill
- worktree-portsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.