---
name: "solidjs-fine-grained-reactivity"
description: "Achieve raw DOM performance without virtual DOM diffing using SolidJS fine-grained signals."
metadata:
  author: "Ryan Carniato"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "create solidjs component"
  - "solidjs createeffect vs creatememo"
  - "solidjs control flow <show>"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# SolidJS Signals & Fine-Grained Virtual-DOM-Less Rendering

Builds applications with SolidJS: createSignal, createMemo, createEffect, resource loading with createResource, control flow primitives (<Show>, <For>, <Switch>), and understanding the difference between components running once vs re-renders.

## When to Invoke
Invoke this skill whenever you need to:
- create solidjs component
- solidjs createeffect vs creatememo
- solidjs control flow <show>

## Execution SOP & Rules
1. Remember SolidJS component functions execute only once upon mounting; never destructure props.
2. Use accessor syntax: count() to read signals and setCount(c => c + 1) to mutate.
3. Use built-in control flow components: <Show when={loggedIn()} fallback={<Login />}>.
4. Use createMemo(() => expensiveCalc(val())) for cached derived computations.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.