solid-js-expert

SolidJS Expert

Overview

Use this skill to write correct SolidJS across the full stack: core reactivity, components, Solid Router, SolidStart, and Solid Meta. SolidJS looks like React but is not React: components run once, signals are functions you call, and reactivity is fine-grained rather than re-render-based. Most mistakes come from applying React habits. Route non-trivial work to the focused files in references/; do not answer from SKILL.md alone when the request involves reactivity behavior, the server/client boundary, or ecosystem APIs.

Source: distilled from the official SolidJS documentation (docs.solidjs.com, solidjs/solid-docs).

Design philosophy

• Teach the reactive mental model first; most Solid bugs are React habits applied to a run-once model.
• One topic per reference file; load only what the task needs.
• Prefer the idiomatic Solid primitive over a hand-rolled React-style pattern (<For> over array.map(), createMemo over derived state in an effect, stores over deeply nested signals).
• Keep the server/client boundary explicit in any SolidStart work: name what runs on the server, what runs on the client, and what must be serializable.

When to use

• Write or review SolidJS components, signals, stores, effects, or memos.
• Debug "my signal/store is not updating" or reactivity that silently breaks.
• Choose control-flow (<For> vs <Index>, <Show> vs <Switch>).
• Build routing with Solid Router (<Route>, useParams, query, createAsync, action).
• Build a SolidStart app: file routing, "use server", API routes, sessions, data mutations, serialization.
• Manage document head / SEO with Solid Meta.
• Migrate React-shaped code to idiomatic Solid.

When not to use

• Generic JavaScript or TypeScript type questions with no Solid involvement; route TypeScript type design to typescript-engineer.
• Other frameworks (React, Vue, Svelte). The reactive model here is Solid-specific and does not transfer.
• Build-tool failures (Vite/Vinxi config, package resolution) unrelated to Solid APIs.