Skill Feedback: meta-framework (mixed)

Skill Feedback: meta-framework

Package: @tanstack/db
Skill version: 0.5.30
Rating: mixed

Task

Integrate TanStack DB with Electric in a TanStack Start app — both the client-side (live queries, preloading) and the server-side (proxy route for Electric shapes, mutation endpoints).

What Worked

• ssr: false + await collection.preload() in route loader pattern was correct and clear
• "Collections are singletons — define once in shared module" guidance was helpful
• The TanStack Start code examples matched the actual API

What Failed

• No direct errors from this skill.

Missing

1. Server-side integration is completely absent — The skill covers the client-side integration thoroughly (ssr: false, preload, live queries) but says nothing about the server-side: how to create a proxy route for Electric shapes, and how to set up mutation endpoints using createServerFn. The electric-new-feature skill tried to fill this gap with a TanStack Start proxy route example, but used createServerFileRoute which doesn't exist. If the meta-framework skill covered the server route pattern for TanStack Start (using server.handlers on createFileRoute), this would have been the natural place to find it.

2. No mention of createServerFn for mutations — When using Electric with TanStack Start, mutations go through server functions that call Postgres and return a txid. The meta-framework skill focuses entirely on the read path. A brief "mutations go through createServerFn — see the Electric skill for txid handshake details" would connect the dots.

Self-Corrections

• None directly from this skill — the client-side patterns all worked on the first try.

User Comments

• User suggested the Electric skill "shouldn't say much about TanStack Start's usage — or it should have a dedicated one." A meta-framework skill that covers both client and server integration for each framework would be that dedicated skill.

Locate the meta-framework skill and compare its client-side TanStack Start guidance with the missing server-side integration described here. Read the existing Electric and electric-new-feature guidance, then document the valid server.handlers pattern on createFileRoute and the createServerFn mutation connection; done means both server concerns are covered without the invalid createServerFileRoute example.