framework-solidjs

<skill_doc> <trigger_keywords>

Trigger Keywords

Activate this skill when the user mentions any of:

Core: SolidJS, Solid.js, createSignal, createStore, createMemo, createEffect, createResource, createAsync

Components:

<Show>

<For>

<Index>

<Switch>

<Match>

<Dynamic>

<Portal>

<ErrorBoundary>

Lifecycles: onMount, onCleanup, batch, untrack

Ecosystem: SolidStart, Solid Router, Solid Primitives, Vinxi, Server Functions, "use server", createServerFn

Tooling: justfile, just, bun, bun run, biome </trigger_keywords>

NO React Hooks:

useState

useEffect

useMemo

are forbidden. Use

createSignal

createEffect

createMemo

NO Prop Destructuring:
```
const { name } = props;
```
breaks reactivity. Always access via
```
props.name
```
or use
```
splitProps
```
/
```
mergeProps
```
.
NO Early Returns in Components: Reactivity setup runs once. Early returns stop effects from being created.
NO
array.map
for JSX: Use
```
<For>
```
or
```
<Index>
```
for reactive lists.
NO
any
: Strictly forbidden. Use
```
unknown
```
or proper types.
NO
@ts-ignore
: Fix errors instead.

Discovery: Check for
```
justfile
```
first. Prefer
```
just
```
recipes (e.g.,
```
just dev
```
,
```
just build
```
) over raw
```
bun
```
or
```
npm
```
commands.
Runtime: Prefer
bun
over
```
npm
```
or
```
yarn
```
for script execution and package management.
Build: Use
```
bun run dev
```
or
```
bun run build
```
if no
```
justfile
```
exists.
Routing: Identify if
```
solid-router
```
or file-based routing (SolidStart) is used.
Type Checking: Use
```
bun run tsc --noEmit
```
or
```
just typecheck
```
to verify safety.

SolidJS Specialist - Fine-grained reactivity without a Virtual DOM.

Philosophy:

Core Primitives:

Tooling Preferences:

Destructuring Props: ❌

const MyComp = ({ title }) => <div>{title}</div>

(Loses reactivity) ✅

const MyComp = (props) => <div>{props.title}</div>

Tracking Scopes: Reactivity is only tracked synchronously within a tracking scope (Effect, Memo, Render). Async callbacks lose the tracking context unless
```
runWithOwner
```
is used, but usually you just read signals where you need them.
Batching: Solid batches updates automatically in effects/event handlers. Use
```
batch(() => ...)
```
for manual grouping outside those contexts.

Examples: See
```
examples/examples.md
```
for detailed code patterns.
References: See
```
references/reference.md
```
for official documentation links. </skill_doc>