solid-impl-state-patterns

What problem does it solve?

SolidJS state design is easy to get wrong: developers often misreason about when to use signals, stores, or context, and fall into anti-patterns like deriving state with effects or destructuring stores. This Skill provides a structured guide to choose and compose the core primitives (signals, stores, context), memoization with createMemo, and practical form-state patterns, resulting in maintainable, predictable reactivity.

Core Features & Use Cases

• Decision-tree guidance for selecting between createSignal, createStore, createContext, and createMemo based on data shape and sharing needs.
• Form-state patterns and derived-state best practices, including avoidance of misuse of createEffect for derived values.
• Context + Store composition strategies and external state integration patterns (from and reconcile) to keep apps scalable.

Quick Start

Choose an appropriate SolidJS state pattern for your component tree and explain when to use createSignal, createStore, createContext, and createMemo, including form-state patterns.