SolidJS Patterns

Quick Guide: A signal is read by calling it — count(), never count — and a component body runs once, so everything that must change over time is an expression inside JSX rather than a re-render. Props are a live proxy: destructuring them freezes their values. Conditionals and lists go through <Show>, <For>, <Index> and <Switch> so Solid can update the DOM node rather than the subtree.

Detailed Resources:

• examples/core.md — signals, effects, on(), memos, batch
• examples/components.md — splitProps, mergeProps, control flow, refs, component types, <Dynamic>
• examples/stores.md — createStore, produce, reconcile, context
• examples/resources.md — createResource, and createAsync + query under SolidStart
• reference.md — decision trees, the anti-pattern routing table, import cheat sheet, review checklists

Which path applies

• Plain SolidJS — async data goes through createResource, read under <Suspense>. Follow examples/resources.md from the top.
• SolidStart with @solidjs/router — createAsync + query replace createResource, because they deduplicate and serialise across the server boundary. Same file, second half. Everything else on this page is unchanged.