skills.rest
OpenAEC-Foundation
OpenAEC-FoundationOFFICIAL
Explore all skills by this author →
GitHub

solid-errors-reactivity-debugging

Diagnose SolidJS reactivity issues with diagnostic flowcharts and devtools guidance.

4|Updated Mar 19, 2026
Search Tags:#debugging#devtools#diagnostics#reactivity#effects#stores#solidjs
One-click install
npx skills add https://github.com/OpenAEC-Foundation/SolidJS-Claude-Skill-Package --skill solid-errors-reactivity-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solid-errors-reactivity-debugging
Source: https://github.com/OpenAEC-Foundation/SolidJS-Claude-Skill-Package/tree/main/skills/source/solid-errors/solid-errors-reactivity-debugging
Command: npx skills add https://github.com/OpenAEC-Foundation/SolidJS-Claude-Skill-Package --skill solid-errors-reactivity-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

SolidJS reactivity can break when effects don't fire or stores fail to propagate, leading to UI not updating and hard-to-trace bugs. Prevents lost tracking from destructuring, conditional signal access, async tracking loss, and stale closures. This skill provides diagnostic flows, debugging strategies with solid-devtools, and practical patterns to recover a reactive graph.

Core Features & Use Cases

  • Diagnostic flowcharts and checklists to identify root causes of non-reactive behavior in SolidJS components.
  • Solid-devtools debugging guidance, best practices for profiling, and tracking-scope verification.
  • Safe patterns for avoiding destructuring, conditional reads, and async boundaries that break dependency tracking, with real-world scenarios.

Quick Start

Follow the diagnostic flowchart in this skill to locate a non-firing effect and apply the recommended tracking-scope fixes.

Frequently Asked Questions about solid-errors-reactivity-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why is my SolidJS effect not firing when the signal updates?▼

SolidJS effects fail to fire when dependency tracking is lost due to destructuring signals, conditional reads, or stale closures. Using diagnostic flowcharts helps pinpoint the exact root cause and apply tracking-scope fixes to restore reactive propagation.

How do I debug SolidJS store updates that fail to update the UI?▼

Debug SolidJS store update failures by using solid-devtools to verify tracking scopes and profile reactive graphs. Diagnostic checklists identify non-reactive behavior patterns and recommend safe coding patterns to ensure deterministic tracking.

What causes lost reactivity in SolidJS async boundaries and timeouts?▼

Lost reactivity in SolidJS async boundaries and timeouts occurs when tracking scopes are broken across asynchronous operations. Applying safe coding patterns and diagnostic strategies recovers the reactive graph and ensures updates propagate correctly.

Can I use this diagnostic approach with SolidJS 1.x and TypeScript?▼

Yes, the diagnostic flows and debugging strategies are compatible with SolidJS 1.x and 2.x environments using TypeScript. Troubleshooting rules and coding patterns ensure deterministic tracking across these versions.

What is the best way to prevent stale closures in SolidJS reactive graphs?▼

The best way to prevent stale closures is to avoid destructuring and conditional signal access while following safe coding patterns. Diagnostic playbooks provide specific rules to maintain deterministic tracking and recover broken reactive graphs.

Related Skills

Explore More Software Engineering Skills→
OpenAEC-FoundationOpenAEC-Foundation
4

solid-syntax-jsx

Outline SolidJS JSX best practices for control-flow primitives and DOM optimization.

Official
Advanced
danielsogldanielsogl
39

angular-signals

Migrate Angular component state from BehaviorSubject to signals.

Community
Advanced
vallafedericovallafederico

solid-core-primitives

Explain SolidJS reactivity primitives including signals, effects, stores, and memos.

Community
Basic
blankuzrblankuzr
6

r-shiny-debugging

Trace Shiny reactive-state failures through the dependency graph.

Community
Advanced