SolidStart v2

Use this skill for SolidStart v2 app work. Keep it focused on Start-specific architecture and server boundaries.

If the task is mainly about Solid core reactivity, component semantics, or Solid 2.x API behavior, use the matching Solid skill alongside this one.

Version boundary

SolidStart v2 architecture guidance does not imply that the app is already using Solid 2.x core semantics.
Start v2 and Solid 2 are not the same migration step. Check the installed Solid packages before applying 2.x-only core advice like Loading, Errored, split createEffect, or top-level reactive read warnings.
Use this skill for Start route, server, auth, middleware, metadata, and runtime patterns. Pull in a Solid core skill only for component-level or reactivity-level questions.

Build SolidStart apps with the framework's native data and mutation model instead of generic fetch glue.
Keep server-only code on the server and use the right boundary for each concern.
Produce app code that is portable, secure, and easy to evolve.
Stay token-efficient by reading deeper references only when the task needs them.