signalize-signals

Create, configure, and destroy reactive signals for @spearwolf/signalize.

30|1|Updated Sep 16, 2021

Search Tags:#typescript #signals #lifecycle #reactivity #effects #signalize #destroy

Ready to run

npx skills add https://github.com/spearwolf/signalize --skill signalize-signals

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: signalize-signals
Source: https://github.com/spearwolf/signalize/tree/main/skills/signalize-signals
Command: npx skills add https://github.com/spearwolf/signalize --skill signalize-signals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides the core reactive primitives used to create, configure, and clean up signals in @spearwolf/signalize, enabling robust fine-grained reactivity without framework lock-in.

Core Features & Use Cases

Create and manage signals with get/set/value and lifecycle methods (createSignal, destroySignal, touch, onChange)
Configure per-signal options like lazy initialization and custom compare logic, plus functional API helpers (value, touch, destroySignal, mute/unmute)
Use in library code or applications to implement reactive patterns such as effects, memos, and links

Quick Start

Import createSignal and use it to create a reactive signal, then read with get() and destroy it when finished.

Frequently Asked Questions about signalize-signals

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

FAQPage Schema

How do I create and destroy reactive signals in TypeScript?▼

You can create reactive signals using createSignal and safely clean them up by calling destroySignal, ensuring proper lifecycle management and preventing memory leaks in client-side applications.

What is fine-grained reactivity and when do I need it for client-side apps?▼

Fine-grained reactivity tracks state changes at the individual signal level rather than reloading entire component trees, making it ideal for client-side apps or libraries requiring precise DOM updates and optimized rendering performance.

Can I configure lazy initialization and custom compare logic for signals?▼

Yes, signals support per-signal options for lazy initialization and custom compare logic, allowing you to control when initial values compute and prevent unnecessary updates when new values are equivalent to existing ones.

Does this reactive signals library work without framework lock-in?▼

Yes, these core reactive primitives are designed for framework-agnostic use, enabling you to build effects, memos, and links in library code or applications without tying your state management to a specific UI framework.

How do I read and mutate signal values using the functional API?▼

The functional API provides helpers like value, touch, and mute to read, trigger, and silence signals, while the object API offers get/set methods for direct value handling and onChange subscriptions.

What are the limitations of using signals for state management?▼

Signals require manual lifecycle management via destroySignal to prevent memory leaks, and developers must explicitly handle muting or custom compare logic to avoid unnecessary effect triggers in complex reactive dependency graphs.